Staff Software Engineer

Responsibilities:

• Craft as a discipline. You take pride in the details, naming, structure, and the difference between code that works and code that lasts. You advocate for high-quality engineering not as a luxury but as the thing that lets us move fast for years instead of months. You can articulate why a design is better, not just that it is.
• Architectural judgement. You can hold the whole system in your head and make calls about where complexity should live. You know when to invest in abstraction and when to cut a straight line through. You phase migrations and rewrites so the team keeps shipping the entire time.
• Code review as leverage. You review code that makes the people around you better, specific, kind, and consistently raising the bar. You see review as one of the highest-leverage things a staff engineer does, not as a chore between meetings.
• Project ownership. You take a piece of work from "We should probably do this" through milestones, scope cuts, and the unglamorous middle, all the way to shipped. You communicate status without being asked. You name risks early.
• Direction. You work with users, products, and the CTO to figure out what to build and how to build it. You sit with operators, watch where they get stuck, and come back with a sharper definition of the problem than we started with. You're a thought partner, not someone waiting for a spec and not someone going off in a vacuum.
• Speed. Not crashed-out hustle culture speed. The kind that comes from deleting unnecessary work, making decisions quickly, and not being precious about being wrong.
• Range. You don't need to be a 10/10 at frontend, backend, infra, AI, and product. You do need to be the person on the team who can dive into whichever of those is on fire this week.

Requirements:

• 8+ years building production software, with meaningful time at the senior or staff level. We care about the slope as much as the years you've shipped, what you learnt the hard way, and what you'd do differently now.
• You've lived in TypeScript and Postgres long enough to have real opinions about both, and you've designed systems that other engineers had to live with for years.
• Agentic AI / LLM systems. You've built something with agents, tools, evals, and the unglamorous plumbing around them. You know when an LLM is the right answer and when it's a fancy way to make a slow, wrong API call.
• Early-stage startup experience. You know what it feels like to have no design system, no playbook, no PM, and a customer call in 90 minutes.
• Healthcare / RCM background. You know what a 271 is. You've fought with a clearinghouse. You have feelings about Availity. This is rare, and we'd love to find it, but we'll happily teach the right person.