Curative is building the future of health insurance with a first-of-its-kind employer-based plan designed to remove financial barriers and make care truly accessible: one monthly premium with $0 copays and $0 deductibles. Backed by our recent $150M in Series B funding and valuation at $1.275B, Curative is scaling rapidly and investing in AI-powered service, deeper member engagement, and a smart network designed for today’s workforce. Our north star guides everything we do: healthcare only works when people can actually use it. That belief drives every decision we make: from how we design our plan, support our members, to how we collaborate as a team. If you want to do meaningful work with a team that moves fast, experiments boldly, and cares deeply, Curative is the place to do it. We’re growing fast and looking for teammates who want to help transform health insurance for the better. Summary We are hiring a forward deployed software engineer to be the technical owner of our care coordination platform — the system our clinical care navigators and clinicians use every day to support the members who need us most. You will sit at the intersection of engineering and clinical operations — embedded with the people who use the software, not insulated from them. You will join clinical team meetings, hear directly what is broken, and ship the fix the same week. You will also be the person watching the dashboards — tracking operational metrics, spotting patterns in how the platform is actually used, and adjusting based on what the data says, not what anyone assumed. You will be the single technical point of responsibility for this service. You will partner with product and clinical stakeholders to turn workflows into shipped software, set the architectural direction, own production, and represent the platform in cross-team discussions. How we build At Curative, AI writes most of the code. Engineers direct it. We use agentic AI coding tools as the primary development surface. A senior engineer here routinely runs multiple agents in parallel — one implementing a feature, one resolving review comments, one chasing down a flaky test. The engineers job is to set context, make the decisions the AI can't make, and keep the bar high on what ships. This is not a role for someone who wants to hand-roll every line. It is also not a role for someone who will accept whatever the AI produces. We are looking for the engineer in between: strong enough fundamentals to catch a wrong answer in a few seconds, disciplined enough to review every diff, and ambitious enough to drive several times the output of a traditional IC. Strong systems and architecture thinking is important, as is product taste. What you'll own The codebase. A full-stack Python + TypeScript application with significant domain complexity. You own code review, architectural decisions, and the quality bar. Most commits will be AI-authored, human-directed, human-reviewed. All of them are yours. AI leverage. The internal tooling, prompts, skills, and evals that let one engineer operate a service of this scope. You will extend it. Production. Cloud infrastructure, deploy pipeline, observability, on-call, incident response, and cost. Operational metrics. You watch how the platform performs for its users — not just uptime, but workflow completion rates, navigator efficiency, time-to-resolution, and the other numbers that tell you whether the software is actually helping. You surface what the data shows, propose changes, and close the loop. Stakeholder relationships. You are the engineer in the room with care navigators, clinicians, and ops leads. You translate their pain into scope, push back when a request won't solve the real problem, and build trust by shipping reliably. The roadmap. Co-owning the product plan with clinical and product stakeholders. Sequencing work, flagging what is infeasible, proposing alternatives — and sometimes arguing for the thing nobody asked for yet because you are close enough to the problem to see it. Strategy for your surface. You don't just execute a roadmap handed to you — you shape it. You see patterns across clinical feedback, production data, and business goals, and propose what to build next. Integrations. A growing set of connections to other internal services and third-party healthcare systems. The clinical domain. You will not arrive a healthcare expert, but within 90 days you will understand the workflows well enough that every prompt you write is loaded with the right context. What we're looking for Foundational skills (non-negotiable) You need these because you are the last line of defense on what the AI produces. The bar is not "can write it from scratch in an interview" - the bar is "can read a 400-line AI-generated diff and spot the subtle bug in 90 seconds" 5+ years shipping production software. Enough reps that you recognize bad code before you can articulate why. Real fluency in Python and TypeScript. Not "I can read it" — fluent. You will direct work in both every day. Strong SQL and relational database fundamentals. You can read a query plan, spot an N+1, and know when a migration is unsafe at scale. Comfort with operational data. You have built or maintained dashboards, dug into usage metrics to find problems, and used data to argue for or against a product change. Systems thinking. Can sketch a service's architecture on a whiteboard, identify the failure modes, and reason about blast radius. Production cloud experience (AWS, GCP, or equivalent). You have been on-call for something real. Comfort working directly with non-technical stakeholders. You can run a 30-minute workflow review with a nurse navigator, extract the real requirements, and leave them feeling heard — not bulldozed. Sharp written communication. You will spend more time writing prompts, specs, and PR descriptions than writing code. Note: prior healthcare experience is not required. AI-first working style (also non-negotiable) You already use Claude Code, Cursor, Codex, or equivalent as your primary development tool — not as a side autocomplete. You have opinions about how to structure prompts, when to split work into subagents, and how to keep AI output from drifting. You review every AI-generated diff. You do not merge on vibes. You treat the AI as a junior engineer with infinite throughput: high leverage, zero judgment, and needs supervision. You enjoy building tooling that makes AI more effective on your codebase — skills, evals, fixtures, integrations. You see AI leverage as what makes it possible for one engineer to own a full product surface and stay close to users — not as a reason to stay heads-down in a terminal. Strongly preferred A portfolio of AI-assisted work — skills you wrote, agents you built, automations you shipped. Experience being the single owner of a non-trivial service in production. Why this role Healthcare is one of the highest-leverage places software can make a difference, and we are a company where a single engineer can own a service that thousands of members and clinicians depend on. The scope is large, the problems are real, and the operating model — AI-first, human-directed, shipped daily — is the one you have been waiting for. Your day might span sitting in on a clinical case review, debugging a production issue, digging into operational metrics to understand why navigator caseload spiked, demoing a new workflow to an ops lead, or setting the technical strategy for your platform. If you have been looking for a role where you own the full loop — problem discovery through production — and AI-first isn't a buzzword but the actual way work gets done, this is it.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Mid Level
Education Level
No Education Listed