At a Glance
- Tasks: Build secure systems for running untrusted user code at scale.
- Company: Join Trigger.dev, a leading platform for AI agents and workflows.
- Benefits: Enjoy generous vacation, training budget, and flexible working arrangements.
- Other info: Collaborative culture with opportunities for personal and professional growth.
- Why this job: Make a real impact in security while working with cutting-edge technology.
- Qualifications: Experience in backend engineering and a passion for offensive security.
The predicted salary is between 63000 - 77000 £ per year.
About us
Trigger.dev is the platform for running reliable AI agents and workflows. Developers use it to build, deploy, and scale production systems with built-in tools for orchestration, scheduling, monitoring, and debugging. 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 looking for a backend product engineer who loves security - not a security box-ticker. You'll build and own the systems that let Trigger safely run massive volumes of untrusted user code inside our infrastructure, at scale. Some of our customers let their own users run untrusted code on top of Trigger - think coding agents executing arbitrary instructions. We have to guarantee that code can never break Trigger's systems, or our customers' systems. That makes this partly a product engineering role: building secure sandbox runtimes is a feature we ship, not something bolted on after the fact.
The ideal person here is a backend engineer with genuine offensive-security instincts - someone who naturally gravitates toward hacking, pen testing, and breaking things, and brings that curiosity into how they build. You'll pair strong backend/product instincts with a hacker's mindset.
What you'll be doing
- Sandbox and runtime security. Designing and maintaining the secure execution environments that isolate untrusted user code - the core, product-shaped problem at the heart of this role.
- Threat detection and incident response. Building monitoring and alerting for suspicious activity, and leading the response when something needs investigating.
- Vulnerability management, end to end. Regular scanning and triage, plus AI-assisted security scans run on a quarterly cadence, and triaging incoming disclosures.
- Offensive security. Running internal, AI-assisted pen testing, and potentially bringing in external firms for deeper engagements.
- PR security review. Adding a security-specific review layer on top of our normal PR process.
- SOC 2 and compliance. Mostly done already - this is about ongoing maintenance, not standing it up from scratch.
- Vulnerability disclosure process. Owning our vulnerability disclosure program end to end.
- Security culture. Helping the wider engineering team build secure habits - reviews, documentation, and pragmatic guardrails rather than heavy process.
Working at a Commercial Open Source Software company is more than just security work:
- 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
- Real backend engineering experience. You can design and ship production backend systems, not just audit someone else's.
- Genuine offensive-security curiosity. Pen testing, CTFs, bug bounty hunting, or hacking as a hobby or discipline - this isn't a checklist role.
- Comfort owning ambiguous, product-shaped security problems. Sandboxing and runtime isolation are engineering problems as much as they are security ones.
- A proactive mindset. This role should take work off the team's plate, not create a queue for others - we're not looking for a security box-ticker.
- Comfortable being on call. Reliability and security response are shared responsibilities across the team.
- Open to in-person events throughout the year. If you're remote, we'll arrange these so the team gets real time together.
You'll be an amazing fit if you have:
- Experience building or hardening sandboxed/isolated execution environments (containers, microVMs, gVisor, Firecracker, WASM sandboxes, or similar).
- A track record in pen testing, bug bounty programs, or CTFs.
- Experience using AI-assisted tooling for security scanning or workflows.
- A proven track record of contributing to open source projects.
- Worked at a developer tools, infrastructure, or open source company.
- Experience with Node.js and TypeScript, enough to read and review application code.
Benefits
- Generous, transparent compensation and equity - we hire the best talent and pay to reflect that. We also offer equity so everyone is invested in the company's success.
- Async working - need a heads-down day or meeting-free days to stay productive? No problem!
- Home office - we help provide equipment for a comfortable setup so you're as productive at home as you are in the office.
- Generous vacation - 25 days vacation excluding national holidays, plus sick leave and generous parental leave.
- Training budget - an annual budget to contribute towards learning, such as books, an Audible subscription, or online courses.
- Pension 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 ship uncomfortably fast - as a startup, moving fast is key. We are pragmatic about what we build, when we build it.
- 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 from that.
Backend Engineer (Security) 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 Backend Engineer (Security)
✨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 Backend Engineer (Security)
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.