Marketplace Org

Zipline•South San Francisco, CA

1d•Hybrid

About The Position

You are hiring into the Senior Software Engineer, Commerce Platform role on Zipline’s Commerce Platform team. This team builds the commercial engine that turns Zipline’s delivery network into a scalable business: merchant-facing portals and integrations, marketplace policy and dispatch logic, fulfillment tooling at partner locations, and the billing/settlements backbone that must be financially correct across promotions, refunds, revenue shares, and taxes. These systems run live against real missions—affecting partner operations, customer experience, and cashflow—and must operate across metros and countries with strict safety, reliability, and financial correctness constraints. This hire will be an owner/operator: shipping core services, owning production reliability and incident response, and moving product and architecture forward in a regulated, hardware-integrated logistics environment. Location: hybrid (primary office [location placeholder] + regular on-site with partner pilots and field ops); role may require multi-day travel to partner sites and occasional weekend or evening production support during launches.

Requirements

Minimum 5+ years building and shipping production distributed systems and web applications, with demonstrated ownership across frontend, backend, and data/streaming pipelines (or comparable scope if title differs).
Experience shipping transactional commerce, payments, billing, or marketplace systems in production at scale (millions of orders per day or multi-region transactional volume), or equivalent experience operating financial reconciliation and settlements pipelines.
Strong systems engineering skills, including production-grade API design, data modeling for ledgers, eventual consistency tradeoffs, schema migrations, and designing for idempotency and retry semantics.
Demonstrated incident leadership, including on-call experience, runbook authorship, post-incident root cause analysis, and driving remediation to prevent recurrence.
Proven ability to define, measure, and achieve key operational metrics, including reconciliation accuracy, onboarding time, MTTR, throughput, and latency targets, while communicating tradeoffs using data.
Deep proficiency in Go, Python, or other scalable backend programming languages, with experience using React or similar frameworks for merchant-facing applications.
Familiarity with Kafka, gRPC, PostgreSQL, AWS, observability tools (Grafana and Honeycomb), and build tooling such as Bazel.
Ability to support occasional off-hours launches and urgent production incidents, with availability for regular multi-day travel to partner sites (approximately 20%) and hybrid work near the primary office.
Strong attention to correctness and edge cases in financial systems, a bias for measurable ownership and accountability, and the ability to simplify complex cross-functional systems into durable abstractions.

Responsibilities

Own one or more production services end-to-end in the commerce stack (merchant portal, partner integrations, marketplace platform, billing engine, fulfillment apps, or support tooling), including design, implementation, rollout, and ongoing operations.
Deliver measurable improvements, such as reducing merchant onboarding time by 50% within 6 months for assigned flows, bringing reconciliation variance below 0.1% month-over-month for owned payment paths, and reducing incident-driven customer-impacting downtime to under 30 minutes MTTR for priority services.
Lead cross-functional launches by defining success criteria, authoring rollout and rollback plans, coordinating with Field Operations, Safety/Compliance, Product, and Finance, and owning post-launch remediation and success metrics.
Build and enforce marketplace controls and policy tooling that enable operators to safely manage pricing, capacity allocation, and prioritization, including feature gates, experiment scaffolding, and pre-production simulation using historical mission data.
Ship partner integrations (POS connectors, APIs, and data feeds) with clear SLAs, backpressure handling, and schema/version migration strategies, while serving as the technical lead for critical partner onboarding and incident response.
Maintain observability and service reliability by defining SLOs, building monitoring and dashboards (Grafana/Honeycomb), and owning alerting thresholds, runbooks, and on-call rotations for assigned services.
Mentor engineers, lead architecture reviews, and make durable abstraction decisions that reduce cross-product fragmentation.