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
Cantina

Staff Product Security Engineer

  • Remote
  • 6+ years

Salary

$200,000 - 250,000/ year

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 is building an agentic security operating system that covers application security, security operations, and agent security.

The team believes security products should understand context, reason across systems, help teams investigate what matters, and take action safely. Building that means working closely with the people who will use the product and learning from how their environments actually run.

Customer systems you may recognise include SIEM and detection tools such as Splunk, Elastic, Microsoft Sentinel, Google SecOps / Chronicle and Panther; EDR and XDR tools such as CrowdStrike Falcon, SentinelOne and Microsoft Defender; SOAR tools such as Tines, Torq and Cortex XSOAR; and AppSec and exposure tools such as Semgrep, Snyk, CodeQL, Burp Suite and Wiz. Experience with every one of these is not expected. What matters is that you have worked close enough to real security operations to understand the trade-offs in those workflows.

The company's primary stack is TypeScript / Node.js. You must be willing to work in it, and prior experience is preferred.

The role sits in the Product team and is a staff-level position. It is not a consulting, solutions engineering or generic backend role.

Responsibilities

  • Work directly with customer security teams to learn how they triage alerts, investigate incidents, prioritise vulnerabilities and handle other recurring work.
  • Design, build, test and refine agents around those workflows, and help customers put them to use.
  • Connect agents to security tools, data sources and operational systems, and handle permissions, context, approvals and the edge cases that appear in production.
  • Take work from discovery through to adoption: prototype quickly, check output with practitioners, measure whether it helps, and iterate until the workflow is reliable.
  • Turn what you see in customer environments into product insight, spotting common needs, platform gaps and chances for reusable tools, integrations, workflows and agent capabilities, and bring recommendations into product planning.
  • Work with product and engineering on solutions, contribute to architecture and implementation, and ship platform features yourself when that is the best answer to a recurring problem.
  • Help set guardrails, evaluation, observability, execution limits and human oversight for agents that act on security data and systems.
  • Use your security judgment to find failure modes, attacker opportunities and operational risks in unclear decisions.
  • Explain technical trade-offs clearly to customers and the product team, and turn scattered feedback into actions.

Requirements

  • Essential: deep hands-on experience in at least one of security engineering, security operations, detection engineering, incident response, application security or security platform engineering.
  • Essential: strong software engineering skills. You can build, integrate, debug and ship working systems, not only advise others on how to build them.
  • Essential: strong, hands-on experience building LLM and agent systems. You have implemented agentic workflows that use tools, APIs and real-world context, and you know how to test, evaluate and improve their reliability beyond prompts and demos.
  • Essential: you use LLMs and AI agents regularly in your own work, including engineering and problem solving. You know where they help, where they fall short, and how to work with them well.
  • Essential: you are comfortable working directly with customers and practitioners. You ask good questions, earn technical trust and help solve loosely defined problems.
  • Essential: product judgment. You can tell a one-off customer request from a reusable capability and make pragmatic trade-offs.
  • Essential: ownership and comfort with ambiguity. You move easily between a customer's workflow, a prototype and a conversation about what the platform needs next.
  • Valuable, but not all required on day one: experience in a forward-deployed, customer-embedded or early-stage product engineering role.
  • Valuable, but not all required on day one: experience with TypeScript / Node.js or a similar backend stack.
  • Valuable, but not all required on day one: experience with detection engineering and KQL.
  • Practical experience matters more than expertise in any particular model or framework. You should already have built with LLMs and agents, not be starting from zero.

Where you’d work

Fully remote

You can work from

  • United States

About the company

Cantina

  • Industry: Cybersecurity

Also hiring in Los Angeles, United States and San Francisco, United States

2 of their 8 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 21 checks run
  • 0 red flags

Still hiring?

14 checks

No red flags

How crowded?

7 checks

No red flags

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
Details11 facts · Role, Location, Compensation, Company
Tech stack
  • Splunk
Seniority
Staff
Industry
Cybersecurity
Specialty
Security
Region
United States
Pay period
Annual
Show 5 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
Security
Seniority
Staff
Experience
6+ years
Tech stack
  • Splunk

Location

Work model
Remote
Region
United States
Remote from
  • United States

Compensation

Salary
$200,000 - 250,000 / year
Pay period
Annual

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