Senior Frontend Engineer: Web Platform & UX Architect

About the Role

We are looking for a Senior Frontend Engineer who wants to own the web surfaces that members and operators interact with every day. This is a senior individual contributor role ideal for someone with 3 to 5+ years of experience who cares deeply about UI quality, performance on real-world devices and networks, and the craft of shipping product.

You will own the frontend architecture across three Next.js applications: our member onboarding flow, our BYOD enrollment experience, and our internal admin surfaces. You will work alongside the Head of Engineering, product, design, and operations to translate company goals into interfaces that work reliably for low-income Americans on Medicaid and Medicare, many of whom rely on us as their primary connection to the internet.

As one of our first in-house senior engineers, you will help shape engineering practices, frontend architecture, and the hiring bar as we grow.

This is a role for someone ready for meaningful scope, autonomy, and impact in a mission-driven company.

What You'll Do

Build and ship

• Contribute hands-on across our three Next.js frontends (member onboarding, BYOD enrollment, admin) while establishing long-term engineering foundations.
• Own development across our core frontend stack:
• Next.js (App Router, server components, middleware) and React
• Type Script across the application and shared library layer
• Sanity CMS for content-driven UI
• Auth0 for member and operator authentication
• Build offline-resilient experiences that hold up on poor or intermittent connectivity — service workers, optimistic updates, retry logic, and graceful degradation are first-class concerns, not polish at the end.

Design and own

• Drive the architecture of our shared component library so changes propagate cleanly across all three apps.
• Set the standard for performance, accessibility (WCAG 2.1 AA), and UX polish — loading states, error handling, and edge cases are part of the definition of done.
• Author architecture decision records and component guidelines as you go — we believe institutional knowledge belongs in the repo, not in people's heads.

Collaborate and execute

• Partner with product, design, and operations to turn goals into actionable roadmaps.
• Work alongside our backend engineers to design the contracts between frontend and API — you will have a voice in how data flows reach the client.
• Drive UX and engineering decisions that balance speed with the kind of quality our members deserve.

Strategize and improve

• Set the bar for code review, testing discipline, frontend observability, and release practices as the team grows.
• Improve developer experience across the frontend codebases — linting, formatting, CI/CD, and tooling are part of the role.
• Identify opportunities to streamline how we ship features without compromising reliability.

About You

Experience and skills

• 3–5+ years building and owning production web applications, with a portfolio of work you can walk us through end to end.
• Deep React and Next.js experience — you have opinions about hooks, server components, routing, middleware, and SSR/ISR patterns, and you can defend them. You know when to reach for a server component and when a client component is the right call.
• Strong Type Script fundamentals — types serve the design, not the other way around.
• Proficiency with:
• React, Next.js (App Router), and modern React patterns
• Type Script across application and shared library code
• Shared component libraries and monorepo tooling (Turborepo, Nx, pnpm work spaces, or similar)
• Tailwind, CSS-in-JS, or modern CSS architecture patterns
• Modern testing tools (Vitest, Playwright, Testing Library)
• Experience building for unreliable networks — service workers, optimistic updates, retry logic, queueing, and graceful offline states.
• Coding standards as a default, not a phase-two — opinionated about linting, formatting, PR review culture, and automated testing.
• Accessibility as a first-class concern — WCAG 2.1 AA is a launch criterion, not a backlog item.
• Nice to have:
  Sanity CMS or headless CMS rendering, Datadog for frontend observability, Auth0 on the frontend, Figma-to-code fluency, full-stack experience (NestJS, Node.js, Next.js API routes),…