Staff Software Engineer

Who you are

• Staff-level delivery. 7+ years building and operating production backend or distributed systems, with demonstrated ownership of architecture and delivery across services and teams
• Developer platform experience. Experience building developer platforms, SDKs, or internal tooling used by other engineers to ship production software, ideally for external API integrations. You treat API usability, documentation, and compatibility as part of the product
• Distributed systems depth. Strong skills in API design, data modeling, asynchronous workflows, schema evolution, eventual consistency, and idempotent processing
• Reusable integration design. Ability to turn varied external APIs into reusable connector patterns with clear boundaries and testable contracts, including experience with automated integration testing and development environments
• Production accountability. Demonstrated production ownership, including observability, on-call support, incident investigation, and improvements that prevent recurring failures. You can show how your work improved reliability or reduced integration effort
• Hands-on engineering depth. Deep proficiency in Go, Python, or a comparable backend language, with experience building libraries, command-line tools, or developer workflows that make other engineers productive
• Frontend SDK judgment. Experience building or supporting frontend libraries, SDKs, or embedded customer experiences, with the ability to reason about client-side integration, authentication, error handling, and usability in partner apps
• Leadership across teams. Define architecture and engineering standards across distributed engineering teams, enable independent execution through documentation and technical review, and align Product, Commercial, Finance, and Operations around platform priorities
• Partner and product judgment. Communicate clearly with external engineering teams, turn ambiguous business needs into practical technical plans, and balance enterprise launch commitments with reusable platform investments
• Thoughtful AI adoption. Use AI tools to improve implementation, testing, debugging, and review while taking responsibility for correctness, security, and maintainability

What the job involves

• As a Staff Software Engineer, you will own the technical direction of Zipline’s integrations platform as a hands-on individual contributor
• You will shape the architecture and roadmap across teams, build production software, and enable engineers to deliver partner API integrations
• You will create frontend and backend SDKs that enable partners to build great customer experiences in their own apps, alongside reusable connector patterns, development environments, and automated quality checks that help engineering teams build reliable integrations independently
• Initial applications include POS and order-aggregation connectors, menu synchronization, and merchant workflows
• Your work will help unlock enterprise deals with major clients by making it easier to integrate with Zipline and launch reliable delivery experiences at scale. You will combine hands-on engineering with architecture and technical leadership, shortening the path from signed partnership to production launch and building a platform that supports Zipline’s commercial growth
• Enable partner experiences. Build frontend and backend SDKs that enable partners to build great customer experiences in their own apps, along with the integration framework, connector templates, and developer tooling to deliver partner API integrations quickly and consistently
• Set the platform architecture. Define clear interfaces between partner-specific connectors and Zipline’s core platform, keeping order lifecycle, authentication, authorization, data mapping, and monitoring consistent. Establish API and SDK versioning and compatibility practices so partners can adopt changes safely
• Make development self-service. Create sandbox environments, partner API simulators, and automated contract tests so engineering teams can develop and validate integrations independently
• Make launches repeatable. Establish integration acceptance criteria and automated release checks that verify correctness, failure handling, and operational readiness before production rollout
• Simplify onboarding. Build documentation, reference implementations, and onboarding workflows that reduce developer ramp time and enable integrations to be completed with minimal support from core engineers
• Keep integrations reliable. Establish consistent retry, idempotency, and fallback behavior across partner APIs and webhooks. Define service reliability goals and own monitoring, runbooks, incident response, and remediation for integration failures
• Build for lasting scale. Evolve partner and partner-site data models to support long-term finance and operations requirements, making architecture decisions that reduce partner-specific workarounds
• Multiply engineering impact. Lead technical reviews and mentor engineers; use recurring implementation issues to improve the framework. Measure developer ramp time, integration delivery time, review effort, production defect rates, and SDK adoption to guide investment
• Guide enterprise launches. Work directly with partner engineers, Product, and Commercial to translate enterprise requirements into a platform roadmap, resolve technical blockers, and shorten the path from signed deal to production launch