We are rebuilding the core infrastructure behind corporate health insurance, everything from care navigation, analytics, claims, and more. Fully cloud-native and AI-first. We are eager to directly impact the health and savings of 60% of the American population.

We are looking to make our first engineering hire. This role reports directly to the CEO and is intended to promote to CTO. We move fast: ex-founders and operators can us within a single day of meeting. If you’re looking for that level of urgency, ownership, and trust, you’ll feel at home here.

Healthcare payments is one of the largest, most broken markets in the world. It’s a $300B+ industry that runs on outdated systems and painful manual work. Providers lose billions every year, and fixing it requires technology that can scale where humans can’t.

We’ve built the foundation and secured partnerships with the three largest law firms in the country. We’re now preparing to deploy across 200 provider groups. The demand is here, the market is massive, and the opportunity to shape the future of healthcare payments is wide open.

This is a true ground-floor role: you’ll be writing code that powers millions of dollars in cashflow for hospitals and physician groups, while shaping the product and culture of the company from day one.

Expect your friends to ask why you’re working so hard—and then ask if they can join.

Role Requirements

• 2+ years of professional software engineering experience
• Full-stack experience with ownership of features end-to-end

Culture-fit Requirements

• Customer-obsessed: care deeply about solving real problems for providers
• Opinionated but convincible: strong views, open to better ideas
• Great taste: in design, code, and product judgment
• Wicked fast iterations: bias toward action and rapid learning
• High trust, high loyalty: thrives in high-autonomy, high-accountability environments
• Mission-driven: passionate about changing healthcare economics

Role Guidelines

• Measure twice, cut once: design features by presenting multiple options before building
• High ownership: run independently and own features end-to-end with minimal guidance
• Comfort with speed: willing to take shortcuts when strategically directed
• Super user: Cursor, Claude Code, Vercel, etc.
• Bonus: background in life sciences, UX, or product design
• Team-builder: help manage and grow an on/offshore team as we scale
• Greenfield builder: design and build products from repo creation
• Data-heavy expertise: skilled at building data-intensive applications

Technical Stack

• Frontend: React, React Router, Tailwind.css, Mantine
• Backend: Node.js + TypeScript (Hono Lambda); Go for heavy I/O
• Infrastructure:
  • Auth: Clerk (moving to Auth.js later)
  • Hosting: AWS, Cloudflare Pages
  • Compute: AWS Lambda, ECS Fargate
  • Storage: S3, DynamoDB, PostgreSQL
  • Analytics: CloudWatch, Metabase

• Frontend: React, React Router, Tailwind.css and Mantine.
• Backend: Node.js + Typescript Hono Lambda. Heavy IO operations will be written in Go.
• Infrastructure:
• Auth: Clerk (we will roll our own using Auth.js eventually)
• Hosting: AWS, Cloudflare Pages
• Compute: AWS Lambda, ECS Fargate (for long running jobs)
• Storage: S3, DynamoDB, PostgresSQL
• Analytics: CloudWatch, Metabase