Lead Product Reliability Engineer (Product Reliability) in London

Requirements

• The work in this role is what we call crunchy. Feature engineering is creative, there's rarely one right answer. Product reliability engineering is different: there is a right answer, and you need to find it fast, with deep knowledge of how systems behave under pressure.
• Solid TypeScript. Expert level. If you don't have this, you shouldn't apply. You need to be fluent enough to diagnose and fix a production incident fast. In an outage, someone who can't read the code can't help solving the issue.
• Serious cloud experience. Google Cloud or equivalent, at depth. Deployments, scripts, GitHub workflows, operational tasks. The kind of engineer who knows not just how to use a cloud platform but how to architect around its constraints.
• Deep database knowledge. Not just querying, but designing. Understanding the database design options available and how to find the most effective solution, then justifying that against any questions.
• Production ownership. When something breaks, you're the one who fixes it. We need someone who's been in that seat before and knows how to stay calm, move fast, and make sure it doesn't happen again.
• Fullstack capability. You'll be designing and building features alongside our product engineers, ensuring you support the development of new features from a reliability perspective.
• Genuine obsession with learning. Everyone says this. We mean it differently. The best person for this role goes home and thinks about the problem. They build tools to understand their own gaps. We look for a deep, self-driven obsession with learning and technical craft, and people who get uncomfortable when they stop growing.

What the job involves

• Reporting to: Founding Engineer, Josh Harrison.
• We're hiring a Lead Product Reliability Engineer to sit within our platform team, a small, high-ownership group responsible for the infrastructure and services that keep Fyxer running as we scale, including taking ownership for billing, integrations with third-party apps, uptime and incident response.
• This isn't a ticket-execution role. You'll own the reliability standard for the whole company: what good infrastructure looks like, what it takes to ship safely, and how incidents get resolved and don't repeat.
• You'll work across the full stack, from cloud architecture to database migrations, using deep technical knowledge and sound judgement to keep a fast-moving product on solid ground.
• Plan and execute infrastructure migrations, the kind where the wrong call takes the product down.
• Be the last line of defence when things break: diagnose it, fix it, and make sure it doesn't happen again.
• Use quantitative data (error logs, cloud metrics) and qualitative data (support tickets, user reports) to identify the highest-leverage reliability improvements.
• Build and maintain the scripts, workflows, and cloud architecture that the product runs on. This is a full-stack engineering role, not just configuration of tools. You'll ship code.
• Work closely with product engineers to review new features before they ship, ensuring they meet the reliability bar before they reach production.
• Own the reliability standard across your product area, so new features and onboardings don't break what's already working.

Some examples of what the team has achieved in the past months to get a taste:

• Migrated our billing structure in Stripe from a subscription model to usage-based billing, from technical specification through to implementation, with zero downtime.
• Redesigned the entire webhook architecture behind our Outlook integration to completely eliminate rate limiting, changing a core part of the product without any downtime.