Lesson 1 of 6
How the Interview Loop Works and What Each Round Tests
See the rounds a Forward Deployed Engineer loop is usually built from, what each one is scoring, and how to find out which rounds you will face.
5 minForward Deployed Engineering
After this lesson you will be able to name the rounds in a typical Forward Deployed Engineer interview loop, say what each round is testing, and find out which rounds your own loop will have.
Why this loop is different
A Forward Deployed Engineer (FDE) builds software with a customer, inside the customer's systems, and is responsible for it working there. The interview tests that job. A software engineering loop mostly asks whether you can write good code. An FDE loop asks that too, and then asks three more things. Can you turn an unclear request into a piece of work? Can you build something that survives someone else's environment? Can you explain what you did to a person who does not write code?
That changes how you prepare. Practising coding puzzles alone leaves most of the loop unprepared. You also need to practise asking questions out loud, cutting scope on purpose, and writing down your reasoning so that somebody else can follow it.
The rounds you are likely to meet
Every company runs its own loop, so treat this list as a map and not as a promise. Most loops are built from these rounds:
- A recruiter call. It checks that the basics fit: your background, where you can work, how much travel or time on customer sites you accept, and why you want this role and not a product engineering role.
- A coding round. A live exercise in a shared editor, often closer to everyday work than to puzzles: parse some data, call an interface, fix a bug in code you have not seen before.
- A take-home. A written brief and a few hours to build something small and send it back, often followed by a call where you walk through it.
- A customer case. The interviewer plays a customer with a vague problem. You ask questions, work out what the problem is, and propose what to build first.
- A system design round. You design a system that has to run in a customer's environment, with the customer's data, security rules and existing systems.
- A behavioural round. Questions about times you owned a problem, dealt with a difficult person, worked without clear instructions, or got something wrong.
Some companies fold two of these into one. A take-home walkthrough can turn into a system design conversation when the interviewer asks how your tool would cope with far more data. A customer case can end with a request to sketch how you would build what you proposed.
What each round is scoring
Interviewers usually write up each round against a set of headings. The headings differ between companies, but they come down to a small number of questions.
In the coding round and the take-home: did you get to something that works, did you check that it works, and can another engineer read it? A small thing that runs and is explained beats a large thing that almost runs.
In the customer case: did you find the real problem before proposing a solution, did you ask what success looks like, and did you say what you would not do? A candidate who starts designing in the first minute has skipped the part being tested.
In the system design round: did you ask about the constraints of the customer's environment before drawing boxes, did you say how the system fails and how someone finds out, and did you plan for the day you hand it over?
In the behavioural round: are your stories specific, do they show you taking responsibility for an outcome and not only for a task, and do you talk about customers with respect?
One more thing is judged in every round without appearing on any form: how you handle not knowing. An FDE is often the least informed person in the customer's building. "I do not know that system; here is how I would find out" is a good answer. A confident guess is not.
Find out what your loop contains
You do not have to guess the rounds. Ask the recruiter. It is a normal question, and the answer saves you days of preparing for the wrong thing. Ask:
- How many rounds are there, and what is each one called?
- Is there a take-home, and how long are candidates expected to spend on it?
- Can I use a programming language of my choice in the coding round?
- Does any round involve playing through a conversation with a customer?
- Who will I meet: engineers, managers, people who work with customers?
Then read the job advert again with the list of rounds beside it. The advert tells you what the company's customers look like (banks, hospitals, factories, software companies) and what the work is (joining up data, deploying AI models, building internal tools). Your case and design rounds are likely to be set in that world, so learn its vocabulary before you walk in.
The example this course uses
The rest of this course works through one made-up customer, so that each round builds on the last. The customer is Calder Freight, a freight company with a warehouse system that records shipments and a billing system that raises invoices. Its finance team believes the two do not agree.
In lesson 2 that problem arrives as a take-home brief and you build a small tool. In lesson 3 you test the tool and write it up. In lesson 4 the same problem arrives as a conversation with the customer. In lesson 5 you design the version that runs every night inside Calder Freight's network. Lesson 6 covers the behavioural round and gives you a plan for the two weeks before your interviews.
Create a folder called fde-interview now. Inside it, create a text file called notes.md. You will add to it in every lesson: your loop, your assumptions, your stories. By the end it is the document you reread the night before an interview.
Key takeaways
- An FDE loop tests coding and three more things: scoping an unclear request, building for someone else's environment, and explaining your work to people who do not write code.
- Most loops are built from a recruiter call, a coding round, a take-home, a customer case, a system design round and a behavioural round.
- In every round, a small thing that works and is explained scores better than a large thing left unfinished.
- Saying how you would find something out is a better answer than a confident guess.
- Ask the recruiter which rounds your loop has before you start preparing.
Try it
Find one current job advert for a Forward Deployed Engineer or a similar customer-facing engineering role. In notes.md, under the heading "My loop", write three short lists: the kinds of customer the company serves, the kind of work the advert describes, and the rounds you expect, each marked as confirmed or guessed. Then write the five recruiter questions from this lesson as a short email in your own words. A good result fits on one screen and makes clear which rounds you still need to confirm.
Official documentation
Written with AI and checked automatically. Nobody has run these steps by hand, and tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.