The second wrong hire is the one that forced this. Capable engineer, wrong role, gone in five months, and when I went back through the notes from the debrief I found something uncomfortable: nobody had actually said the candidate was strong. What had happened was that I had said it first, nobody had evidence to contradict me, and the absence of objection had been recorded as agreement. The interviews were fine. The decision was the broken part.
The Failure Is in the Decision, Not the Interview
Most engineering teams in Singapore have spent real effort on their interviews and almost none on the thirty minutes afterwards where the decision is made. That is the wrong allocation, because the debrief is where good evidence gets thrown away.
Three things go wrong, reliably. Anchoring: the first confident speaker sets the frame and everything after it is a reaction. Seniority weighting: the most senior person in the room is right more often than chance but far less often than their influence implies. Absence treated as assent: an interviewer with no evidence on a dimension says nothing, and silence gets counted as a yes. That last one is what sank my second bad hire.
None of those are fixed by better interview questions. They are fixed by changing the order of operations, which is what the seven steps below do. Five of them cost nothing.
Step 1: Assign Non-Overlapping Coverage Before Anyone Interviews
Before the first interview is scheduled, write down which interviewer covers which area, and make sure no two people cover the same one.
This is the structural fix for the four-opinions problem. If four people each assess general engineering ability, you finish with four views of one dimension and no evidence at all about the other three that matter. Assign them: one takes systems reasoning, one takes code quality in their actual working language, one takes collaboration and how they handle being wrong, one takes the specific domain or stack risk for this role.
Write it in the scheduling invitation, not in someone head. An interviewer who knows they own collaboration asks about collaboration. An interviewer who thinks they own everything asks whatever occurs to them and reports a feeling.
Our expert take
The coverage map has a second use that is almost more valuable than the first. When a hire does not work out, you can look back and see which dimension nobody actually assessed. In both of our bad hires the answer was the same: nobody owned the question of whether this person wanted the job that existed, as opposed to the job in the advert. That is now an assigned area with a named owner, and it has changed two decisions since.
Step 2: Collect Written Evidence Before Anyone Speaks
If you adopt one step from this piece, adopt this one. Every interviewer submits written notes and a provisional score before the debrief, and before seeing anyone else submission.
This single rule removes anchoring and seniority weighting at once, because every position on the record was formed independently. It also converts “I liked them” into something examinable, since a written note that contains no evidence is visibly a note that contains no evidence, in a way that a confident sentence in a meeting is not.
The submission should contain what the candidate actually said or did, then the score, in that order. Notes written the other way around tend to be justifications. A deadline matters too: within four hours of the interview, while recall is real rather than reconstructed.
Expect resistance, and expect it to be about time. The honest counter is that it takes about ten minutes, and the alternative costs a quarter of someone salary when it goes wrong.
Step 3: Score Against the Scorecard, Not Against Each Other
The question a score answers is narrow: did this candidate meet the bar for the area I was assigned. Not whether they were better than the person interviewed yesterday, and not whether they are as good as the interviewer was at the same stage.
Comparative scoring produces drift. A strong week raises the bar, a thin pipeline lowers it, and six months later nobody can say what the standard is. The tell is an interviewer who says a candidate was “the best we have seen this month”, which is information about the month rather than about the candidate.
If you do not have a scorecard yet, that is the prerequisite rather than this article: we cover the construction in our method for evaluating full-stack developers.
Step 4: Run the Debrief in a Fixed Order, Weakest Signal First
Open with the area where the evidence is thinnest, not with the person who has the strongest view.
Two reasons. It puts attention where the risk is, since the dimension nobody has evidence on is the one most likely to produce a surprise in month three. And it defuses the seniority effect without anyone having to be told to speak less, because the order is set by the evidence rather than by the room.
The decider speaks last. Always. A decider who opens the debrief has, in practice, ended it.
Want us to look at a debrief that went wrong
Send us the notes from a hire you regret, with names removed. We will show you which of the seven steps was missing and which dimension nobody actually assessed.
Get startedStep 5: Force a Decision, With Four Allowed Outcomes
Exactly four outcomes are permitted, and the debrief does not end until one is chosen:
- Hire, at a stated level.
- No hire.
- Hire at a different level than advertised, which is the outcome teams forget exists and the one that rescues the most candidates.
- One more interview, with a named interviewer and a written question it must answer.
What is banned is the fifth outcome: the vague maybe. “Let us keep them warm” is how a pipeline silts up with unresolved candidates who eventually accept somewhere else and tell their network you were slow. If option four is chosen without a specific question attached, it is really the banned option wearing a disguise.
Do not average scores. A mean of a strong yes and a strong no is a decision nobody in the room holds, and it is the mechanism by which teams hire candidates no individual interviewer would have defended.
Step 6: Record the Reason and the Counterfactual
Two sentences in the record. Why the decision went this way, and what would have changed it.
The counterfactual is the part that earns its keep. It makes the record useful in the three situations that actually arise: the candidate reapplies in a year and you can tell them something specific, the decision turns out to be wrong and you can see which assumption failed, or a similar candidate appears and you can check whether you are being consistent.
This also matters for fairness in a market as international as Singapore. A written reason is reviewable. A remembered impression is not, and impressions are where inconsistency hides, usually without anyone intending it.
Step 7: Audit Decisions Against Performance at Six Months
Twice a year, put the debrief records next to how those hires actually performed. You are looking for three patterns:
- Which interviewer predicted well. Some people are consistently right and quiet. Those are your deciders, and they are frequently not the most senior person available.
- Which signals predicted nothing. Every team carries at least one interview question it is attached to and which has never once correlated with performance. Find it and drop it.
- Which dimension keeps being the surprise. If month-three surprises cluster in one area, that area is under-covered in step 1 regardless of what the map says.
Keep it small. Two hours, twice a year, on the hires you have six months of evidence for. The exercise fails when it becomes a performance review of the interviewers rather than of the process.
| Step | Cost | The failure it prevents |
|---|---|---|
| 1. Coverage map | 15 min per role | Four opinions on one dimension, none on three others |
| 2. Written submission first | 10 min per interviewer | Anchoring and seniority weighting |
| 3. Scorecard not comparison | Zero | Bar drifting with pipeline quality |
| 4. Fixed order, weakest first | Zero | Attention going to the loudest view |
| 5. Four outcomes, no maybe | Zero | Candidates lost to silence |
| 6. Reason and counterfactual | 2 min | Unreviewable, inconsistent decisions |
| 7. Six-month audit | 2 hours, twice a year | A process that never learns |
The 4 Things This Will Not Fix
- A bad role definition. If nobody agrees what the person will do, a structured debrief produces a well-documented argument about an undefined job. Fix the role first; the debrief will make the confusion visible, which is useful but not the same as solving it.
- Interviewers who do not know what good looks like. Structure organises judgement, it does not create it. A panel that has never worked with a strong engineer in a given area will produce confident, well-formatted notes about the wrong things.
- A pipeline with nobody in it. Decision quality is irrelevant at the top of an empty funnel. If you are choosing between two candidates because two is all you have, the work is upstream in sourcing.
- Compensation that is not competitive. You can run an excellent process and lose every candidate at offer. If that is your pattern, the debrief is not the problem and tightening it further will not help.
For the stages around this one, see our methods for running remote technical interviews and reference checks on Singapore developer hires, and for the build-versus-hire question our guide to custom software development in Singapore.
Frequently Asked Questions
How many people should be in a developer hiring debrief?
What if the interviewers genuinely disagree?
Does this slow hiring down in a competitive market like Singapore?
How does this work when part of the panel is in another timezone?
Start with the coverage map, not the meeting
We help Singapore employers tighten the decision end of hiring, then shortlist pre-vetted developers who can be assessed against a real scorecard rather than a general impression.
Get startedRelated reading: Evaluating full-stack developers · Remote technical interviews · Reference checks for developer hires
