Software Engineer (Senior)

About the role

This role focuses on building and operating healthcare billing products at scale. The team delivers core infrastructure and user-facing features while balancing speed and reliability. Success depends on cross-functional collaboration and clear communication.

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

Complex services and platforms are conceptualized, designed, developed, and maintained, with ownership extended over large parts of product and infrastructure. Each feature or component is delivered end to end, ensuring it meets customer needs and supports scalable, reliable performance.

Solutions are designed to address these needs in creative and practical ways.

Decisions on scope and tradeoffs align with customer outcomes and system constraints.

Engineering practices and the broader company culture are strengthened, with contributions aimed at making the workplace one where the team can perform at their best.

Requirements

A Bachelor of Science or Bachelor of Art in Computer Science, Computer Engineering, Math or a similar degree is required.

At least 8 years of experience in a software engineering role is required.

Experience across programming languages, relevant frameworks, databases, and cloud platforms is required.

The ability to build high-quality software is anchored in customer outcomes and sound judgment about scope and technical debt.

Ownership of features from conception through launch is demonstrated, including comfort moving across the stack and learning new tools.

A customer-first mindset and a drive to continuously learn and teach others are required.

Strong communication skills enable clear explanation of complex ideas in both verbal and written formats.

Practical notes

The role is based in San Francisco and requires compliance with any applicable onboarding or security requirements. Employment eligibility and background checks may apply. 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

Roles in this field often involve distributed workflows across product, design, and operations.

Cloud platforms, container orchestration, and modern web frameworks are common tools in this type of role.

Clear communication and concise documentation support alignment in fast-moving engineering organizations.

Continuous learning and peer feedback help maintain high standards for software quality and user impact.

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.