Full-Stack Engineer

About the role

The team builds and scales a healthcare store that simplifies shopping for care.

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 and beautiful consumer healthcare product is shaped through collaboration with design, operations, and clinical stakeholders. SQL is used to analyze feature performance and guide product decisions. QA is owned end to end to ensure releases meet clinical and consumer standards. Multiple tech stacks are worked with so that the engineering velocity and code quality remain balanced.

Requirements

The posting states a bachelor's degree requirement. Two or more years of experience building web apps as a full-stack engineer are necessary. Proficiency in a modern tech stack is required even when it differs from AWS, Ruby on Rails, and NextJS currently in use. The office in Boston or San Francisco is the primary work location. In-office days are required a minimum of 3 days per week, approaching 4 or 5 days when possible.

Practical notes

The team operates with high autonomy and expects ownership across product and technical tasks. Clinical complexity and regulatory realities are navigated on a regular basis. 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 working with price transparency and emerging regulations. Data-driven decisions are supported by direct analysis of feature performance using SQL. Rapid iteration is common while balancing engineering velocity and quality. Generalist engineers write requirements, analyze data, and own quality. Tooling commonly includes cloud infrastructure, modern web frameworks, and database systems.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

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.

About the company

General Medicine is a national, tech-enabled medical group delivering comprehensive adult care through telemedicine. Founded by the innovators behind PillPack (acquired by Amazon Health), we are an early-stage startup building the future of care delivery - we move fast and hire with intention.