Principal Engineer

• Typescript, Python, and/or Rust in production
• A shipped record of brownfield modernization — strangler migrations, context extraction, boundary enforcement in CI
• Durable-execution engines and event-driven systems with schema governance
• Eval frameworks, LLM observability, and MCP
• A background in insurance or other regulated categories

• You have shipped domain-driven design, not just read about it: a bounded-context map you drew and then enforced, an anti-corruption layer that saved a migration, a hexagonal refactor that survived contact with a deadline — and you know when the pattern is overkill.
• You are at home in more than one language ecosystem — e.g., systems-level work in Rust or a peer language, large-scale strictly-typed TypeScript, etc. — and you know which discipline each one demands.

• You have built and operated agent systems in front of real users — tool contracts, capability boundaries, approval gates — and the machinery that makes them trustworthy: eval gates, provenance capture, autonomy expanded through earned evidence rather than optimism.
• Frontier models are daily instruments in how you build, and “the model can probably do this” is a hypothesis you test with an eval, not a hope you ship on.

• You have run infrastructure other people depend on: infrastructure-as-code at organization scale, GitOps, container orchestration, secrets, observability-as-code — and a pager you did not hand back.
• You treat delivery machinery — CI/CD, environments, releases — as a product with users, and you can argue a migration in cost and risk rather than tool preference.

• You reason in writing. ADRs, design docs, review comments — decisions here live in documents, and you make arguments better by writing them down.
• You multiply rather than add. The measure of this seat is what the engineers and agents around you can safely do a quarter after you arrive.
• You have experience in and passion for early-stage startups and/or high-growth environments

(Please note these steps may vary slightly depending on the role)

• 30-minute phone call with our recruiting team
• 30-45 minute video interview with the hiring manager
• Case study/technical screen
• Meet the team! 30-45 min 1:1 video discussion with 3-4 team members you’d work closely with in the role
• Executive chat