Senior Fullstack Engineer

Senior Fullstack Engineer — Applied AI Claims PlatformSan Francisco · On-site · Full-time$185K–$250K base + 0.1%–0.3% equityThe companyThe company is building applied AI for insurance claims, a workflow where accuracy, auditability, and operational reliability matter as much as model quality.The product is already deployed with large insurers. The business reached multi-seven-figure ARR in less than a year and is growing at roughly 50% month over month.The seed round was 13x oversubscribed and raised $3.8M from Founders Fund and Emergence Capital, led by a partner who was early at OpenAI and Scale AI.The team is small — about 12 people — and unusually dense in technical talent: engineers from DRW, Optiver, AWS, and Palantir; AI researchers from Oxford and Cambridge labs publishing at ICML, ICCV, and NeurIPS; and multiple ICPC and Olympiad winners.The roleThis is a high-ownership fullstack role for someone who wants to work across product, customer integration, and core systems.You will ship to production early, but the expectation is not just speed. You will write specs when they do not exist, implement the system, roll it out with customers, and stay accountable for what happens after launch.This role is closer to senior/staff-scope ownership than to a standard fullstack position. You will be expected to make good technical calls in ambiguous situations and to carry those calls through to production outcomes.The technical problemInsurance claims are not clean software flows.You are dealing with customer-specific rules, exception handling, long-running workflows, manual review steps, changing requirements, and systems that need to work in production from day one.The hard part is not building isolated features.The hard part is building software that can handle enterprise integrations, workflow correctness, product iteration, and operational visibility without turning every customer deployment into a one-off system.What you'll ownEnd-to-end product delivery: take work from problem definition to spec, implementation, launch, and post-launch follow-up.Customer integrations: work directly with insurers to connect workflows, adapt logic to real operating constraints, and iterate based on production feedback.Core application logic: design and ship the systems that determine how claim workflows move, where human review is needed, and how AI fits into the process.Workflow reliability: own the failure modes that matter in production — retries, idempotency, state transitions, observability, and recovery when things go wrong.Data and product consistency: make sure the same underlying data can support customer-facing workflows, internal tooling, and future product surfaces without fragmentation.Infrastructure decisions: help evolve the codebase and deployment model as the company scales, with a bias toward maintainability and clear operational boundaries.Engineering standards: set a high bar for code quality, reviews, and technical judgment in a small team where each decision compounds quickly.Why nowThe company has already proven demand. The next constraint is building a product and engineering layer that can scale across customers without turning every deployment into custom work.That means the most important engineering problems now are reliability, extensibility, and customer integration speed — exactly the problems this role owns.The team is small enough that strong engineers have direct leverage, and the product is early enough that the architecture decisions made now will shape the next several years.Who this is forYou are likely a fit if you have:Owned production software end to end, not just individual tickets inside a larger system.Strong judgment around specs, tradeoffs, and sequencing when requirements are incomplete.Built software that had to work in customer environments, not just in controlled demos.Experience with enterprise workflows, async systems, data modeling, or other reliability-sensitive product surfaces.Comfort debugging issues across application code, integrations, and infrastructure.A preference for direct feedback loops with customers and technical peers over layers of process.The ability to explain why a design choice is worth the complexity it adds.High standards for correctness, clarity, and code quality.This role is not for you ifYou want narrowly scoped tickets with fully written specs before you start.You prefer working only on isolated frontend or backend features.You are uncomfortable owning customer-facing outcomes after launch.You do not want to work directly with enterprise customers when requirements are still moving.You want a role where architecture, reliability, and product judgment are handled elsewhere.Compensation and logisticsBase salary: $185K–$250K, with flexibility for more tenured candidatesEquity: 0.1%–0.3%Location: San FranciscoWork model: on-site, Monday through FridayVisa support: availableEmployment: full-timeInterview processTypical process:Initial screen — 15 min: role fit, scope, and motivation.Live coding — 45 min: practical implementation work.System design — 45 min: architecture, tradeoffs, and reliability.Third technical round — 30 min: deeper dive on execution and judgment.About AuroraAurora helps exceptional engineers find the right role at some of the most ambitious startups worldwide.We work with teams that care about ownership, technical rigor, and clear scope.