Skip to main content

Staff Software Engineer – Integrations Platform

Posted today

ziplineMillbrae (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: As Staff Software Engineer, you own the technical direction of Zipline’s integrations platform and contribute as a hands-on leader. You shape architecture, deliver production-grade software, and empower engineers to build partner API integrations. You’ll create frontend and backend SDKs and reusable patterns to accelerate partner integrations at scale. This role sits at the core of expanding enterprise partnerships and delivering reliable delivery experiences globally. Your work enables faster, safer integration launches and long-term platform growth. Compensation / Benefits equity compensation medical, dental, and vision insurance paid time off performance bonuses overtime pay sales incentives
Responsibilities: Define platform architecture and interfaces for partner connectors and Zipline core, ensuring consistent order lifecycle, auth, data mapping, and monitoring Build and maintain frontend and backend SDKs and integration framework to accelerate partner API integrations Create sandbox environments, simulators, and automated tests to enable self-service development Establish integration acceptance criteria and automated release checks for production readiness Develop onboarding workflows, documentation, and reference implementations to reduce ramp time Ensure reliable integrations through consistent retry, idempotency, and fallback behavior across APIs and webhooks Define data models and architecture decisions to support long-term finance and operations requirements Lead technical reviews, mentor engineers, and measure metrics to drive platform investment Collaborate with Partner, Product, and Commercial teams to translate enterprise needs into a platform roadmap Guide enterprise launches by shortening the path from signed deal to production rollout
Key requirements: 7+ years building and operating production backend or distributed systems with architecture ownership Experience building developer platforms, SDKs, or internal tooling for external API integrations Strong API design, data modeling, asynchronous workflows, schema evolution, eventual consistency, and idempotent processing Ability to create reusable connector patterns with clear contracts and automated integration testing Proven production ownership including observability, on-call support, incident investigation, and reliability improvements Proficiency in Go, Python, or similar backend languages; building developer tools and workflows Experience building frontend libraries/SDKs and reasoning about client-side integration and usability Leadership across distributed teams; setting architecture and engineering standards Excellent communication with external engineering teams; translating business needs into technical plans Thoughtful AI adoption to improve implementation, testing, and debugging while upholding security and maintainability collaboration communication leadership Go Python API design

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