Travel Expect regular onsite work with customers. Travel is an expectation and critical to this role. The Role Forward Deployed Security Engineers (FDSEs) embed directly with enterprise security teams. The work is turning legacy AppSec noise into a clear plan. What is exploitable in this environment. What matters most. What to fix first. How to keep that posture current as AI and agent-led development reshape the threat picture. You own the engagement end-to-end. From connecting the first repos and building the initial threat model, through prioritization, remediation support, and final delivery to the CISO. The customers you work with have real backlogs, real board pressure, and limited confidence in what their existing tools are telling them. This is not a demo role and it is not a CSM role. You go deep in the code, run working sessions with AppSec teams, validate fixes as they land, and own the technical and executive output. You are also the tightest feedback loop into our product and research teams. What you see in the field is what shapes Enclave next.

What You'll Do

Lead discovery with enterprise AppSec, product security, and security engineering teams. Understand their stack, constraints, existing tool sprawl, and the risk picture leadership is actually being asked about. Connect repos to Enclave and drive the initial threat model. Key assets, risky flows, likely attack paths. Run working sessions to triage findings, prioritize by real exploitability in the customer's environment (not CVSS theater), and support remediation alongside their engineers. Validate fixes as they land. Confirm what worked. Flag what is still open. Capture where Enclave's findings are clear, useful, confusing, or missing context. Drive deeper research alongside our researchers. Chase code paths around known findings and surface issues earlier tooling missed. Own the final delivery. Produce a CISO-ready report that frames posture, residual risk, and next steps in business terms. Plus an updated AI-ready threat model the customer's team can keep using. Be the feedback loop into product. Push what you learn back into Enclave's roadmap and research agenda. Confusing findings, missing context, workflow friction, new threat patterns. Set up customers for the next phase. Successful engagements convert into broader rollouts. You are the technical owner of that path. Get onsite working with customer face to face. Travel is an expectation and critical to execute in this role. You May Be a Fit If You have worked in application security, product security, offensive security, or security engineering. You can read code in at least a couple of major languages well enough to reason about exploitability, not just severity. You have built or owned threat models for real production systems. You know the difference between a finding that matters and a finding that just exists. You are comfortable in ambiguity. There is no playbook yet for what an AI-ready security engagement looks like, and you would rather define one than wait for one. You are comfortable in front of customers. Running discovery, leading working sessions with engineering teams, and handing off a report to a CISO in the same week. You ship. If a workflow needs a script, a quick integration, a Burp extension, a query against a SAST or SCA tool, or a custom check against an LLM-based pipeline, you build it instead of filing a ticket. You have seen what AI and agent-led development is doing to the security surface area firsthand, and you have opinions about it. Bonus: experience with LLM-based code analysis, MCP, agentic systems, supply-chain attacks, cloud-native runtime context, or prior FDE work at a security or developer-tools company.