Software Engineer: Full Stack

Role overview A full stack engineering role focused on building software that supports employer-funded health benefits and gives employees more control over how they use their coverage. The work spans both user-facing interfaces and backend services that power onboarding, benefits management, and payments—territory where financial accuracy and healthcare clarity matter just as much as engineering quality. Teams are organized around the people they serve, so engineers own end-to-end experiences and ship with both speed and accountability.

Responsibilities - Own meaningful product areas from early concept through production deployment - Build features across the entire stack, including user interfaces and backend services - Translate real user and business needs into pragmatic technical solutions - Maintain high standards for code quality, system design, and product polish - Take responsibility for production reliability, debugging, and ongoing improvement - Balance shipping speed with correctness and long-term maintainability

Requirements - Experience building and shipping production web applications across the full stack - Strong product judgment and comfort navigating ambiguity - Ability to reason about complex systems and business logic - Familiarity with modern engineering tools and frameworks - Demonstrated ownership, cross-functional collaboration, and sound technical decision-making - Engineering experience at multiple levels, with emphasis on scope owned, impact delivered, and decision quality

Nice to have - Background in healthcare, finance, or other regulated domains - Experience with HR, payroll, payments, or partner-facing systems - Ownership of systems with real operational or financial impact - Prior Ruby on Rails experience (helpful but not required) - Comfort with React and TailwindCSS on the frontend, plus Python or backend JavaScript where appropriate

Benefits and work setup - Hiring process is structured to be rigorous yet efficient, typically completed within three weeks - Stages include an initial recruiter conversation, a collaborative pair programming session, a systems design interview paired with an engineering culture conversation, and a final discussion with engineering and company leadership - Engineering culture emphasizes action, early shipping, learning from real usage, trust, ownership, empathy, clarity over ceremony, and quality over shortcuts