Skip to main content

Staff Software Engineer – Marketplace

Posted today

ziplineMillbrae (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: In this role you will own and evolve core services in Zipline’s Commerce Platform, turning the delivery network into a scalable business. You’ll work across merchant portals, partner integrations, billing, and fulfillment tooling to ensure reliable, compliant, and measurable outcomes. You’ll collaborate with Field Ops, Safety, Product, and Finance to launch and sustain high-impact commercial capabilities. This is a chance to shape tradeoffs in a regulated, hardware-connected logistics system at speed and scale. Compensation / Benefits medical, dental and vision insurance paid time off equity compensation discretionary annual or performance bonuses remote/onsite options and hybrid work overtime/pay flexibility
Responsibilities: Own end-to-end production services in the commerce stack (merchant portal, partner integrations, marketplace platform, billing engine, fulfillment apps, or support tooling) Deliver measurable improvements (e.g., onboarding time, reconciliation accuracy, MTTR) Lead cross-functional launches with clear success criteria and rollout plans Build marketplace controls and policy tooling for pricing, capacity, and prioritization Ship partner integrations with SLAs and incident response leadership Maintain observability and reliability with SLOs, dashboards, and on-call processes Mentor engineers and lead architecture reviews to reduce cross-product fragmentation
Key requirements: 5+ years building and shipping production distributed systems and web applications Experience shipping transactional commerce, payments, billing, or marketplace systems at scale Strong systems skills in API design, data modeling for ledgers, eventual consistency, migrations, idempotency Incident leadership: on-call, runbooks, post-incident analysis Ability to define and hit metrics and present data-driven trade-offs Proficiency in Go, Python, or scalable backend languages; React experience; familiarity with Kafka, gRPC, PostgreSQL, AWS, Grafana, Honeycomb, Bazel ownership and accountability data-driven decision making cross-functional collaboration Go Python React

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this