Lesson 6 of 6
Behavioural Questions, Your Own Questions and a Two-Week Plan
Prepare five true stories for the behavioural round, the questions you will ask the company, and a dated two-week plan that covers every round.
6 minForward Deployed Engineering
After this lesson you will be able to answer behavioural questions with stories prepared in advance, ask the company questions that show how you think, and follow a two-week plan that covers every round in this course.
What the behavioural round looks for
Every company asks behavioural questions. For an FDE they carry more weight than for most engineering roles, because the job is done in front of customers and often alone. The interviewer wants evidence of four things. You take ownership of an outcome and not only of a task. You stay useful when nobody has told you exactly what to do. You can work with a person who is unhappy or difficult. And you say so plainly when you got something wrong.
Evidence means something that happened. "I am good with customers" is a claim. "The customer's operations manager stopped answering my emails, so I went to their site on a Tuesday and asked her what I had got wrong" is evidence.
Prepare five stories
You cannot predict the questions, but five stories cover most of them. Choose one of each kind from your own work, study or projects:
- A time you owned an outcome from start to finish, including the dull parts.
- A time the instructions were unclear and you had to decide what to do.
- A time you worked with a difficult person, ideally a customer or a user.
- A time you got something wrong, what it cost, and what you changed.
- A time you had to learn something quickly to get a job done.
Give each story three parts: the situation in two sentences, what you did, and the result. Spend most of the time on what you did. Say "I" and not "we" for your own actions, because the interviewer is hiring you and not your team. End on a result that is a fact: a number, a decision somebody made, something that is still in use.
Here is the shape, with the fourth kind of story:
"I built a report for a finance team that compared two exports. In the first week it flagged forty problems a day, and the team stopped reading it. I had treated a comma in an amount as a difference, so most of the forty were false alarms. I sat with the person who read the report, went through one day's list with her, fixed the comparison and added a test for each kind of false alarm. The list dropped to about five a day, and she started acting on it again. Now I read the real data row by row before I write the comparison."
That takes under a minute to say. It names the mistake without excuses, shows what was done about it, and ends with what changed in how the person works. If you have no customer experience, use a user of something you built, a teammate, or a client from any job. The interviewer is listening for how you behaved.
One story can answer several questions. "Tell me about a conflict", "tell me about a time you disagreed with a decision" and "tell me about a hard conversation" can all be the third story, told with a different first sentence.
Answer "why this role"
You will be asked why you want to be a forward deployed engineer and not a product engineer. A good answer has two halves. The first is what draws you: seeing your work used, working on a different problem with each customer, being close to the decision about what to build. The second is that you know what the job costs. You will travel or keep a customer's hours. You will work in old systems you would never choose. You will write code that is thrown away when the customer's need changes. Requirements will move under you.
Say the costs out loud, and say why you accept them. A candidate who describes only the attractions sounds as if they have not understood the job.
Ask your own questions
Near the end you will be asked whether you have questions. This is part of the interview. Your questions show what you think matters, and the answers tell you whether you want the job. Ask about how the work is really done:
- How long does a typical piece of customer work last, and how many customers does one engineer work with at a time?
- When a customer asks for something the product does not do, who decides whether it gets built?
- What happens to the code an FDE writes for one customer? Does any of it reach the product?
- How is an FDE's work judged after six months?
- What did the last person who did well in this team do in their first three months?
Write the answers down afterwards. If you get an offer, they are how you compare it with another.
A two-week plan
Two weeks of steady work is enough to prepare for the loop in lesson 1 if you already write code. Put the days in a calendar with dates. Alongside the plan, do thirty minutes of practical coding every day: read a file, clean the data, write a function, test it.
- Days 1 and 2: find out the rounds for the company you are applying to and write them in
notes.md. Read what the company sells and who buys it. - Days 3 to 5: the take-home. Repeat lessons 2 and 3 with a brief you write for yourself, inside a three-hour limit, and finish with a README.
- Days 6 to 8: customer cases. One case a day, spoken aloud with a partner or a recorder, with the half-page summary from lesson 4 afterwards.
- Days 9 to 11: system design. One design a day on one page, in the order from lesson 5: questions, flow of data, failures, handover, trade-offs.
- Days 12 and 13: stories. Write the five, say them aloud, and cut each to under two minutes.
- Day 14: rest. Read your notes once and stop.
If you have less time, keep the order and shorten each part. Do not drop the practice that is spoken aloud. It is the part people skip, and the customer case and the behavioural round are both spoken.
On the day
A few habits carry across every round. When a question is unclear, say what you think it means and ask whether that is right. When you are thinking, think aloud, so that the interviewer can follow you and help. When you do not know something, say so, and say how you would find out. When you are given a hint, take it. And in every round, come back to the customer: who uses this, what do they do with it, and how will anyone know it worked.
You now have the whole loop in one folder: a tool with tests and a README, a customer case with its summary, a design on one page, five stories and a dated plan. Those files in fde-interview are what to reread the night before.
Key takeaways
- Five true stories, each with a situation, what you did and a result, cover most behavioural questions.
- Say "I" for what you did; the interviewer is hiring you and not your team.
- Answer "why this role" with its costs as well as its attractions.
- Your questions to the company are part of the interview, so ask how the work is really done.
- Put the plan in a calendar with dates; practice that is spoken aloud and timed counts for more than reading.
Try it
In notes.md, write your five stories, each as three short paragraphs: the situation, what you did, and the result. Then write your two-week plan with a real date beside each day, and the four questions you will ask the company. Say each story aloud against a timer. A good result is five stories that each take under two minutes to tell, each with a result you can state as a fact, and a plan whose first session is in your calendar.
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.