Technical WriterJob Title: Technical Writer - Systems Discovery & Documentation Role Overview :- We are seeking a highly analytical and technically curious Technical Writer to play a foundational role in uncovering, documenting, and structuring our internal systems knowledge.- This is not a traditional writing role - we are looking for someone who thrives on reverse-engineering undocumented systems, conducting deep interviews, and creating the first layer of formal technical documentation across our platforms and services.Key Responsibilities- Discover undocumented systems by interviewing engineers, long-tenured staff, production support, and business analysts.- Inventory APIs, services, data flows, integration points, and backend behaviors across core platforms such as the OMS/BOS, CCR, and Market Connectivity Platforms.- Analyze source code (with access to read-only repos) to document service behavior, business logic, and internal workflows.- Conduct tours of DEV and production systems (led by production support or engineering) to understand real-world behavior.- Map out system-to-system interactions, external integrations, and user-facing dependencies.- Work with architects and dev leads to ensure terminology, flows, and documentation reflect the current state of architecture.- Document:- Service catalogs- Sequence and flow diagrams- Data dictionaries- API and integration specs- Deployment/infra topologies- Change history and evolution of legacy systemsExpected Outputs :- Your documentation will serve as the baseline for modernization, onboarding, and dev team velocity. Outputs include:- Service Inventory: Detailed listing of services, purpose, endpoints, and dependencies.- API Reference Docs: REST and/or internal RPC documentation with request/response formats.- System Interaction Diagrams: Sequence diagrams, swimlanes, or call flows.- Integration Maps: Data and process integrations with third parties or internal platforms.- Infrastructure Topologies: DEV/PROD environments, component maps, deployment models.- Source-linked Comments: Extracted documentation or inline references to logic in source code.- Glossary of Terms & Acronyms: Shared business-technical vocabulary.- Change Logs and Version Notes: Historical evolution of key components.- Developer Onboarding Packs: For each major system/module.Required Skills & Qualifications :- 3-7 years of experience in technical writing for software products or enterprise systems.- Ability to interview deeply and synthesize information from multiple technical and non-technical stakeholders.- Strong comfort with code-reading, log analysis, and API tools (Postman, Swagger, etc.).- Familiarity with:- Microservices, APIs, and service architectures- Sequence diagrams (PlantUML, Lucidchart, etc.)- Markdown, Confluence, Git, and documentation platforms- Proven ability to create clarity from chaos - structuring documentation from scratch.- Bonus: Experience in fintech, capital markets, or brokerage systems.What Success Looks Like- Engineering and business teams no longer rely on tribal knowledge alone.- A new developer or integrator can onboard to a system in days, not weeks.- Architects and PMs can refer to diagrams and structured docs during planning.- Core legacy systems are demystified through clear language and visuals.- Documentation becomes a part of our delivery process and internal standards. (ref:updazz.com)