Overview
Own application security at Trigger.dev across infrastructure, the app, the runtime that runs users' code, and the secrets customers entrust to the platform. This is a product engineering role, with roughly half to three quarters of time spent on backend engineering.
What you'll do
- Design and harden the sandbox and runtime environments that isolate untrusted user code (core of the role).
- Build security features for customers, such as end-to-end encrypted secrets, log redaction, private networking, and runtime hardening.
- Use AI tools to attack Trigger.dev's own systems on a schedule, find weak spots, and fix them; bring in outside pen testers when worthwhile.
- Build monitoring and alerting for suspicious activity, improve security observability, and lead response when something needs a look.
- Run vulnerability scanning and triage, own the vulnerability disclosure program, and handle incoming reports.
- Own security PR reviews, automated scans, fixes, and triage.
- Document how security is done so the team can answer customer questions with confidence.
- Help the engineering team build secure habits through reviews, docs, and light guardrails.
- Help in the Discord and GitHub community, write docs, and create content such as blog posts, code examples, and videos.
What you'll need
- Senior backend engineer who designs and ships production backend systems.
- Hands-on application security experience, such as secure code review, threat modelling, pen testing, CTFs, or bug bounties (no security job title or security team leadership required).
- Experience running production systems in the cloud.
- Experience building or securing multi-tenant systems where many customers share infrastructure.
- Comfortable working in TypeScript (codebase also uses Go and Rust).
- Uses AI tools to automate testing, detection, and defense.
- Has worked at a startup a step or two ahead of Trigger.dev's stage, knowing what good looks like at its size.
- Owner's mindset: takes work off the team's plate and fixes what they find.
- Participates in the shared on-call rotation for reliability and security response.
- Open to team events a few times a year, in person.
Nice to have
- Built or hardened sandboxes using containers, microVMs, gVisor, Firecracker, WASM, or similar.
- Secured platforms where customers have their own customers.
- Track record in bug bounties or CTFs.
- Contributed to open source.
- Worked at a developer tools, infrastructure, or open source company.
- Experience with Go or Rust.
Details
- Location: Remote or Hybrid, UK.
- Occasional in-person team events (a few times a year).
Read the full description and apply on the company’s own careers page.