Practise FDE Role Interview Questions

A day-in-the-life answer that lists every task still fails if it never says why the parts depend on each other.

"Walk me through a typical week" is not a request for a calendar. Answer each prompt below out loud first, pick the three or four lines that fit, then compare with the outline and reread the lesson it points to.

Objectives:

• answer the common role questions in under a minute each;
• lead with the interdependence of the three lenses;
• avoid reciting a script when only part of it fits the question.

The source material is a bank of lines, not a speech. Pull the three or four that fit the question actually asked. A recited script answers a question nobody asked and runs out the clock.

Every good answer has the same spine. Name the three lenses. Say that they reinforce each other. Then give one concrete moment from a real engagement.

1. "Why FDE? How is it different from a software engineer or a solutions role?" Name the unit of work: an engagement, not a pipeline or a control boundary. Say what the role is judged on: the customer's outcome, and whether the team could have delivered it without the FDE. Add the two habits: ask before architecting, and offer to own the definition of done. → Three Roles, Three Questions

2. "How do you split your time?" Most days touch all three lenses. Keep enough hands-on build for technical credibility and enough customer time to stay anchored to a real outcome. Keep enough team time that nobody is blocked waiting. The weighting shifts; the three stay. → The Three Lenses of FDE Work

3. "Walk me through a typical day." Morning: find who is blocked. Mid-morning: the highest-risk decision, such as an access-control boundary that would fail silently. Midday: discovery, demo or escalation. Afternoon: build, and review the team's work against the customer's intent. Evening: test how it fails and report honestly. → A Senior FDE's Day

4. "How do you guide an internal team?" Unblock before building. Review designs before code is written, while a wrong turn is cheap. Coach engineers to spot ambiguous requirements themselves. Review with a customer-intent lens, not only for correctness. Own hard scope conversations with the customer, shielding the team while keeping them informed. Model transparent reporting of failures, false alarms included. Scope the first build narrowly to prove the model before scaling. → A Senior FDE's Day

5. "What makes you senior, not just an FDE?" It is less about harder individual work and more about being the person whose judgement the team can borrow. That covers scope, what "done" means for this customer, and when to go deep versus ship the simpler thing. It only works when the FDE stays technical enough to be trusted, connected enough to the customer to know what matters, and available enough not to be the bottleneck. → The Three Lenses of FDE Work

Warning: "a consultant who codes" is the answer to avoid. It names two activities and no outcome. Replace it with the unit of work and the interdependence of the lenses.

A strong answer runs about forty seconds. "Most days touch all three. I keep enough hands-on build that the team trusts my calls. On the insurer engagement that meant designing the two-layer access check myself, because it would fail silently if wrong. I keep direct customer time, running users and compliance as separate discovery conversations. And I start each day by unblocking the team. None of these are separable: credibility speeds trust, customer access speeds decisions, and the team's growth lets me stay deep where it matters."

Score it against the spine. It names all three lenses, gives one concrete moment, and ends on interdependence. That ending is the line that separates senior from mid-level.

• Treat the material as a bank of lines and pick the three or four that fit.
• Every answer names the three lenses, says they reinforce each other, and gives one concrete moment.
• "Why FDE" is answered with the unit of work and what you are judged on, not a job description.
• The senior answer is about borrowable judgement, sustained by depth, customer connection and availability.

1. What three parts should every role answer contain? The three lenses, the statement that they reinforce each other, and one concrete moment from a real engagement.

2. Give the one-sentence answer to "what makes you senior". Being the person whose judgement the team can borrow on scope, on what "done" means, and on when to go deep, while staying technical, customer-connected and available.

3. Name three habits for guiding an internal team. Any three of: unblock before building; review designs before code; coach engineers to spot ambiguity; review with a customer-intent lens; own hard scope conversations; report failures transparently; scope the first build narrowly.