Forward Deployed Engineer, Customer Deployments
Posted 4 days ago
The role in short
Embed with enterprise clients to identify high-leverage AI opportunities, build and deploy production AI agents and integrations, and lead adoption.
ABOUT TITAN
Titan is building the AI workforce for IT. We deploy AI agents across our portfolio of Managed Service Providers and enterprise customers: agents that monitor, triage, and resolve work across the service desk, infrastructure, security, identity, endpoint, and application operations. The result is faster resolutions, better uptime, and more proactive, personalized support, delivered 24/7.
We've raised over $100M from General Catalyst, 8VC, and CalPERS, acquired market-leading MSPs like RFA, and put agents into production in large enterprises. We've automated 100K+ tickets across 800+ customers. Our tech team has talent from Scale AI, CoreWeave, Vanta, Dropbox, Meta, FiveRings, TwoSigma, Amazon, Harvard, Stanford, and MIT.
Joining Titan means helping redefine how work gets done in IT services, and building a $100B company.
ABOUT THE TEAM
Customer Deployments is Titan's central AI deployment team. We sit at the holding company level and partner with our MSPs to bring applied AI into production for the businesses they serve. Those clients span every industry: private equity, venture and hedge funds, family offices, biotech and pharma, insurance, accounting firms, healthcare, manufacturing, law. Inside each one we work across functions like finance, investor relations, compliance, operations, HR and client service. Working alongside the MSP that already supports each client means every deployment fits how the business runs, and has a team behind it long after launch.
Most companies know AI should change how they work. Very few have someone who can walk in, learn the business in a week, find the work that matters, and ship something people actually use. That's this team.
ABOUT THE ROLE
Forward Deployed Engineers on Customer Deployments own a deployment end to end. You'll sit with a client's leadership and the people doing the work, learn how their business really runs, find where AI changes the outcome, design the solution, build it, ship it to production, and stay until it's adopted. One month you might be working with a private equity firm to build AI into its value creation plan and deploy it across its portfolio companies; the next, learning how a biotech runs its regulatory submissions or how an insurer handles claims intake.
This is a high-trust, high-autonomy role for someone who is part architect, part engineer and part operator. You build with agentic coding tools and move fast, but your edge is judgment: which problem to solve, how to make an agent safe and reliable, and when it's ready for users. What you learn in the field shapes Titan's platform, and the patterns you build become the playbook for every deployment after yours.
IN THIS ROLE YOU WILL
- Get up to speed quickly on a new business and its workflows, sit with the people doing the work, and find the highest-leverage opportunities for AI
- Architect solutions across models, agents, data and integrations, and decide when an off-the-shelf platform beats a custom build
- Build with agentic coding tools: prototype in days and ship to production in weeks, connected to the systems clients run (CRMs, ERPs, fund admin and portfolio systems, document stores, data warehouses, Microsoft 365 and Google Workspace)
- Put agents into production properly, with guardrails, evals, observability, human review where it matters, and the access controls and documentation regulated clients expect
- Lead onboarding, training and change management so deployments get used, and measure their impact against a baseline
- Be the technical voice in front of executives: explain tradeoffs, push back on weak use cases, and earn the next project
- Turn what works into reusable components, templates, evals and playbooks, and bring what you learn in the field back to Product and Engineering
- Partner with MSP leadership to find and shape new deployment opportunities across their client base
YOU MIGHT THRIVE IN THIS ROLE IF YOU
- Love learning how businesses work: you can get up to speed on a PE fund's deal process, an insurer's underwriting workflow or an accounting firm's close in days, and talk about it credibly with the people who run it
- Bring 5+ years in solutions architecture, forward deployed engineering, technical consulting or software engineering, with significant customer-facing work
- Use agentic coding tools (Claude Code, Codex, Cursor and similar) as your daily way of building, and write solid Python or TypeScript
- Have a solid grounding in applied AI: you've built LLM-powered tools, agents or workflows, and you understand what it takes to run them reliably in production (evals, guardrails, failure modes, cost and latency)
- Can run a room with a business leader, turn a vague ambition into a concrete scope, and say no to the wrong project
- Thrive in ambiguity: a new industry, a new stack and a new set of stakeholders every few months sounds fun to you
- Would rather put a working system in front of 10 users in three weeks than a perfect one in front of none in three months
- Take extreme ownership of outcomes and treat client data with a security mindset
BONUS
- Have shipped LLM agents to production for real users, with evals and guardrails you designed
- Forward deployed, solutions or software engineering experience at an AI, SaaS or consulting company
- Domain depth in financial services (PE, VC, hedge funds, family offices), life sciences, insurance or professional services
- Experience in or alongside MSPs and IT services
LOGISTICS
- Location: New York City or San Francisco
- Travel: Up to 25%, for on-site discovery, launches and client workshops
- Compensation: $150K - $250K + generous equity package
Prep for this interview
5 questions likely to come up at Titan, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “Have a solid grounding in applied AI: you've built LLM-powered tools, agents or workflows, and you understand what it takes to run them reliably in production (evals, guardrails, failure modes, cost and latency)”
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.
- 2Coding
They wrote: “Use agentic coding tools (Claude Code, Codex, Cursor and similar) as your daily way of building, and write solid Python or TypeScript”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 3Discovery and scoping
They wrote: “Can run a room with a business leader, turn a vague ambition into a concrete scope, and say no to the wrong project”
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.
- Score each request by business value and by effort, with the customer in the room
- Pick one item that proves value fast and unblocks later work
- Write down what's out of scope so it doesn't creep back in
- 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.
- 4Integrations and APIs
They wrote: “Architect solutions across models, agents, data and integrations, and decide when an off-the-shelf platform beats a custom build”
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.
- 5Cloud, deployment and security
They wrote: “Take extreme ownership of outcomes and treat client data with a security mindset”
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.
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.