Dashboard
Checked on their board 15 Nov

Tolmo Hiring now

Member of the Technical Staff, Security Engineer

AI agents that hunt bugs in live systems. You'd research how systems break and teach the agents to attack.

San Francisco, CAHybridFull-timePosted 12 days ago
Who to email about itThe Head of Engineering at TolmoTheir email address, hidden
Apply on Ashby ↗

We find the person most likely hiring for it, check their work email, and write yours in your voice. Free to try: paste your LinkedIn and this role comes first.

About the role

From Tolmo's posting on Ashby, as they wrote it

About Tolmo

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.

The role

As a Research Engineer on Offensive Security, you make our agents attack like the best human red teamers, and then better. You'll research how real systems get broken, turn that knowledge into techniques, tools, and evaluations our agents can use, and prove it against real customer environments.

This sits between research and engineering. In one week you might reproduce a new exploit class, teach an agent to chain an SSRF into cloud credential access, build the harness that checks whether it actually got there, and review the findings it files for a customer. You'll work directly with the founders, our engineers, and the security leads who run pentests with our agents, and your work ships to production.

What you'll do

  • Exploit research: study techniques across web applications, APIs, cloud (AWS, GCP, Azure), CI/CD, and identity, and turn them into capabilities our agents use in the field.
  • Attack-path discovery: work out how individually minor weaknesses chain into real impact, and encode that reasoning over our live graph of code, cloud, and telemetry.
  • Red-team tooling: build the scanners, probes, sandboxes, and exploitation helpers our agents call while they work.
  • Evals and benchmarks: design environments, including intentionally vulnerable targets, that measure whether our agents find, exploit, and validate real vulnerabilities, and keep false positives out.
  • Field validation: review agent findings from customer engagements, and turn every miss into a test case and an improvement.
  • Staying ahead: track new CVEs, exploitation research, and attacker tradecraft, and get them into the product within days.

What we're looking for

  • Deep hands-on offensive security experience: penetration testing, red teaming, exploit development, or vulnerability research.
  • A track record that shows it: CVEs, bug bounty results, CTF wins, published research, or talks.
  • Strong engineering skills: you write production-quality code (Go, TypeScript, or Python) and build tools other people rely on, not just one-off scripts.
  • Solid understanding of modern application and cloud architectures and how they fail: auth, access control, SSRF, injection, misconfigured IAM, exposed secrets, supply chain.
  • You build with AI coding agents daily (e.g., Claude Code, Cursor) and are curious about how far autonomous agents can take offensive work.
  • Sound judgment about safety and scope: you know how to test production-like systems without causing harm.

Nice to have

  • Certifications like OSCP, OSEP, OSWE, or CRTO. None are required.
  • Experience building or evaluating LLM agents, or applying machine learning to security problems.
  • Cloud security depth: privilege escalation in AWS, GCP, or Azure, Kubernetes, and container escapes.
  • Experience on an internal red team or at a security consultancy.
  • Contributions to open-source offensive tooling.

Compensation & benefits

  • 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.

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.

Live on Tolmo's board as of 15 Nov. We check it every day.

Apply on Ashby ↗

Tracking Tolmo

Applying to Tolmo? Email the person hiring instead.

Free to try: see the roles that fit you and who's hiring for them. No sign-up to start.

The company

About Tolmo

Tolmo is building a team with wide-ranging backgrounds, perspectives, and paths into security; we think it makes our product and judgment better.

Tolmo writes email addresses like jane@tolmo.com (a made-up name). How we know

More roles at Tolmo

Similar roles

Tracking Tolmo

Get roles like this one the day they're posted

A role stays uncontested for about four days. Here's the window, and where we put you in it.

Free to try: see the roles that fit you and who's hiring for them. No sign-up to start.

  1. LiveWatching Tolmo0 applicants
  2. Same dayRead off their careers page~2 applicants
  3. Next morningIn your matches, with who's hiring~5 applicants
  4. Day 2You've emailed them~8 applicants
  5. Day 7+Hits the job boards250+ applicants