Member of the Technical Staff, Security Engineer
Tolmo is hiring a Member of the Technical Staff, Security Engineer for a remote role open to applicants in United States. Level rates it ; you can apply on Tolmo.
Level's read on this job
- On Level's scale, this cybersecurity role is Works on AI ●●●○: the daily work is on AI products, without building the model.
- The posting lists this role as remote.
- Tools and skills the posting cites include Claude, Cursor and Claude Code.
- Level lists 4 other open roles at Tolmo.
- The role was posted within the past week.
AI in this role
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.
How we rate this
Member of the Technical Staff, Security Engineer at Tolmo rates 63 out of 100 for how much of the daily work is AI. That makes it Works on AI (AI Level 3 of 4). The level is about AI in the job, not seniority.
Works on AI. The daily work is on AI products, without building the model.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Pay
- Typical cybersecurity job
- $160k
This posting doesn't list pay. Use the typical cybersecurity figure when pay comes up. See cybersecurity jobs
Questions you could be asked
- How do you decide when an AI agent can act on its own versus asking for approval first?
- Walk me through how you've used Claude in your day-to-day work.
- What are the limits of Cursor that you've run into, and how did you work around them?
- What's a project where you used Claude Code hands-on?
- Describe a typical day in a role like this one: which parts run through AI directly?
Adapt your resume
- List these exact terms on your resume: AI agents, Claude, Cursor, and Claude Code. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Show where AI is part of your daily process, not a one-off project. This role expects it to be a running habit.
Get your CV reviewed before you apply
Send your CV and the role you want next. Your review arrives by email within 3 days.
Get new remote cybersecurity jobs (Works on AI ●●●○ or higher) by email
One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free.
Similar roles
Security roles that work on AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step