We're hiring Senior Go Engineers across various teams
You'll be placed where your strengths and interests line up best:
- Order Management - orchestrating the order through its entire lifecycle, from checkout reservation to handoff, keeping state consistent across systems that don't always agree with each other.
- Fulfillment - the pick-and-pack brains behind our warehouses and hubs, plus the integrations with the warehouse and carrier systems that move stock in the real world.
- Logistics - routing, tracking, and delivery, including BashDelivery, our in-house courier.
- Internal Apps (aka “Supply Chain Applications”) - This team builds the front-ends used by store, warehouse, and hub staff, nationwide. As a Go engineer in this team you’ll build backends hand-in-hand with the Flutter engineers building the front-ends.
What you'd actually work on
- Real-time stock and reservation systems where being correct and being fast are both non-negotiable, regardless of the system load. Expect to see thousands of orders per hour.
- Event-driven services that keep order state in sync across warehouses, carriers, and third-party logistics platforms. We use Kafka and Temporal extensively.
- Integrations with messy external systems (couriers, WMS, partners) - the kind that don't have clean APIs and don't care about your sprint.
- Tooling and operational systems that store and warehouse staff actually use every day, so the feedback loop is short and very real. Millions of parcels a year flow through our hubs.
The Stack
- Go is our primary backend language, and we mean it - this isn't a "we have one Go service" job. Around it: AWS, Kubernetes, and a strong observability culture (you build it, you can see it, you own it). Internal tools and admin surfaces are built in Retool, and we plan and track work in Linear. You won't be reaching for new tech for its own sake, but you also won't be fighting a decade of legacy to ship something sensible.
You'll fit well if you have
- 5+ years building production backend systems, primarily in Go (or you're a strong engineer in another language who's genuinely keen to go deep on Go).
- Solid instincts for databases, data structures, and algorithms, and a real interest in distributed systems - consistency, failure modes, and what happens at 2am when one node disagrees with the rest.
- Comfort owning your services end-to-end: writing them, deploying them on AWS and Kubernetes, and being the person who knows how they behave in production.
- A bias toward observability and monitoring - you'd rather know than guess.
- Strong written and verbal communication, because the hard part of Supply Chain is rarely the code in isolation; it's the seams between teams and systems.
- You’re comfortable leveraging agentic coding tools, but you still read and validate everything “you” commit.
- A BSc in Computer Science (or equivalent) is a nice-to-have, not a gate. Strong, demonstrable experience speaks louder.
How we work
We're a cross-functional, Agile team, but we care less about ceremony than about how engineers actually operate day to day:
- You own your work. Senior here means you remove ambiguity from your own tickets, shape the solution, and drive it to done - not wait to be told.
- You build to last. Resilient, maintainable, observable. You hold a high bar on testing and code review, and you lift it by example, so the team ships solutions that don't page anyone six months from now.
- You share the load. That includes pitching in on operational work and an on-call rotation for critical alerts - because the people who built the systems are the people best placed to keep them healthy. We take on-call seriously and we don't make it miserable.
- You build relationships with other engineers, product managers, and the wider org. The best supply-chain engineers are the ones people want in the room.
- You make the team better. Senior is a leadership level here. You mentor without being asked, spot gaps and bring solutions, and set a technical bar others want to meet.