At a Glance
- Tasks: Keep our platform fast and secure while scaling to millions of executions.
- Company: Join a cutting-edge developer platform focused on AI agents and workflows.
- Benefits: Enjoy competitive pay, flexible remote work, generous vacation, and a training budget.
- Other info: Be part of a small, autonomous team that values continuous learning and community contributions.
- Why this job: Make a real impact in a fast-paced startup environment with a focus on open source.
- Qualifications: Experience in distributed systems, observability, and cloud-native technologies is essential.
The predicted salary is between 70000 - 90000 £ per year.
About Trigger.dev
Trigger.dev is a developer platform for building and running AI agents and workflows. We provide everything needed to create production-grade agents: an SDK, deploying, scaling, monitoring, and debugging them without needing to manage any infrastructure. Our Cloud product is a managed service where we deploy our users' code and auto-scale from zero to millions of executions. Today, we serve thousands of teams building AI apps and agents, handling hundreds of millions of executions per month.
About the position
We're hiring a Senior Site Reliability Engineer to keep Trigger.dev fast, observable and hard to break as we scale. You'll work across our open source codebase and the Cloud product that runs it in production. We're handling hundreds of millions of executions a month on infrastructure we run ourselves, and the next order of magnitude needs someone who thinks in distributed systems and treats observability and security as part of the product, not bolted on later.
Day to day you'll be chasing bottlenecks, hardening services like the sandbox runtime that executes untrusted user code, and making the platform legible to the engineers running it at 3am.
What you'll be doing
- Owning observability across the platform. Extending our OpenTelemetry instrumentation, sanding down noisy signals, and making metrics, logs and traces something engineers actually reach for during incidents.
- Designing and operating the distributed systems primitives we lean on (queues, schedulers, checkpoints, idempotency, backpressure) under real production load.
- Architecting and tuning the auto-scaling infrastructure that runs untrusted customer code at high throughput.
- Hunting bottlenecks across the stack, from Postgres query plans and Redis hot keys down to kernel, cgroup and network behaviour.
- Hardening the security posture of our multi-tenant runtime: sandbox isolation, secrets handling, network policy, supply chain.
- Owning Terraform and IaC as the source of truth for our cloud-native footprint, rather than an afterthought.
- Working on runtime internals: CPU/RAM snapshotting, cold-start optimization, live migration between hosts, resilient distributed file storage.
- Designing and running our on-call practice: runbooks, SLOs, blameless postmortems, paging hygiene.
- Making the rest of engineering faster and safer by keeping the platform easy to reason about.
- Contributing to architectural decisions and the technical roadmap.
We build in public, so you can see some of the things you might work on here.
Working at a Commercial Open Source Software company is more than just coding:
- We have an active community on Discord and GitHub. Everyone on the team helps customers, reviews PRs, and creates issues.
- Having great documentation is essential. Everyone writes docs.
- We're a product-led growth company, so everyone is expected to get involved in creating content like code examples, blog articles, videos, and tweets.
Requirements
You really need to have:
- Strong observability chops. Production experience with OpenTelemetry, Prometheus or equivalent, and opinions about cardinality, sampling and signal-to-noise.
- Distributed systems experience. You've designed or operated systems with non-trivial failure modes (queues, consensus, replication, idempotency).
- Cloud-native fluency. Comfortable in the CNCF orbit (Kubernetes, OTel, Argo, Crossplane, eBPF) rather than wedded to any one tool.
- Self-managed Kubernetes in production, not just clicking around managed control planes.
- Performance and scaling debugging instincts. You've chased real bottlenecks across application, database and infrastructure layers.
- Terraform fandom. IaC as a first principle, with experience running it at meaningful repo and team scale.
- Security mindset. Multi-tenant isolation, least privilege, secrets management, threat modelling.
- Expertise with Postgres and Redis under load.
- Experience with Go.
- Familiarity with Linux.
- Cloud infrastructure experience. AWS strongly preferred, GCP/Azure considered.
- OK with being on call and understanding reliability is a shared responsibility for the engineering team.
You'll be an amazing fit if you have:
- Experience running container orchestration at scale (cold starts, pod density, scheduler tuning, IP exhaustion, image pull optimization).
- Worked with MicroVMs (Firecracker, gVisor) or other sandbox runtimes for executing untrusted code.
- Demonstrated system scaling and performance optimization on high-throughput platforms.
- A proven track record of contributing to open source projects, especially in the observability or cloud-native ecosystem (OTel collector, Prometheus, Grafana stack, k8s operators).
- Expertise in Node.js and TypeScript (we use Remix), enough to land changes in our application code, not just the infrastructure around it.
- Experience with React, or better still, Remix.
- Designed SDKs for developers.
- Worked at a developer tools company or commercial open source company.
- You've previously been a venture-backed startup founder.
About the team
We are a small team with a flat hierarchy. We encourage continuous learning and personal development. Everyone operates autonomously; we trust you to get the job done, but to also quickly raise your hand if you need help. We care about our customers and the open-source community. Being a start-up, the work is challenging and fast-paced, but we also understand the importance of taking time off to recharge.
Salary
We use PostHog's salary calculator to benchmark fair and transparent compensation which varies based on employee location and level of experience (this role falls under "Backend engineer").
Benefits
- Generous, transparent compensation and equity - We hire the best talent and pay to reflect that. We also offer equity as a way to ensure everyone is invested in the success of the company.
- Async working - Need a heads-down day or meeting-free days to stay productive? No problem!
- Home office - We will help provide equipment for a comfortable setup so you're as productive at home as you are in the office.
- Generous vacation - We believe it's important to take time off. We encourage you to take your 25 days vacation excluding national holidays, plus sick leave and generous parental leave.
- Training budget - An annual budget to contribute towards learning such as purchasing books, an Audible subscription or online courses.
- Pension and 401k contributions - Enroll in our company pension scheme or we'll contribute directly to your private pension.
Our values
- We are proud to be open source - We believe in the open source community and building a great free-to-use product. We encourage community contributions and are public about what we are building.
- We ship uncomfortably fast - As a startup, moving fast is key. We are pragmatic about what we build, when we build it, and value iterative development above all.
- Working autonomously - We don't tell you what to do. We decide as a team what will have the biggest impact for our customers and prioritise what we work on from that.
Interview process
- Application. We'll review your application, CV, and any code samples or open source contributions you share.
- Screening call. A chat about your background, the systems you've built, and what you're looking for next.
- Hiring manager call. A deeper technical conversation about your work and how you'd approach the role.
- Paid task day. You'll spend a paid day working on a real engineering problem with us, then walk us through your thinking with the team.
- Final interview. A call with a couple of members of the wider team to answer any remaining questions and align on culture fit.
- References & offer. If everyone is happy, we'll make you an offer to join us.
If this sounds like your dream job, we can't wait to hear from you. If you're not sure that you exactly fit these requirements, get in touch anyway!
Senior Site Reliability Engineer (Europe) employer: Trigger.dev
At dev, we pride ourselves on being an exceptional employer that fosters a collaborative and innovative work culture. As a Senior Backend Engineer, you'll have the opportunity to contribute to meaningful open-source projects while enjoying generous benefits such as a transparent compensation structure, a supportive home office setup, and a dedicated training budget for your professional growth. Our commitment to employee well-being is reflected in our flexible vacation policy and emphasis on continuous learning, making dev a rewarding place to advance your career in a thriving tech environment.
StudySmarter Expert Advice🤫
We think this is how you could land Senior Site Reliability Engineer (Europe)
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Trigger.dev or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Trigger.dev.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Trigger.dev.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Trigger.dev that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Senior Site Reliability Engineer (Europe)
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Trigger.dev.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Trigger.dev and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Trigger.dev
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Trigger.dev uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.