Senior Software Engineer

• →

  5+ years building production web applications, with deep TypeScript, React, and Node experience. Next.js is a strong plus.

• →

  Comfort across the stack: relational data modeling (we use Prisma and Postgres), auth flows, caching, background jobs, and cloud deployment (AWS, Docker, Terraform or similar).

• →

  A real testing habit at every layer: unit, component, and end-to-end. We use Vitest, Storybook, Cypress, and Playwright.

• →

  Strong product judgment and the ability to work directly with design, clinical, and partner-facing teammates.

• Daily, expert use of agentic coding tools such as Claude Code, Cursor, or Codex. You write project instructions and reusable skills for your agents, hand them multi-step tasks, and review the output like a senior reviewer, not a rubber stamp.

• Hands-on experience shipping LLM features: prompt design and versioning, structured outputs, tool/function calling, streaming UIs, retrieval-augmented generation, and multi-turn conversation state.

• You've run evals and traced production LLM traffic (LangSmith, Braintrust, Langfuse, or homegrown), and you can explain what changed the last time a model version bumped underneath you.

• You understand the cost, latency, and quality triangle and have made real trade-offs: model selection, caching, prompt compression, and fallback strategies.

• Clear-eyed about limits. You know when an LLM is the wrong tool, how to constrain one when it's the right tool, and how to keep a hallucination from ever reaching a member.

• Healthcare, benefits, or other regulated-data experience (HIPAA, SOC 2).

• Building MCP servers or internal agent tooling for a team.

• Experience with Clerk, Stripe, or Sentry.

• Contributions to AI developer tooling, open source or internal.

AI is part of our engineering culture, not a side experiment. Our repository ships with agent configuration, we maintain shared skills for code review and security checks, and we expect engineers to spend more of their time on judgment and less on typing. We also expect the opposite discipline: no unreviewed AI-generated code lands, and "the agent wrote it" is never an explanation for a bug.