OpenAI
OpenAI84 open roles

Forward Deployed Engineer (FDE), Cyber

London, UK; Tokyo, JapanHybridSeniorFull-time

Posted today

The role in short

Embed with customer security teams to design, build, and deploy production AI agents and security tools that automate patching, detection, and defense workflows.

About the Team

OpenAI’s Forward Deployed Engineering team builds with customers to bring frontier AI into production. Our Cyber FDEs partner with the security and engineering teams that defend globally critical systems, from enterprise software to the core infrastructure it runs on. Cyber FDEs work closely with our Product, Research, and Go-to-Market teams to adapt our products and models to what customers need to defend their systems.

About the Role

You’ll build systems that give defenders an advantage at a scale few engineering teams encounter. You might help an enterprise identify, test, and deploy patches across hundreds of thousands of code repositories, or help a security team analyze petabytes of logs for signs of malicious agents or coordinated attacks. Across these deployments, you’ll build tools that customer engineers can trust to support consequential security decisions.

You’ll work directly with customer security teams, from CISOs to frontline analysts. As AI changes how attackers operate, you’ll help these teams determine where their defenses need to evolve, prioritize what to build, and validate solutions with the engineers who will operate them. Alongside OpenAI’s account teams, you’ll translate security priorities into deployed systems that help defenders cover more ground.

You’ll also help shape what OpenAI builds next. When you identify a gap between what defenders need and what today’s models or products can do, you’ll partner with Research and Product to define, build, and test capabilities that address it.

This role is based in London. We use a hybrid work model of 3 days in the office per week. We offer relocation assistance. Travel up to 50% is required.

In this role you will:

  • Partner with customer security leaders and OpenAI’s Go-to-Market team to scope engagements, establish responsibilities, and define measurable success criteria.
  • Lead technical design and implementation alongside customer engineers. Integrate agents into security workflows, establish access boundaries, and determine which actions require human review.
  • Build evaluations grounded in the decisions defenders make. For a patching agent, test whether a fix blocks a known exploit while preserving expected application behavior. For a detection system, replay historical attacks alongside normal traffic to measure detection speed and false-positive rates.
  • Guide production rollout with the engineers who will operate the system. Provide the observability and controls they need to understand system behavior, intervene when necessary, and expand adoption with confidence.
  • Translate successful approaches across deployments into reusable tools and engineering practices that other defenders can adopt.

You might thrive in this role if you:

  • 5+ years of software engineering experience, including building and shipping production software.
  • Experience protecting production systems through work in security engineering, infrastructure, SRE, DevOps, or product engineering.
  • Experience building and evaluating AI agents for software engineering workflows.
  • Experience with CI/CD pipelines and practices that maintain code quality, reliability, and security.
  • Ability to navigate unfamiliar codebases and contribute maintainable, production-quality changes.
  • Ability to communicate technical concepts and trade-offs to engineering teams and senior security stakeholders.

Additional experience includes:

Cybersecurity spans many disciplines, and while we’re primarily looking for strong engineering generalists, we’d love to hear about deeper experience in any of the following areas:

  • Security curiosity and experimentation: You read CVE write-ups because you want to understand how things break. You may have built an agent honeypot to test a hypothesis—or prove a point—and enjoy turning a security question into a hands-on experiment.
  • Security community engagement: You enjoy exchanging ideas with defenders, whether that’s discussing security strategy with a CISO at Black Hat or comparing technical approaches with frontline practitioners.
  • Application security: You’ve written CodeQL queries or Semgrep rules, built fuzzing harnesses, or discovered and responsibly disclosed vulnerabilities.
  • Automated remediation: CI/CD is your happy place. You’ve built tooling that turns security findings into tested patches, dependency upgrades, or configuration changes across large codebases.
  • Detection engineering: You’ve written and deployed detections using Sigma, YARA, Splunk, or KQL and tested them against attacker behavior.
  • Cloud and identity security: You’ve designed cloud IAM architectures and investigated abuse of workload identities, role hierarchies, or cross-account trust.
  • Security research: You’ve reverse-engineered malware, developed exploit reproductions, or contributed to vulnerability research.
  • Agent security: You’ve tested agents for prompt injection, tool misuse, or credential exposure and built defenses against them.

About OpenAI

OpenAI is an AI research and deployment company dedicated to ensuring that general-purpose artificial intelligence benefits all of humanity. We push the boundaries of the capabilities of AI systems and seek to safely deploy them to the world through our products. AI is an extremely powerful tool that must be created with safety and human needs at its core, and to achieve our mission, we must encompass and value the many different perspectives, voices, and experiences that form the full spectrum of humanity.

We are an equal opportunity employer, and we do not discriminate on the basis of race, religion, color, national origin, sex, sexual orientation, age, veteran status, disability, genetic information, or other applicable legally protected characteristic.

For additional information, please see OpenAI’s Affirmative Action and Equal Employment Opportunity Policy Statement.

Background checks for applicants will be administered in accordance with applicable law, and qualified applicants with arrest or conviction records will be considered for employment consistent with those laws, including the San Francisco Fair Chance Ordinance, the Los Angeles County Fair Chance Ordinance for Employers, and the California Fair Chance Act, for US-based candidates. For unincorporated Los Angeles County workers: we reasonably believe that criminal history may have a direct, adverse and negative relationship with the following job duties, potentially resulting in the withdrawal of a conditional offer of employment: protect computer hardware entrusted to you from theft, loss or damage; return all computer hardware in your possession (including the data contained therein) upon termination of employment or end of assignment; and maintain the confidentiality of proprietary, confidential, and non-public information. In addition, job duties require access to secure and protected information technology systems and related data security obligations.

To notify OpenAI that you believe this job posting is non-compliant, please submit a report through this form. No response will be provided to inquiries unrelated to job posting compliance.

We are committed to providing reasonable accommodations to applicants with disabilities, and requests can be made via this link.

OpenAI Global Applicant Privacy Policy

At OpenAI, we believe artificial intelligence has the potential to help people solve immense global challenges, and we want the upside of AI to be widely shared. Join us in shaping the future of technology.

Prep for this interview

4 questions likely to come up at OpenAI, each matched to a line in this posting.

  1. 1Discovery and scoping
    They wrote: “Partner with customer security leaders and OpenAI’s Go-to-Market team to scope engagements, establish responsibilities, and define measurable success criteria.”

    How do you decide what to build first when a customer wants ten things?

    How to answer

    Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.

    1. Score each request by business value and by effort, with the customer in the room
    2. Pick one item that proves value fast and unblocks later work
    3. Write down what's out of scope so it doesn't creep back in
    4. Revisit the list after the first release, with real usage data

    Tip: Show a simple way to rank the list and name what you'd leave out on purpose.

  2. 2LLMs, RAG and agents
    They wrote: “Experience building and evaluating AI agents for software engineering workflows.”

    How do you know an LLM feature is good enough to ship?

    How to answer

    Why they ask: Evals are what separate a demo from production. Many roles list them by name.

    1. Write 50–200 real examples with expected outcomes, with customer experts
    2. Agree on a pass bar and the errors that are never acceptable
    3. Score automatically where possible; review a sample by hand
    4. Re-run on every prompt or model change, and watch live traffic after launch

    Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.

  3. 3Cloud, deployment and security
    They wrote: “Lead technical design and implementation alongside customer engineers. Integrate agents into security workflows, establish access boundaries, and determine which actions require human review.”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  4. 4Travel
    They wrote: “This role is based in London. We use a hybrid work model of 3 days in the office per week. We offer relocation assistance. Travel up to 50% is required.”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at OpenAI

All 83

Similar roles at other companies

OpenAI

Hybrid

Apply