FDE interview questions

FDE loops test whether you can build and whether you can work with a customer. Questions fall into three groups. For each one, here is what a strong answer covers.

Technical questions

"A partner's webhook sometimes sends the same event twice. How do you handle it?" Covers: an idempotency key stored with a unique constraint, ordering by event version, and replaying failed events from a log. Practise it on the idempotent webhook problem.

"How would you let staff ask questions over 400 policy PDFs?" Covers: chunking with document version metadata, retrieval with citations, refusing when nothing relevant is found, and a test set to measure quality. Practise on the HR policy RAG problem.

"How do you know an LLM feature is good enough to ship?" Covers: an eval set built from real inputs, a pass bar agreed with the customer, error categories rather than one score, and a gate in the release process.

"Map this CRM export to warehouse tables." Covers: entities and keys, handling duplicates, keeping raw data in staging, and one query that proves the model works.

Client questions

"The customer's sponsor asks for 'AI for the whole support team'. What do you do first?" Covers: discovery before building, finding one workflow, agreeing a success metric in numbers, and identifying the data and systems involved.

"Mid-pilot, a user asks for a new feature. How do you respond?" Covers: logging the request, stating its cost in time, offering a swap, and getting the sponsor's decision. See handling scope change.

"Explain retrieval-augmented generation to a non-technical manager." Covers: plain language, a concrete example from their business, and what can go wrong.

Behavioural questions

"Tell me about a time you owned something end to end." Covers: the problem, what you decided, what went wrong and what you would change. Ownership means including the parts that were not your job.

"Tell me about a difficult stakeholder." Covers: what they needed, how you found out, and the outcome. Avoid blaming them.

"Why FDE rather than a product engineering role?" Covers: genuine interest in customers and varied problems, backed by something you have done.

How to prepare

Take the free skill tests to find weak spots, build one portfolio project you can talk through in depth, and rehearse the case round out loud.