Share this job
Forward Deployed Security Engineer (Clarion)
United States
Apply for this job

About Cantina

Cantina is building an agentic security operating system spanning application security, security operations, and agent security.

We believe security products should do more than aggregate alerts or automate isolated tasks. They should understand context, reason across systems, help teams investigate what matters, and safely take action. Building that kind of product means working closely with the people who will use it, and learning from the messy realities of their environments.


The Role

We're hiring a Forward Deployed Security Engineer to own our customers' technical health from onboarding onward, and to build what keeps them getting value.

You'll sit on Cantina's go-to-market team and join each customer during onboarding. From there, youll partner with the customer to identify their evolving use cases and work to streamline those workflows within the product.

This is an engineering role. You'll tune agents to each customer's environment, keep integrations healthy, and write the code a customer needs when configuration isn't enough. It isn't a support queue.


What You'll Do

  • Join each new customer during onboarding. Learn their environment and what they need from the product, and own the account's technical health from there.
  • Tune agents to the environment. Cut noise, adjust agents, skills, monitors and rules, and keep triage accurate as the customer's stack changes.
  • Keep integrations healthy. Watch the connections to EDR, SIEM, cloud and identity tools, and catch a broken or silent one before the customer does.
  • Stay close to every account. Run regular technical check-ins, notice when usage drops, and work closely with account managers to keep customers getting value.
  • Be the technical escalation for account managers. Answer customers' technical questions, work issues through to a fix, and close the loop with the customer.
  • Feed what you learn back to sales. Tell the GTM team which use cases hold up after onboarding and which fade.


What You'll Build

You write code. Most of what you build lives in customer workspaces, and the rest feeds the product.

  • Custom agents and skills for workflows a customer needs that the defaults don't cover.
  • Integrations and data mapping for the tools each customer runs, including fixes where a vendor's API misbehaves.
  • Scripts and internal tooling that make onboarding, tuning and health checks repeatable across accounts.
  • Reusable fixes, with product. When a need shows up across customers, you bring it to the product team, and where a fix belongs in the core platform, you can help build it.


Who You'll Work With

You'll work day to day with our sales and account management teams, and closely with product and engineering on anything that belongs in the platform.


Why This Role Is Different

You'll own real customer outcomes and have the engineering room to deliver them. You'll see firsthand where security teams lose time, build what fixes it, and help shape what the product does next.

Success means customers' agents keep doing real security work long after onboarding, and what you learn shows up in the product.


What You Bring

Essential

  • Hands-on experience in security operations, detection engineering, incident response or security engineering. You've tuned detections and triaged real alerts.
  • Enough software engineering to build and debug working integrations, agents and scripts on your own.
  • Hands-on experience building with LLMs and agents that use tools, APIs and real-world context. You know how to test them and make them more reliable.
  • You use LLMs and AI agents in your own day-to-day work.
  • Comfort working directly with customer security teams. You earn technical trust, explain trade-offs plainly, and run a check-in without a script.
  • Ownership of a set of accounts. You follow up without being chased and notice when one goes quiet.
  • The judgment to tell a one-off customer need from a reusable product capability.


Valuable, but not all required on day one

  • Experience in a forward-deployed, customer-embedded or post-sale engineering role at a security vendor
  • TypeScript / Node.js or a similar backend stack
  • Detection engineering and query languages such as KQL or SPL
  • Familiarity with how crypto and Web3 companies run security operations
  • Experience at an MDR or managed security provider, working across many customer environments at once
  • Previous experience at an early-stage startup


Relevant Background

You'll likely recognize some of the systems our customers run:

  • SIEM and detection. Splunk, Elastic, Microsoft Sentinel, Google SecOps / Chronicle, Panther, or similar
  • EDR and XDR. CrowdStrike Falcon, SentinelOne, Microsoft Defender, Huntress, or similar
  • Cloud and identity. AWS, Okta, Microsoft Entra, Google Workspace, or similar
  • SOAR and automation. Tines, Torq, Cortex XSOAR, or similar
  • AppSec and exposure management. Semgrep, Snyk, CodeQL, Burp Suite, Wiz, or similar

We don't expect experience with every tool. We care that you've been close enough to real security operations to know what a noisy queue costs a team.


Technical Environment

  • TypeScript / Node.js is our primary stack. You'll read it daily and write it when a fix calls for it.
  • Agents, skills, monitors and rules configured in the platform and tuned per customer
  • APIs and integrations connecting multiple security platforms
  • Agent evaluation, guardrails and human approval for actions on customer systems


Apply for this job