You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Early Window: Closes in
Company hidden

Member of the Technical Staff

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay $135K - 220K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds cybersecurity software for a time when coding agents ship code faster than teams can review it, and 100+ pull requests per engineer per week is no longer unusual.

Attackers now use the same agents to find and exploit weaknesses within days, which makes quarterly pentests and long alert queues ineffective.

The product runs a set of AI security agents that reason over a live graph of production, covering code, CI, cloud, and telemetry, and test a faithful copy of it the way a real attacker would.

Each finding arrives validated, with its blast radius and a fix plan that fits existing workflows and that a coding agent can apply. Integration takes hours, and the first validated finding arrives in days.

The founders previously built a security company that Datadog acquired.

Responsibilities

  • Keep incident response in order: when something breaks, internally or at a customer, contain it quickly and understand it fully.
  • Work on two fronts: respond to incidents at the company itself, where a breach would reach every customer whose code, cloud accounts, and telemetry the agents can access, and teach the agents to investigate like seasoned responders.
  • Within 1 week you could lead a response to a leaked credential, write a detection that would have flagged it a day sooner, and build an eval that checks whether an agent reaches the same conclusion unaided.
  • Work directly with the founders and engineers; your work goes to production.
  • Lead end-to-end response to security incidents at the company: triage, containment, eradication, recovery, then a blameless post-mortem.
  • Build and tune detections across AWS, Kubernetes, GitHub, and identity providers to catch incidents within minutes and keep alert queues short.
  • Write and maintain playbooks for expected incidents such as credential leaks, compromised dependencies, cloud account takeover, and misused agent permissions, and run tabletop exercises against them.
  • Collect and analyze evidence from CloudTrail, VPC flow logs, Kubernetes audit logs, application logs, and endpoints, and build timelines that hold up.
  • Turn your investigation methods into agent capabilities: timeline reconstruction, blast-radius scoping on the live graph, and containment plans that can run right away.
  • Design realistic incident scenarios to test whether agents reach correct conclusions, and convert every miss into a test case.
  • When a validated finding is confirmed as exploited at a customer, help them establish what happened and what to do next.

Requirements

  • You have run serious security incidents from detection through final review, making containment decisions while the wider business was waiting on the outcome.
  • You have investigated real attacks in AWS (IAM, CloudTrail, GuardDuty) and Kubernetes and understand how attackers move through them.
  • You have rebuilt what an attacker did from raw cloud, application, and endpoint logs into a timeline that held up.
  • You have written detections as code that caught real intrusions in a SIEM or log platform such as Datadog, Splunk, Elastic, or Panther.
  • You have written production-quality Go, TypeScript, or Python to automate repeated response work.
  • You have written incident reports and post-mortems that engineers, executives, and customers acted on.
  • You use AI coding agents such as Claude Code or Cursor daily and want to see how far autonomous agents can go in defensive work.
  • Certifications such as GCIH, GCFA, GCFR, or GREM are an option, but none is required.
  • Background at an incident response firm, a managed detection provider, or a cloud-native company's CSIRT.
  • Offensive experience such as penetration testing or red teaming, since you know attacker thinking from doing it yourself.
  • Experience investigating on GCP or Azure, with SaaS and identity provider logs (Okta, Google Workspace, GitHub), or with 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.

Conditions

Salary is competitive and set by level and experience.

The role is based in San Francisco and is done in person.

The role shares an on-call rotation, because incidents happen outside office hours.

The team draws people from varied backgrounds and routes into security, which the company sees as strengthening its product and judgment. Applicants who meet only some of the points above are still encouraged to apply.

The company is an equal opportunity employer.

Benefits

  • Early-stage equity: you join early and hold a real ownership share in what gets built.
  • Medical, dental, and vision coverage.
  • The equipment you need to do the work well.

Where you’d work

Part of the week in the office

The office

You can work from

  • United States

About the company

Company hidden

  • Industry: Cybersecurity

Office in San Francisco, United States

Your chances

Still hiring, not crowded yet, and you'd be among the first.

  • 15 checks run
  • 6 good signs
  • 0 red flags

Still hiring?

10 checks

Actively hiring

In its favour2

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence

How crowded?

5 checks

Low

In its favour4

  • In its Early Window: not on the big job boards yetStrong evidence
  • Hybrid in San Francisco: only people nearby can take itSlight evidence
  • Senior level: far fewer people qualifySlight evidence
1 moreFewer
  • Asks for Datadog, which fewer than 1% of open roles doSlight evidence

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details14 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Python
  • Go
  • AWS
  • Kubernetes
  • Azure
  • Datadog
  • Splunk
Seniority
Staff
Type
Full-time
Equity
Equity offered
Industry
Cybersecurity
Specialty
Security
Show 8 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
Security
Seniority
Staff
Experience
6+ years
Tech stack
  • Python
  • Go
  • AWS
  • Kubernetes
  • Azure
  • Datadog
  • Splunk

Location

Work model
Hybrid
Region
United States
Office
  • San Francisco, United States
Remote from
  • United States

Compensation

Salary
Salary by agreement
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Company

Industry
Cybersecurity

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason