Senior Content Engineer

Content Engineer

We have thousands of developers building on Healthie's APIs every day -- founders, engineers, and clinical operators who chose Healthie because they needed a compliant foundation they could build on top of, not just run on. That community has grown organically and it requires: world-class documentation, clearer architecture guidance, richer code samples, and a genuine technical presence that meets builders where they are.

As Healthie's Content Engineer, that's what you'll build. You'll own the technical content layer that makes Healthie's platform legible and reachable for the developers and operators who want to build on it -- documentation, integration guides, architecture references, code samples.

Your job is to make that distinction clear, credible, and useful to every builder who encounters Healthie -- whether they're reading a quickstart guide, watching a demo, or trying to figure out how Healthie fits into their stack.

• Audit what we have, find the gaps, and raise the quality bar across all developer-facing docs: quick starts, API reference, integration guides, rate limit and query depth rules, and code samples in the languages developers actually use.

• Develop guidance specifically optimized for LLM-assisted development, so that customers building on Healthie via AI coding tools have clear rails to work within and a dramatically better experience.

• Work closely with Engineering to ensure our documentation reflects hard rules around things like rate limits and query depth (the guardrails that make building on Healthie safe and predictable).

• Develop the content plan that maps to our platform story — what we publish, where, how often, and for whom.

• Write and produce technical content: integration walkthroughs, architecture guides, API use case spotlights, and "here's what you can build" demos that make the possibilities feel real and reachable.

• Create the diagrams, stack guides, and reference architectures that help developers immediately understand how Healthie fits into their broader tech stack and support them as those decisions change over time.

• Represent Healthie at conferences, developer meetups, hackathons, and healthcare tech events.

• Partner with Sales and Solutions teams to bring "show, don't tell" to conversations — live demos, real examples, a tangible sense of what's buildable.

• Help retire "yes, but you'd need to do it via the API" from our vocabulary for good. Own the live demo tool that helps our customers know how they can best leverage Healthie within their tech stack

• Invest in and grow the developer community we already have: the forum, the Discord, the Git Hub presence, the regular touchpoints that make builders feel genuinely supported.

• Be the person developers trust: answering questions, closing the loop on feedback, and making sure the people building on Healthie know they're not on their own.

• Run events, AMAs, and office hours that connect our community directly to our product and engineering teams.

• You've shipped real documentation for an API, SDK, or developer platform, and you have strong opinions about what makes it good.

• You have a background in technical writing, developer relations, content engineering, or a role that sat directly at the intersection of engineering and external-facing content. You know what "production-ready" means and you apply that standard to documentation.

• You can hold a substantive conversation with an engineer about rate limiting, query depth, schema design, or authentication flows -- and then turn that conversation into something a developer can actually use.

• You find healthcare important. Not just interesting -- important. Compliance constraints, clinical workflows, the stakes of software that touches patient care: these things motivate rather than frustrate you.

• Bonus: you've built something with an AI coding tool and have a genuine take on what makes an API and its documentation "LLM-friendly."

The hard part of healthcare software is not the interface. It's the…