Forward Deployed Engineer
Posted 25 days ago
The role in short
Design, build, and deploy production AI agents and integrations for clients, owning the technical architecture and delivery within a consulting pod.
Citrin Cooperman's Applied AI Practice designs, builds and runs AI agents inside clients' businesses. Those clients are middle-market companies, private equity sponsors and their portfolio companies, and enterprise clients our team has served for years.
As a Forward Deployed Engineer, you own the technical side of an engagement. You work in a pod with a Deployment Strategist, who owns the business case, the scope and the executive relationship. You own the architecture, the code, and whether the system holds up in production.
Most of our clients don't have large IT or data teams. A typical engagement starts with scattered data, an older ERP, a small IT staff, and a CFO who wants to see the controls before an agent touches the general ledger. You leave with a system in production and a client team that can run it.
WHAT YOU'LL BUILD
- Agents for sales, marketing, service, operations, finance and accounting work, connected to clients' ERPs, accounting systems and CRMs
- MCP servers, agent skills and integrations that give models safe access to client systems, written so the next engagement can reuse them
- Data pipelines that prepare client data for AI: you profile, clean, model and connect the sources before an agent depends on them
- Evaluation suites, monitoring and audit trails, so every agent ships with a measured accuracy baseline and every action it takes can be traced and reviewed
DISCOVERY AND DESIGN
- Run technical discovery with your Deployment Strategist: map the client's workflow, systems and data, then turn the business problem into an architecture
- Pick the right stack for each client: Anthropic or OpenAI models, AWS, Azure, GCP, Salesforce Agentforce, or a mix
- Build proofs of concept quickly, and know what it takes to turn one into a production system
DELIVERY AND PRODUCTION
- Own components from architecture through deployment, monitoring and handoff in the client's environment
- Get systems through client security reviews, access controls and data-handling requirements, including at regulated clients
- Train client teams to operate and extend what you deliver
PRACTICE BUILDING
- Turn what works into reference architectures, starter repos, eval templates and playbooks for the rest of the Practice
- Review designs and code from other engineers on the team
- Send field lessons and platform gaps back to the Practice and to our technology partners
What Success Looks Like in the First Year
- Systems in production at clients, each with a measured accuracy baseline and an audit trail
- Reference architectures and starter repos that other engagements reuse
- You meet the billable utilization target and earn strong client satisfaction scores
Qualifications
- Five to eight years of software engineering experience, including at least one production system you can walk us through in detail
- Client-facing technical delivery experience in consulting, professional services or a forward deployed role; this is a requirement
- Deep expertise in at least one platform: Salesforce, AWS, Azure, GCP, or a frontier lab ecosystem (Anthropic or OpenAI APIs, agent SDKs and tooling)
- Production experience with large language models: prompt design, tool use, agents and evaluation, including why an agent failed and what you would change
- Fluency in Python or a strongly typed language, and working SQL
- Experience designing APIs, data models and integrations, beyond using them
- Able to explain technical trade-offs to finance leaders and executives as clearly as to engineers
- Willing to travel about 25% of the time
Preferred Qualifications
- Finance and accounting operations experience: close, AP/AR, FP&A or audit
- Private equity experience: sponsor work, portfolio operations or value-creation plans
- Delivery in regulated industries such as financial services or healthcare
- Middle-market consulting, where clients have small IT teams and fixed budgets
- Certifications from Anthropic (Claude Certified Developer, Claude Certified Architect), Salesforce (Agentforce Specialist, Platform Developer I), AWS, Azure or GCP
- Experience with MCP, agent frameworks (Claude Agent/Messages SDK, OpenAI Agents SDK, LangGraph) or cloud data platforms (Snowflake, Databricks, Microsoft Fabric, Salesforce Data 360)
Prep for this interview
5 questions likely to come up at Citrin Cooperman, each matched to a line in this posting.
- 1Cloud, deployment and security
They wrote: “Pick the right stack for each client: Anthropic or OpenAI models, AWS, Azure, GCP, Salesforce Agentforce, or a mix”
The agent reads emails and web pages. How do you stop text in them from taking control of it?
How to answer
Why they ask: Prompt injection is the main security risk of agents that act. They want concrete defences.
- Keep instructions separate from the content the agent reads
- Give the agent only the tools and permissions the task needs
- Require a person to approve actions that send, pay or delete
- Check outputs and log every tool call for review
Tip: Assume some content is hostile and limit what damage it can do.
- 2Discovery and scoping
They wrote: “Run technical discovery with your Deployment Strategist: map the client's workflow, systems and data, then turn the business problem into an architecture”
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.
- 3Integrations and APIs
They wrote: “Experience designing APIs, data models and integrations, beyond using them”
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.
- 4Coding
They wrote: “Five to eight years of software engineering experience, including at least one production system you can walk us through in detail”
How do you keep quality high when you ship fast at a customer site?
How to answer
Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.
- Tests for the parts that touch customer data or money
- Code review even when it's fast, ideally by someone on the product team
- Feature flags and an easy way to roll back
- Clean up the shortcuts in the next release, and write them down
Tip: Name the few checks you never skip, and what you skip on purpose.
- 5Data and SQL
They wrote: “Data pipelines that prepare client data for AI: you profile, clean, model and connect the sources before an agent depends on them”
The customer's data is spread across five systems that disagree. How do you get one clean view?
How to answer
Why they ask: Real deployments rarely have one source of truth. They want a practical approach, not a perfect one.
- List each system and what it's the best source for
- Pick matching keys and decide how to handle records that don't match
- Load into one place with clear rules, and keep the raw copies
- Show the customer the mismatches; they often fix the source
Tip: Name the system the business trusts most for each field, and get the customer to agree.
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.