Member of the Technical Staff, Incident Response Security Engineer
Tolmo · Remote · San Francisco, California · Posted November 19, 2026 (today)
- Remote · San Francisco, California
Job description
About us
Tolmo is cybersecurity for the age of AI. Coding agents now ship software faster than any human team can review or secure it; 100+ pull requests per engineer per week is no longer an outlier, and attackers are using the same agents to find and exploit weaknesses in days, not months. The old playbook of quarterly pentests and endless alert queues breaks at this speed.
We're building a new security playbook. Tolmo runs a fleet of AI security agents that reason over a live graph of your entire production system (code, CI, cloud, and telemetry) and continuously attack a faithful copy of it like a real adversary. Every finding arrives validated, with its blast radius and a remediation plan that lands in your workflow, ready for a coding agent to fix. Hours to integrate, days to your first validated finding.
We've done this before: Tolmo's founders built Sqreen (acquired by Datadog) and led security products that thousands of organizations trusted. We're backed by Accel and Y Combinator and just getting started.
About the role
As a Security Engineer on Incident Response, you make sure that when something goes wrong, at Tolmo or at a customer, it gets contained fast and understood completely. You bring the instincts of someone who has run real incidents, and you turn them into playbooks, detections, and agent capabilities that work at machine speed.
The role has two halves. You own incident response for Tolmo itself: our agents hold access to our customers' code, cloud accounts, and production telemetry, so a breach at Tolmo is a breach at every customer at once. And you teach our agents to investigate like an experienced responder: reconstruct a timeline from cloud and application logs, scope the blast radius on our live graph, and hand back a containment plan a team can act on in minutes.
In one week you might lead the response to a leaked credential, write the detection that would have caught it a day earlier, and build the eval that checks whether an agent reaches the same conclusion on its own. You'll work directly with the founders and our engineers, and your work ships to production.
Responsibilities
- Incident command: lead the response to security incidents at Tolmo end to end, from triage and containment through eradication, recovery, and a blameless post-mortem.
- Detection engineering: build and tune detections across AWS, Kubernetes, GitHub, and our identity providers, so the next incident is caught in minutes and alert queues stay short.
- Readiness: write and maintain playbooks for the incidents we expect (credential leaks, compromised dependencies, cloud account takeover, abused agent permissions), and run tabletop exercises that test them.
- Forensics: collect and analyze evidence across CloudTrail, VPC flow logs, Kubernetes audit logs, application logs, and endpoints, and build timelines that hold up.
- Agent-led investigation: turn how you investigate into capabilities our agents use: timeline reconstruction, blast-radius scoping on our live graph, and containment plans ready to execute.
- Evals: design realistic incident scenarios that measure whether our agents reach the right conclusion, and turn every miss into a test case.
- Customer incidents: when a validated finding turns out to have been exploited, help the customer scope what happened and what to do next.
Required qualifications
- You've personally led serious security incidents from first alert to post-mortem, making containment calls while the business waited on you.
- You've investigated real attacks in AWS (IAM, CloudTrail, GuardDuty) and Kubernetes, and know how an attacker moves through them.
- You've reconstructed what an attacker actually did from raw cloud, application, and endpoint logs, in a timeline that held up.
- You've written detections as code that caught real intrusions, in a SIEM or log platform such as Datadog, Splunk, Elastic, or Panther.
- You've written production-quality code (Go, TypeScript, or Python) to automate the parts of response you'd otherwise repeat.
- You've written incident reports and post-mortems clear enough that engineers, executives, and customers acted on them.
- You build with AI coding agents daily (e.g., Claude Code, Cursor) and want to see how far autonomous agents can take defensive work.
Preferred qualifications
- Certifications like GCIH, GCFA, GCFR, or GREM. None are required.
- Experience at an IR consultancy, an MDR provider, or on a CSIRT at a cloud-native company.
- Offensive background (penetration testing, red teaming): you know how attackers think because you have been one.
- Experience with GCP or Azure investigations, SaaS and identity provider logs (Okta, Google Workspace, GitHub), or supply-chain incidents.
- Experience building or evaluating LLM agents, or applying machine learning to detection.
- Familiarity with SOC 2 and ISO 27001 incident-management requirements.
Compensation
- Competitive salary, depending on level and experience.
- Early-stage equity: you're joining early; you'll own a real piece of what we build.
- Comprehensive medical, dental, and vision coverage, and the equipment you need to do your best work.
- Based in San Francisco; we work in person. Incidents don't keep office hours, so this role shares an on-call rotation.
Tolmo is building a team with wide-ranging backgrounds, perspectives, and paths into security; we think it makes our product and judgment better. If you're excited about this role but don't match every point above, we'd still like to hear from you. We're an equal opportunity employer and welcome applicants of every background.
Posting 384d10c4-f1ac-452c-a7c8-9209c84df7b6 on ashby. Source: the employer’s listing. Valid through January 3, 2027 unless closed earlier.