Senior Technical Writer

Who is Dex. Care? Dex. Care optimizes time in healthcare, streamlining patient access, reducing waits, and enhancing overall experiences. Guided by our mission – Nobody waits for care – Dex. Care addresses tech gaps by aligning supply and demand to modernize healthcare infrastructures for an inclusive ecosystem. We are equally committed to our DEIB mission: Creating an inclusive workplace where diversity drives innovation, equity ensures fairness, and belonging strengthens collaboration, enabling everyone to thrive.

What is Dex. Care? Dex. Care, a digital care orchestration platform, streamlines care delivery logistics. It empowers healthcare systems to predict constraints and precisely schedule services, optimizecapacity, and cuts operational costs. Currently serving 57 million patients, including Kaiser Permanente and Providence, Dex.

Care ushers in a new era of digital-care access, ensuring health systems can efficiently track and deliver every hour of capacity for consumer ease. For more information, visit www.dexcare.com or follow us on LinkedIn. About Role 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 Dex. Care'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 Dex.

Care's product lines (Acquire, Search, Scheduling, PDM, Optimize, Virtual/ODV, Mila). Why One Multifunctional Hire 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.