Senior Technical Writer in Bengaluru, Karnātaka at DexCare

One multifunctional technical writer embedded with our platform engineering teams in the Bangalore GCC. The role is API-first — the primary reader is an engineer integrating with DexCare's APIs — but deliberately not API-only: the writer also owns end-user and admin documentation and pivots between the two streams as launches demand. The writer owns API reference documentation, developer integration guides, release notes, and product user/admin documentation across DexCare's product lines (Acquire, Search, Scheduling, PDM, Optimize, Virtual/ODV, Mila).

We sized the two streams before writing this spec. The API/platform stream runs ~0.7–0.85 FTE sustained: four platform-spine APIs under active documentation through the re-platform program, PDM ingest and third-party syndication, the Optimize developer portal, Mila integration payloads, and release notes across all product lines. The user/admin stream runs ~0.25–0.35 FTE and is bursty — heavy at product launches, light in maintenance. Combined that is roughly one FTE before AI leverage, so we are hiring one writer who can carry both, not a specialist for each. Zinnov should screen for range accordingly.

• API reference documentation: Author and maintain OpenAPI (OAS 3.0) specifications and the reference documentation generated from them, keeping them accurate release over release.
• Developer guides: Integration guides, quickstarts, and authentication/tenancy walkthroughs for customer and partner engineers consuming our platform APIs.
• Release notes: Own the engineering and product release-notes pipeline on our release cadence, working from Jira and GitHub rather than waiting for inputs.
• Docs-as-code workflow: All documentation lives in Markdown on GitHub and moves through pull-request review. Drafting is AI-assisted (we use Claude heavily across R&D); the writer's judgment is the editorial layer on top, not a replacement for it.
• User & admin documentation: Second stream, picked up in launch bursts and maintenance: product user manuals, admin-app help content, and customer-facing launch collateral (for example, maintaining the PDM user manual as the product evolves).
• Partnership: Sits with Engineering and Product daily. Must be able to pull accuracy out of busy engineers — reading the code change, the spec, and the ticket — rather than needing content handed over finished.

• Range across both documentation types: 4–7 years of technical writing with the majority on developer-facing content (API references, SDK docs, integration guides) plus real end-user or admin documentation experience (product manuals, help content). The role is API-first but multifunctional — a portfolio showing only one of the two falls short, and a UI-help-only portfolio does not qualify.
• OpenAPI / OAS 3.0 hands-on: Can read, edit, and maintain OAS 3.0 specs directly — not just render them in a portal.
• REST fluency: Comfortable with endpoints, request/response shapes, OAuth2/JWT auth, webhooks, and error semantics; can fire a test call in Postman or curl to verify what they are documenting.
• GitHub + Markdown: Branches, pull requests, reviews, merge discipline. Docs-as-code is the daily workflow, not an aspiration.
• Reads payloads and code: Can read JSON/YAML and follow sample code in at least one of Python, Java, or JavaScript well enough to catch documentation errors.
• Strong written English: A writing sample (API reference or developer guide they authored) is required with every submitted profile.

• Healthcare technical writing: Prior technical writing in healthcare or healthtech is a big plus — EMR/EHR integrations, HL7 or FHIR interfaces, provider or claims data, HIPAA-aware documentation. A writer who already speaks this language shortens ramp materially; weight this heavily when two profiles are otherwise equal.
• Documentation tooling: Redoc, Swagger UI, Stoplight, ReadMe, Docusaurus, or similar API documentation platforms.
• AI-assisted documentation: Demonstrated use of AI tools (Claude, Copilot, or similar) in a real documentation workflow — prompting, reviewing, and correcting output rather than pasting it.