Software Engineer

Forward Deployed Software EngineerCurative 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 health plan Finance and Accounting (F&A) platform — the brains of Curative's financial operations. It's a deeply data-intensive application: it pulls large volumes of financial data from many sources, transforms and reconciles it, and turns it into the accurate analysis the business depends on. You will sit at the intersection of engineering and F&A operations — embedded with the people who use the software, not insulated from them. You will join the F&A team's working sessions, hear directly where the numbers don't line up, and ship the fix the same week. You will also be the person watching the data — tracking where our system and the source of truth disagree, and chasing down why. A big part of the job is building AI agents that take work off people's plates — handling incoming support and billing questions, and automating the manual, repetitive processes the F&A teams run. You will be the single technical point of responsibility for this service. You will partner with F&A and product stakeholders to turn their workflows into shipped software, set the architectural direction, own production, and represent the platform in cross-team discussions.How we buildAt Curative, AI writes most of the code. Engineers direct it. We use agentic AI coding tools as the primary development surface. Most engineers 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. This is a fully remote positionWhat you'll ownThe 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.Agents that do the work. You will design and ship AI agents that handle support and billing issues and automate the manual processes the F&A team runs by hand today — turning recurring, tedious work into software that runs itself. This is some of the highest-leverage work on the platform, and it's yours to own end to end.The data. This platform lives and dies on its data — moving it from many sources, transforming it correctly, and keeping it trustworthy. You own the pipelines that feed it and the checks that catch a bad number before anyone downstream sees it.Financial correctness. The numbers this platform produces have to be right. You own the logic and the safeguards that make the output something the business can rely on and stand behind.Production. Cloud infrastructure, deploy pipeline, observability, on-call, incident response, and cost — including the data jobs the F&A team depends on running on schedule.Sensitive data. This platform touches both PHI and financial information. You own handling it responsibly, with data-privacy discipline baked in rather than bolted on.Operational metrics. You watch how the platform performs for its users — not just uptime, but whether the numbers reconcile, how much manual work the software is or isn't eliminating, and where the data says something is off. You surface what the data shows, propose changes, and close the loop.Stakeholder relationships. You are the engineer in the room with accountants and F&A 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 F&A 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 stakeholder feedback, the data, and business goals, and propose what to build next.Integrations. A growing set of connections to internal services and third-party financial systems that this platform reads from and writes to.The domain. You will not arrive an expert in health-plan finance, 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)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.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, and reason carefully about the joins and aggregations that decide what a number ends up being.Experience building data-intensive applications. You have built systems that move, transform, and reconcile meaningful volumes of data — ETL/sync pipelines and the interfaces on top of them — and you care about getting the data right, not just moving it.A correctness mindset. You have built systems where the output has to add up, and you instinctively reach for the checks, invariants, and audit trails that prove a number is right rather than just plausible. You are comfortable with the idea that "close enough" is not close enough.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 an accountant, extract the real requirements, and leave them feeling heard — not bulldozed.An interest in working with financial data. You don't need a finance background, but you should be genuinely interested in the problem space — financial data, the systems that produce it, and the satisfaction of making the numbers come out right.Sharp written communication. You will spend more time writing prompts, specs, and PR descriptions than writing code.Note: prior healthcare or finance experience is not required. We care far more about your track record building and operating data-intensive systems where correctness matters — any industry counts. What we do look for is an interest in working with financial data and the discipline that comes with it.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, needs supervision.You enjoy building tooling that makes AI more effective on your codebase — skills, evals, fixtures, integrations.