
Site Reliability Engineer
PaddleWhat do we do?
Paddle offers digital product companies a completely different approach to their payment infrastructure. Instead of assembling and maintaining a complex stack of payments-related apps and services, we’re a Merchant of Record for our customers. That means we take away 100% of the pain of payment fragmentation. It’s faster, safer, cheaper, and, above all, way better.
We’re backed by investors including KKR, FTV Capital, Kindred, Notion, and 83North and serve over 6000 software sellers in 245 territories globally.
The Role:
As a Site Reliability Engineer, you’ll be helping to drive our product and engineering department forward, ensuring reliability on different parts of the Paddle platform and helping our Engineers to work better and more efficiently.
Paddle SRE team’s role is “Everything SRE”, with a focus on infrastructure, reliability standards, and practices. The SRE team is part of the Platform function. By following this model:
It’s easy to spot patterns and draw similarities between services and projects.
We act as a glue between disparate product teams, creating solutions out of distinct pieces of software.
Enable product engineers to use DevOps practices to maintain user-facing products without divergence in practice across the business.
Define production standards as code and work to smooth out any sharp edges to greatly simplify things for the product engineers running their services.
You are empowered to use the right tech for the job. You’ll have the freedom to input into what technology and tooling are used and educate the rest of your colleagues accordingly.
As an SRE, we want you to be a driving force of improving and automating how our product teams develop software at all stages of its lifecycle, which we strive to achieve with strong collaboration and communication with our fellow engineers.
Tech Stack:
Go for our new services
PHP Laravel for our Classic system
Aurora MySQL and PostgreSQL for persistent data storage
Docker in production and local development
AWS ECS Fargate for our runtime
AWS SQS for asynchronous message queues
AWS EventBridge for our event bus
Redis for key/value store
Terraform for resource management
Honeycomb, SLOs and OpenTelemetry for our observability needs
Cloudflare for our firewall and DNS server
What you'll do:
Develop and maintain tools to maximise engineering efficiency; such as but not limited to automating deployment infrastructure and database upgrades
Seek out processes that can be improved with automation and have internal Developer Experience as a main driver. Collaborate and enable engineers to do their jobs more efficiently, working with other engineers on a regular basis
Create, maintain and test our system disaster recovery process, including tooling to automate the process
You’ll be able to choose from a selection of AI tools to support day-to-day work (e.g. code generation, investigation, automation, and documentation), and we’ll back sensible experimentation with the right guardrails.
Handle production incidents, author blameless postmortems and enrich operational playbooks and runbooks
Monitoring, alerting, and SLO tracking; hands-on SRE work, not just DevOps-style monitoring
Run performance investigations (load testing, bottle
Similar roles
Design & Tech
Related reads from TCHNX

The Quiet Revolution in Local-First Software
As major platforms face outages and data breaches, a new generation of developers is building applications that prioritise local data storage and peer-to-peer sync, challenging the cloud-first orthodoxy that's dominated tech for two decades.

The Quiet Revolution in Edge AI: Why Your Next Computer Might Not Need the Cloud
As neural processing units become standard in consumer devices, we're witnessing a fundamental shift in how AI applications work. Local processing is no longer a fallback; it's becoming the preferred architecture.

The Rise of AI-Assisted Code Generation 2: Are Developers Becoming Prompt Engineers?
As AI coding assistants reshape software development, the industry grapples with a fundamental question: is writing code giving way to writing prompts? We examine how London's tech scene is adapting to this seismic shift.


