56 questions for hirers and 28 we use ourselves, across 14 disciplines. Each one carries what a strong answer contains and, more usefully, what a plausible weak one sounds like.
The second half is the point. In a room where you cannot judge the content, fluency beats correctness unless somebody has named the failure in advance.
Yes, candidates can read this too
Including the questions we ask when assessing somebody for the register. A question that stops working once the candidate knows it is coming was never testing anything, and we would rather people arrived prepared than caught out. Preparation cannot manufacture a production failure you have never had.
Ask these whatever the discipline
01
Tell me about something you built that failed in production. What broke, how did you find out, and what did you change?
The single most useful question in this whole bank. Anyone who has run real systems has one of these ready. Anyone who has only demonstrated them does not, and no amount of preparation manufactures the specific detail.
A strong answer
A specific failure with a mechanism, a detection story that involves how they found out rather than being told, and a change that is smaller and more boring than you expected. Strong practitioners usually describe fixing the thing that let the failure go unnoticed, not just the failure.
The confident failure
A fluent, well-structured story about a challenging project that was ultimately delivered successfully. Note the tense and the abstraction: challenges rather than a failure, lessons rather than a change. It sounds like an answer because it has the shape of one.
02
What would you refuse to do on this project, and what would you tell me instead?
Independence. A fractional specialist whose value is judgement has to be willing to lose the work, and somebody who has never refused anything is being paid for compliance.
A strong answer
A concrete refusal with a reason, followed by an alternative that costs the client less rather than more. Best answers name a refusal that has already cost them an engagement.
The confident failure
A carefully framed answer about the importance of open dialogue and working collaboratively to find the right path. It is agreeable and it tells you they will do what you ask.
03
How would you know, three months in, that this was not working?
Whether they think in terms of falsifiable outcomes or in terms of activity. It also tells you whether they will let you stop early, which is where most of the money is saved.
A strong answer
A named signal with a threshold, agreed at the start, that they would raise themselves. Strong candidates volunteer the point at which they would recommend stopping.
The confident failure
Regular check-ins, clear communication, and a set of measures agreed with stakeholders as the work progresses. Every word is true and none of it can ever be false.
04
What is the part of your own work that you are least confident about?
Calibration. The gap between what somebody knows and what they think they know is the thing that costs you money, and it is not visible in a CV.
A strong answer
A specific, technical, slightly uncomfortable answer, usually about an area adjacent to their strength. Calibrated people find this question easy.
The confident failure
A strength rebranded as a weakness, or an answer about work-life balance. Also a genuine-sounding admission that turns out to be about something nobody would have expected them to know anyway.