DevOps / Platform Engineer — Reliability, Performance & Production Ownership

DevOps / Platform Engineer — Fully Remote, Performance & Production Ownership

Want to work fully remotely with real freedom and ownership while operating high-throughput, low-latency systems that serve billions of shoppers?

For the right person, this is a high-trust role where you have flexibility in how you structure your work and the opportunity to make a significant impact on the technology behind billions of e-commerce experiences.

We’re building the infrastructure behind better e-commerce experiences for billions of shoppers every year.

Our systems serve more than 2,000 requests per second. Our in-house search engine delivers a p50 latency of sub-ms, while our entire infrastructure maintains 99.998% uptime.

We work with modern technology, use AI as a fundamental part of how we build, and continuously push the limits of reliability, performance, and innovation. Our goal is simple: connect e-commerce shoppers with the right products at the right time while helping merchants create a better customer experience and improve their bottom line.

We’re proud of the systems we’ve built—and we want someone who is excited to help make them even faster, more reliable, and more capable.

• You enjoy operating high-throughput production systems where latency, reliability, and customer impact matter

• You care deeply about reliability, latency, throughput, and system performance

• You can investigate problems across infrastructure, application code, databases, queues, and networks

• You are comfortable reading, writing, debugging, and optimising production code

• You proactively identify failure scenarios before they become incidents

• You build automation and tooling instead of accepting repetitive manual work

• You enjoy improving CI/CD, infrastructure as code, observability, and developer experience

• You have handled serious production incidents and understand the responsibility that comes with on-call

• You think beyond whether a deployment succeeded and care about how the system behaves afterwards

• You can communicate clearly during incidents and take ownership when things matter

• You are curious about new technology and enjoy finding better ways to build and operate systems

• You want to work closely with software engineers rather than treating infrastructure as a separate world

• You thrive in a remote environment where freedom is matched by responsibility

No two days will be the same, but your work might include:

• Investigating why a service, query, or piece of application code is slower than it should be

• Improving the reliability and performance of systems serving thousands of requests per second

• Reviewing metrics, traces, logs, and alerts to identify issues before they affect customers

• Designing and implementing infrastructure, automation, and internal tooling

• Writing, reviewing, debugging, and optimising production code

• Working with developers to improve how systems are built, deployed, and operated

• Responding to incidents when needed, then making sure the underlying problem is permanently addressed

• Exploring how new technologies and AI-powered tools can improve our engineering workflow

• Thinking proactively about scaling, capacity, resilience, and potential failure scenarios

We’re an AI-first company. AI and agentic coding are already part of how we build, investigate, automate, and improve systems.

You should already be comfortable using AI in your daily engineering workflow—for example, to investigate incidents, generate and review code, build internal tooling, automate operational work, and improve your own productivity.

This role can be fully remote for the right person.

We believe in giving people the freedom to structure their work in a way that helps them perform at their best. We care about impact, ownership, communication, and results—not about watching when or where you work.

You’ll need to work with meaningful overlap during CET working hours and participate in our PagerDuty/on-call rotation. Freedom comes with responsibility, especially when you are responsible for production systems.

If you are scheduled to be on call and a genuine production alarm goes off—whether that is on a normal weekday, Christmas Eve, Christmas Day, New Year’s Eve, or New Year’s Day—you are expected to respond, take ownership, and stay with the issue until our systems are fully up and running again.

This is an important part of the role and is not optional. We are looking for someone who genuinely stands behind their work and understands that production ownership sometimes means being there when things go wrong.

At the same time, your goal is to make this situation as rare as possible. The best engineer is not the person who enjoys firefighting every holiday, but the person who builds reliable systems, strong monitoring, and effective automation so that firefighting is never needed.

Instead of starting with a traditional cover letter, please send us a maximum 10-minute video.

We are hiring a human being—not AI-generated slop, a spotless resume, or someone who simply knows how to present the right keywords. We know the kind of person we are looking for, but the process also needs to be mutual. You should get the opportunity to meet the people behind the company and decide whether this is the right environment for you.

That is why we want to meet you upfront and see how you think, communicate, and explain your experience—not only evaluate what is written on paper.

In the video, please tell us:

• Who you are

• The production systems you have owned

• A difficult reliability or performance problem you solved

• What you changed and the measurable result

• How you approach incidents and on-call responsibility

• How you currently use AI and agentic coding

• Why you believe you would be a strong fit for this role

• What you are looking for in your next team and role

The video does not need to be polished. Please don’t spend time producing a perfect presentation or reading a script. We want to see the real person, understand how you think, and hear about the work you have actually done.

You may also include a short written example of a system that was slow, unreliable, or difficult to operate. Explain how you found the root cause, what you changed, and what improved afterwards.

If you are primarily an infrastructure administrator, this probably isn’t the right role. If you are a production-minded software engineer who enjoys making systems faster, more reliable, and easier to operate, we would love to hear from you.