Forward Deployed Engineer
A 12-week live, project-led course for software engineers: scope customer needs, integrate products into real systems, and deploy AI features.
Curriculum
OUT-01The FDE Role & Customer Discovery3 lessons · 16 h
- FDE vs consulting and sales engineering
- Discovery interviews and workflow mapping
- One-page problem statement signed by both sides
OUT-02Data Wrangling in Someone Else's Systems3 lessons · 16 h
- Python and SQL on undocumented data
- Messy CSVs, duplicates and merged-cell Excel files
- Cleaning pipeline and data-quality report
OUT-03Integrations: APIs, Auth & Legacy3 lessons · 16 h
- REST and SOAP clients
- OAuth and SAML SSO
- Webhooks, rate limits, retries and idempotency
OUT-04Deploying AI Features for Customers3 lessons · 16 h
- LLM APIs and retrieval over customer documents
- Tool-calling agents
- Evals and fallbacks for wrong answers
OUT-05Production: Cloud, Security & Operations4 lessons · 16 h
- Docker and cloud deployment
- Secrets, access control, logging and monitoring
- Data residency and security questionnaires
- Runbook and incident drill
OUT-06Stakeholders, Handover & Capstone3 lessons · 16 h
- Scope changes and saying no
- Status reports and field feedback
- Capstone demo and handover to a customer panel
What's included
Questions
Do I need prior experience?
This course is set at intermediate level. The first module starts from the basics, so you only need the time and a laptop or phone with a stable connection.
What if I miss a live class?
Every live class is recorded and posted within 24 hours. You keep access to the recordings for 12 months.
When are the classes?
The next cohort starts 4 January 2027 and runs for 12 weeks, ~8 hrs per week. The full timetable and class link appear in My courses before the first class.
Which language is the course taught in?
English.
How do I pay?
Online through UPI, cards, net banking or wallets, processed by Razorpay. You get a receipt by email and the course appears in My courses right away.
Q01What does a Forward Deployed Engineer do?RoleBasic
An FDE works directly with customers to get the product working in their environment: understanding the problem, integrating with their systems and data, and shipping production code.
Unlike a sales engineer, an FDE builds and maintains real deployments, not demos. Unlike a core product engineer, most of the work happens in the customer's systems, and the FDE feeds what they learn back to the product team.
Q02How do you run a first discovery call with a customer?DiscoveryBasic
Prepare on their business beforehand. Ask about the current workflow, who does each step, where it breaks, how they will measure success, and constraints on data, security and timeline.
Listen more than you pitch. Play back what you heard, and follow up with a short written problem statement and success criteria that both sides sign off.
Q03Halfway through a project the customer asks for a new feature. What do you do?ScopingIntermediate
Find the need behind the request first. Work out the effect on timeline and risk, then give options: swap it for something in scope, move it to a later phase, or offer a workaround.
Get the decision in writing from the person accountable on their side, and log the request as product feedback.
Q04How do you build a reliable integration with a flaky third-party API?IntegrationIntermediate
Set timeouts, retry with exponential backoff and jitter, and use idempotency keys so retries don't create duplicates. Respect rate limits and add a circuit breaker.
Put work on a queue, send repeated failures to a dead-letter queue, log and alert, and run a reconciliation job that finds and fixes mismatches.
Q05A customer sends a messy CSV export with duplicates and mixed formats. How do you handle it?DataIntermediate
Profile it first: row counts, nulls, types and distinct values. Agree the business keys and cleaning rules with the customer.
Keep the raw file, normalise formats, deduplicate on the agreed keys, and add validation checks. Make the pipeline rerunnable, and share a data-quality report showing what changed.
Q06Explain SSO with SAML and OIDC at a high level.AuthIntermediate
Both let the customer's identity provider sign users in to your product. SAML sends XML assertions through the browser and is common in large enterprises. OIDC builds on OAuth 2.0 and uses signed JSON tokens, and is common for modern web and mobile apps.
Setting it up means exchanging metadata, redirect URLs and certificates, and mapping user attributes and groups. Always test with a normal user account, not just an admin.
Q07How do you make an LLM feature reliable for a customer?AIAdvanced
Build an eval set from their real data and agree an accuracy target with them. Ground answers in their documents with citations.
Add guardrails and fallbacks: say "I don't know" or hand off to a human when confidence is low. Log inputs and outputs for review, roll out in stages, and monitor cost and quality.
Q08A customer's security questionnaire asks where their data is stored and who can access it. How do you answer?SecurityAdvanced
Answer from the actual architecture: storage regions, encryption in transit and at rest, access controls and least privilege, audit logging, retention and deletion, and any sub-processors.
Involve your security team, never promise what isn't true, and check data-residency rules such as India's DPDP Act.
Q09A production issue hits a customer deployment late at night. What do you do?OperationsAdvanced
Acknowledge it, judge the impact, and tell the customer early. Restore service before hunting for the root cause, for example by rolling back or turning off a feature flag.
Keep a timeline as you go. Afterwards, run a blameless postmortem, fix the cause, and update the runbook.
Also on its own page: Forward Deployed Engineer interview questions