Senior Software Development Engineer

About the role

The position is based in Mountain View, California, and requires five days onsite per week.

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

Core commerce primitives are defined through API endpoints for Merchant, Resource, Discount, and UseCase to serve internal applications and external developers.

An API-first, platform-first codebase is shaped through collaboration with Staff and Principal engineers to ensure scalability, extensibility, and security.

Clear API documentation and developer-facing resources are created to enable consistent integration for internal and external teams.

Code reviews and team standards are contributed to uphold engineering excellence and surface risks early.

Requirements

A Bachelor's degree in Computer Science or a related field is required as the baseline education.

6+ years of backend software engineering experience focused on customer-facing products and API development is required.

5+ years of experience in modern languages such as Java, Ruby, Go, or Python with proven ability to build RESTful APIs and distributed systems is required.

Strong understanding of API design, versioning strategies, and contract-first development practices is required to reduce integration issues.

Familiarity with cloud platforms, infrastructure-as-code tools, and modern CI/CD pipelines is required to accelerate delivery.

Working knowledge of identity and access management standards such as OAuth 2.0, OpenID Connect, or SAML is required to align with platform protocols.

Experience with monitoring, logging, and observability tools such as Prometheus, Datadog, or similar is required to maintain reliability.

Experience building high-reliability systems focused on performance, fault tolerance, and operational excellence is required.

Exposure to multi-tenant SaaS architectures or identity-powered commerce platforms is required to accelerate context transfer.

Practical notes

This is a full-time, in-office role in Mountain View, California, requiring five days onsite per week unless otherwise noted for specific exceptions.

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

Identity and access management principles underpin secure, scalable digital ecosystems.

Modern distributed systems rely on observability and automation to achieve reliability at scale.

API-first design enables interoperability and faster integration for internal and external consumers.

Cloud infrastructure and CI/CD practices support frequent, low-risk changes to production services.

Roles in identity platforms often collaborate across multiple product and engineering teams to deliver cohesive experiences.

Continuous learning helps professionals keep pace with evolving standards and tools in identity and commerce.

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.