Platform Engineer

Docflow builds AI agents that run the back office for healthcare providers. Our automation handles the work that buries their teams: document intake, prior authorizations, order entry, and payer portal workflows. Customers start with a paid pilot, see real work getting done within weeks, and expand from there.

We’re a small, scrappy, AI-native founding team, and we’re growing fast. A year ago, agents opened none of the pull requests merged into our codebase. Last month, they opened more than half. Building the system that makes that safe is now the most important engineering work we do. That’s why we’re hiring you.

You won’t be writing our automations. You’ll be building the system that writes them, runs them, and keeps them working.

Take browser automation. We run hundreds of automations against payer and provider portals we don’t control, following business rules that change whenever a payer or a customer does. Portals get redesigned overnight. A payer adds a step. A customer changes how they want an order handled. No team of people could keep up with that by hand, so agents do most of it.

They investigate failures, trace them to a root cause, write the fix, review each other’s code, confirm the fix worked in production, and finish stuck work themselves in a live browser when an automation can’t.

Your job is to build the engineering system all of that happens inside: the runtime agents work in, the pipeline their changes ship through, the observability that shows them and us what’s actually happening, and the guardrails that keep an agent’s change from reaching a customer unchecked. Browser automation is just one example. The same system supports document extraction, eligibility checks, outbound calling, and whatever we build next.

This is infrastructure engineering: distributed systems, durable execution, deployment and versioning, observability, reliability, and security. What’s different is who uses what you build. Your users are agents and the people who supervise them, and agents are demanding users. They work fast, they work in parallel, and they will find every ambiguity in an interface and every gap in a guardrail.

We’re hiring two engineers. This is the one that builds the platform. Our other engineering role, Product Engineer, owns what customers experience: the tools built on top of the platform and the product they use every day. If you’d rather build the system every workflow and every agent depends on than tune any one of them, this is your seat.

We write strictly typed Type Script in a functional style: algebraic data types and discriminated unions, state reified as explicit values rather than implied by scattered flags, and exhaustive handling the compiler enforces. That matters more when agents write much of the code, not less. When an agent adds a new case, the compiler walks it to every place that has to handle it.

Because we handle protected health information, reliability and care are not optional. An agent moves faster than a person, and so do its mistakes. A big part of this job is making sure the system catches them first.

• Build the runtime our agents work in: isolated sessions on on-demand cloud machines, warm pools, sandboxed browsers, and tightly scoped access to the credentials and portals each job needs

• Evolve the loop that carries a problem from first report to verified fix: investigation, root cause, code change, automated review, human approval, deploy, and verification against real business outcomes in production

• Own deployment and versioning, so a workflow change can ship in under a minute, run exactly the code it was built with, and roll back cleanly without anyone watching

• Build the observability that makes a highly autonomous system…