Forward Deployed Engineer (FDE), Financial Services
Posted 16 days ago
The role in short
Embed with financial institutions to design, ship, and maintain production-grade AI systems and integrations that meet strict regulatory and performance standards.
About the team
OpenAI’s Forward Deployed Engineering team partners with banks, asset managers, insurers, and private capital firms to deploy production-grade AI systems in high-stakes financial environments. We operate at the intersection of customer delivery and core platform development, embedding deeply with customers to translate frontier model capabilities into reliable, auditable systems that create measurable business impact. Our work turns early deployments into repeatable solution patterns, operating standards, and evaluation practices that scale across regulated financial institutions.
About the role
We are hiring a Forward Deployed Engineer (FDE) to lead end-to-end deployments of OpenAI’s models inside financial services organizations where correctness, latency, explainability, and control matter. You will work with customers who are experts in investment banking, trading, risk, compliance, underwriting, research, operations, or investment decision-making, translating complex workflows, data constraints, and regulatory requirements into production systems.
You will measure success through production adoption, workflow efficiency, risk reduction, revenue impact, and evaluation-driven feedback loops that inform product, model, and GTM strategy. You’ll work closely with Product, Research, GTM, Security, Legal, and GRC to deliver systems that meet enterprise standards for governance, auditability, and operational resilience.
You will also play a central role in shaping OpenAI’s Financial Services offering — identifying high-value use cases, defining solution patterns, and building the first repeatable deployments that scale across institutions. Learn more about some of our work with financial institutions.
This role is based in New York. We use a hybrid work model of 3 days in the office per week. We offer relocation assistance. Travel up to 50% may be required.
In this role, you will:
- Design and ship production AI systems around models, owning integrations, data flows, reliability, observability, and on-call readiness across financial workflows.
- Lead discovery and scoping from pre-sales through post-production, translating ambiguous business problems into hypothesis-driven problem framing, system requirements, and delivery plans with measurable outcomes.
- Define and enforce launch criteria for regulated financial environments, including controls, audit artifacts, evaluation benchmarks, and acceptance thresholds tied to risk and performance.
- Build in sensitive data environments where access controls, data lineage, explainability, and failure modes shape architecture and operating procedures.
- Run evaluation loops that measure model and system quality against workflow-specific financial benchmarks (e.g., accuracy, latency, coverage, false positives) and use results to drive iteration.
- Own delivery state across multiple workstreams, making trade-offs between scope, speed, and quality to protect production outcomes.
- Distill deployment learnings into hardened primitives, reference architectures, playbooks, and tooling that scale across financial institutions.
- Surface field feedback that informs model behavior, product capabilities, and platform gaps in real-world financial use cases.
You might thrive in this role if you:
- Bring 5+ years of software engineering, ML engineering, or technical deployment experience with customer-facing ownership in financial services or adjacent regulated industries.
- Have owned complex AI or data-driven systems end-to-end, from scoping through production adoption, in environments where errors carry real financial or regulatory consequences.
- Have experience with financial workflows such as research, trading, risk, compliance, underwriting, operations, or investment processes, and understand how incentives and controls shape adoption.
- Write and review production-grade code across backend and frontend systems using Python, JavaScript, or comparable stacks.
- Have deployed systems powered by LLMs or generative models and understand how model behavior, evaluation, and guardrails affect user trust and business outcomes.
- Communicate clearly across engineering, product, risk, compliance, and executive stakeholders, translating technical trade-offs into decision quality and risk posture.
- Apply systems thinking with high execution standards, turning incidents, escalations, and failures into improved operating standards and repeatable deployment patterns.
- Stay calm and decisive when delivery is urgent, ambiguous, and high-stakes.
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
5 questions likely to come up at OpenAI, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Lead discovery and scoping from pre-sales through post-production, translating ambiguous business problems into hypothesis-driven problem framing, system requirements, and delivery plans with measurable outcomes.”
A customer says “we want AI in our claims process.” What do you ask in the first meeting?
How to answer
Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- Ask what data you can access, and who signs off on security
Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.
- 2Integrations and APIs
They wrote: “Design and ship production AI systems around models, owning integrations, data flows, reliability, observability, and on-call readiness across financial workflows.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3LLMs, RAG and agents
They wrote: “Have deployed systems powered by LLMs or generative models and understand how model behavior, evaluation, and guardrails affect user trust and business outcomes.”
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.
- Write 50–200 real examples with expected outcomes, with customer experts
- Agree on a pass bar and the errors that are never acceptable
- Score automatically where possible; review a sample by hand
- 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.
- 4Cloud, deployment and security
They wrote: “Have experience with financial workflows such as research, trading, risk, compliance, underwriting, operations, or investment processes, and understand how incentives and controls shape adoption.”
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.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- Keep the new answers for the next customer
Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.
- 5Coding
They wrote: “Bring 5+ years of software engineering, ML engineering, or technical deployment experience with customer-facing ownership in financial services or adjacent regulated industries.”
Build a small in-memory cache. Then add expiry. Then a size limit.
How to answer
Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.
- Start with get and set on a dictionary, plus tests
- Store an expiry time with each value and check it on read
- Track use order and evict the least recently used entry when full
- Say what you'd change for many threads or many machines
Tip: Keep the first version simple and well tested so the next stage is a small change.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
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.