Frontend Engineer (Boston)

About the role

The team builds and scales a healthcare store that simplifies shopping for care. This role owns major surfaces of a Next.js application, including search, scheduling, provider profiles, and checkout. The work focuses on delivering a polished, seamless patient experience.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

A component architecture guides the implementation of search, scheduling, provider profiles, and checkout to serve the patient journey. Details of UI polish and the patient experience are refined to meet product expectations.

A data model informs frontend interactions with RESTful APIs so product behavior remains consistent and reliable.

Performance, accessibility, and cross-browser compatibility are optimized to support a broad and diverse user base.

The product integrates with external systems such as EHRs and revenue cycle management to handle the complexities of American healthcare.

Full-stack tracing connects frontend behavior to the Rails backend, enabling the diagnosis of issues and the delivery of features end-to-end.

Product requirements documents describe features and logic, and SQL queries analyze how features perform in practice.

Quality assurance is owned end-to-end, including tests and manual validation, to ensure releases meet standards.

The roadmap balances engineering velocity against quality under significant ambiguity, requiring rapid yet careful execution.

Generalist problem solving spans product, operations, and clinical stakeholders to advance shared outcomes.

Requirements

The posting states a bachelor's degree requirement. 3 or more years of experience building production web applications with React.

Strong proficiency in TypeScript and modern React patterns, including server components, hooks, and data fetching.

Experience with Next.js or a similar framework, covering routing, SSR/SSG, API routes, and caching strategies.

A keen eye for UI quality, noticing small inconsistencies such as padding misalignment.

Proven experience with frontend performance optimization, accessibility, and cross-browser compatibility.

Comfortable reading and working with RESTful APIs and understanding backend data models.

Familiarity with Ruby on Rails and Postgres is a plus.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Building consumer healthcare products involves navigating complex regulations and real-world care workflows.

The role relies heavily on React, TypeScript, and Next.js within a modern web stack.

Engineers operate in fast-paced, high-ambiguity environments and must switch between frontend and full-stack contexts.

Technical excellence and rapid delivery are balanced through ownership of product requirements and quality.

The product leverages price transparency and emerging technology to reshape healthcare shopping experiences.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.