Mobile Engineer (SF)

About the role

The role involves building and scaling 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 new mobile application is shaped by defining and iterating on API contracts with product and engineering, and the contract grows as usage increases.

Swift or Kotlin is used when needed for integrations such as HealthKit, push notifications, or video calling SDKs, while most work happens in TypeScript and React.

SQL is written to analyze feature performance, and product requirements documents are authored by the team.

QA is owned end to end, and tasks are not restricted if they help deliver a great product.

Complexities of the American healthcare system, including integrations with EHRs and revenue cycle management, are explored to deliver solutions.

Requirements

The posting states a bachelor's degree requirement. A minimum of 3 years of experience building mobile apps is required, with meaningful production experience in React Native.

Strong understanding of native iOS and/or Android development is required, using Swift or Kotlin comfortably even if not expert in both.

Experience with Expo is required, including build tooling, OTA updates, and native module configuration.

Proficiency with TypeScript and React is required.

Experience architecting shared code between mobile and web codebases is required, with a clear approach or opinion on how to do it well.

Familiarity with modern backend frameworks such as 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

General mobile development patterns are applied in consumer healthcare settings.

The role relies on tools such as React Native, TypeScript, and React.

The field combines engineering rigor with healthcare complexity.

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.