By Johnny Campbell
Introduction
Attention to detail is not checking everything. Checking everything is just slow. What you actually want is a candidate who can look at a piece of work and tell you, fast, which three things in it would cause real damage if they were wrong—and then be immovable about those three while letting the rest go. The person who proofreads a throwaway Slack message with the same care they’d give a client contract does not have high standards; they have poor judgement about risk, and in a busy role that judgement failure will cost more than the odd typo ever would. The candidate who ships a slightly scrappy internal deck but has triple-checked every figure in the board pack is doing the job properly. Detail is a budget. Good candidates spend it where the blast radius is biggest.
Most interviewers assess this badly, and they do it in three predictable ways. The first is asking “are you detail-oriented?” and accepting yes—nobody has ever said no. The second is treating a typo-free CV as evidence, when it’s the most heavily edited document a candidate will ever produce and tells you almost nothing about how they behave at 5pm on a Thursday with two competing deadlines. The third is the sneakiest: rewarding perfectionism. Interviewers hear “I can’t let anything go until it’s right” and mark it up, when the role actually needs someone who triages ruthlessly and ships. That’s not a strong hire. That’s a bottleneck with good intentions.
This page covers 24 interview questions across four capability areas: Catching Errors Before They Ship, Judgement About Which Details Matter, Precision Under Time Pressure, and Building Systems That Catch Mistakes. Every question is designed to make a candidate produce a specific incident rather than a philosophy. We’ve drawn on structured interview research and our own patterns across thousands of candidate assessments to isolate the questions that expose real judgement about risk, not just carefulness.
Catching Errors Before They Ship
What good looks like
A strong candidate can point to a specific error they caught—not a general sense of carefulness—and explain the mechanism that surfaced it: a re-read, a cross-check against another source, a gut instinct they then verified rather than dismissed. They catch their own mistakes as readily as other people’s, and they can describe what actually happened when something did slip through, including who it affected and what fixing it cost.
Behavioural questions
- Tell me about an error you caught just before something went out the door.
- What was the thing, and who would have seen it if it had shipped?
- What specifically made you look again at that point rather than trust your first pass?
- How close to the deadline was it, and what did fixing it cost you?
- Who else found out, and did anything change afterwards because of it?
- Walk me through the last time you found a mistake in your own work.
- What was the mistake, and how long had it been sitting there before you found it?
- What were you doing when you spotted it—were you looking for it or did it surface on its own?
- What did you do in the moment you found it, before you told anyone?
- Did you go back and check for the same mistake elsewhere? What did you find?
- Describe a situation where you spotted an error in someone else’s work.
- Whose work was it, and what was your relationship to them?
- How did you raise it—directly with them, or through some other channel?
- What was their reaction, and did it change how they took feedback from you afterwards?
- What would have happened if you’d said nothing?
- Tell me about a time you noticed something was wrong before you could explain why.
- What was the first thing that felt off, even before you could name it?
- How long did it take you to work out what it actually was?
- What did you do while you still couldn’t explain it—did you flag it or keep it to yourself?
- Were you right? What happened when you finally traced it?
- Walk me through a mistake that made it out to a customer or client.
- What was the mistake, and how did you find out—did the customer tell you, or did you catch it?
- What did it cost—money, time, trust, or something else?
- What did you personally do in the hour after you found out?
- What changed afterwards so it couldn’t happen the same way twice?
- Describe a piece of work you refused to sign off on.
- Whose work was it, and what pressure were you under to approve it anyway?
- What specifically was wrong, and how did you explain it to them?
- What was the reaction—did they agree, push back, or go over your head?
- What happened to the deadline once you held the line?
Situational scenario
You’re reviewing a client-facing report an hour before it’s due to go out. You find a calculation error in one of the headline figures—fixing it properly means re-running numbers that feed three other sections, and there’s no time to redo all of them before the deadline. Your manager is in back-to-back meetings and unreachable for the next ninety minutes. The client has already been told the report is coming at the top of the hour.
Walk me through what you do from the moment you spot the error.
Then introduce a constraint: “You reach your manager with five minutes to spare and they tell you to send it as-is and flag the correction separately afterwards. What do you do?”
What to listen for
whether they treat the deadline or the accuracy of the headline figure as the thing they protect first, whether they check the other three sections for the same error or assume it’s isolated, and whether they push back on the instruction to send it as-is or simply comply.
Judgement About Which Details Matter
What good looks like
A strong candidate triages consciously. They can name a specific detail they chose not to check, explain the reasoning behind that call, and describe what they focused on instead. They don’t apply uniform care to everything regardless of consequence, and they don’t confuse thoroughness with value—they can tell you, unprompted, which details in a piece of work would actually cause damage if wrong, and which wouldn’t.
Behavioural questions
- Tell me about a detail you deliberately let go.
- What was the detail, and what told you it wasn’t worth the time?
- What were you spending that time on instead?
- Did anyone challenge the decision to skip it? What did you say?
- Did it ever come back to bite you, even slightly?
- Walk me through how you decided what to check on your last major deliverable.
- What was the deliverable, and who was it going to?
- What did you check first, and why that before anything else?
- What did you deliberately not check, and how did you decide that was safe to skip?
- How much time did the checking actually take against the time you had?
- Describe a time you were told your work wasn’t thorough enough and you disagreed.
- Who told you, and what specifically did they think you’d missed?
- What was your reasoning for the level of detail you’d applied?
- How did you make your case to them—did you push back in the moment or think it over first?
- Where did it land—did they change their mind, did you, or did you agree to disagree?
- Tell me about a small detail that turned out to matter far more than you expected.
- What was the detail, and why did it seem minor at the time?
- What surfaced that showed you it mattered more than you’d assumed?
- What did it end up costing, or nearly costing?
- What do you check differently now because of it?
- Walk me through a piece of work where getting it perfect would have been the wrong call.
- What was the work, and what would “perfect” have actually required?
- What did you produce instead, and how did you decide where to stop?
- Did anyone push you to keep polishing it? What did you tell them?
- How did it land once it was out—did the level of finish hold up?
- Describe a time you pushed back on a request for more detail.
- Who asked for it, and what more were they wanting?
- What was your reasoning for saying the extra detail wasn’t worth it?
- How did they respond—did they accept it, insist, or meet you halfway?
- Looking back, were you right to push back?
- Tell me about a detail you missed that you now check for every single time.
- What was the detail, and how did you find out you’d missed it?
- What was the actual consequence, however small?
- What specifically do you do differently now—describe the check itself?
- Has that check ever actually caught something since?
Situational scenario
You’re finishing a proposal document for a major prospective client, due out this afternoon. You’ve checked all the pricing and the core commercial terms twice. With twenty minutes left, you notice the appendix—a technical spec sheet nobody reads closely—has an outdated product name in three places, and the formatting is slightly inconsistent throughout. Fixing the appendix properly would mean missing the deadline by at least half an hour.
Walk me through what you do with the twenty minutes you’ve got left.
Then introduce a constraint: “Your manager, copied on the email thread, replies-all: ‘Make sure it’s perfect before it goes, we can’t afford to look sloppy.’ What do you do now?”
What to listen for
whether they hold their triage decision when told to make it perfect, or fold and let a cosmetic detail eat time that should protect the deadline; whether they explain their reasoning to the manager rather than silently comply or silently ignore the instruction; and whether they can articulate, specifically, why the appendix carries less risk than the commercial terms.
Precision Under Time Pressure
What good looks like
A strong candidate can describe what they protect and what they sacrifice when the clock runs out, rather than claiming they maintain the same standard regardless of time pressure. They know which checks are non-negotiable even under pressure, which corners can be cut safely, and they’re honest about the times accuracy suffered because the deadline genuinely couldn’t move. They ask for more time when the risk warrants it, rather than quietly hoping for the best.
Behavioural questions
- Tell me about a time you had to get something exactly right on a deadline you couldn’t move.
- What was it, and what would “wrong” have actually cost?
- How much time did you have, realistically, once you accounted for everything else on your plate?
- What did you cut to protect the accuracy of the thing that mattered?
- Did you make the deadline, and was it actually right?
- Walk me through the last piece of work you shipped knowing it wasn’t fully checked.
- What was left unchecked, specifically?
- Why did you decide to ship anyway rather than push the deadline?
- Did you flag to anyone that it wasn’t fully checked, or did you keep that to yourself?
- Did anything come of the parts you didn’t check?
- Describe a situation where speed and accuracy pulled in opposite directions.
- What was the work, and who was pushing for speed?
- Where exactly did you feel the pull—what were you tempted to skip?
- What did you actually do, and how did you decide?
- What was the outcome for both the timeline and the accuracy?
- Tell me about a time you asked for more time to check something.
- Who did you ask, and how did you justify the extra time?
- What was the reaction—did they grant it easily or push back?
- What did you find in the extra time that justified the ask?
- What would have happened if you’d been told no?
- Walk me through how you handled a task that arrived with no notice and no margin for error.
- What was the task, and how much notice did you actually get?
- What was the first thing you did once it landed on your desk?
- What did you check first, and what did you decide you didn’t have time to check at all?
- How did it turn out?
- Describe a time you had to verify something you had no easy way to verify.
- What was it, and why couldn’t you check it directly?
- What did you do instead—what’s the actual mechanism you used?
- How confident were you in the answer you landed on?
- Were you right, and how did you find out?
Situational scenario
You’re two hours from sending a contract renewal to a client, and legal signs off at 5pm sharp today or the deal slips to next quarter, which your VP has said isn’t an option. Reviewing it one final time, you spot that the payment terms clause doesn’t match the number you verbally agreed with the client last week—a difference that could cost roughly £15,000 over the contract term depending on which version is right. You can’t reach the client’s procurement contact, and legal is unavailable until tomorrow morning.
Walk me through what you do in the two hours you’ve got.
Then introduce a constraint: “At 4:40pm your VP messages: ‘Just send it, we’ll fix it in an amendment if it’s wrong.’ What do you do?”
What to listen for
whether they treat the £15,000 discrepancy as something to resolve before sending or something to paper over afterwards, whether they push back on the VP’s instruction or simply follow it, and whether they can articulate what “we’ll fix it in an amendment” actually costs in practice—client trust, renegotiation leverage, or both.
Building Systems That Catch Mistakes
What good looks like
A strong candidate has moved beyond personal vigilance towards building something repeatable—a checklist, a second-reader step, a template, an automated check—that catches mistakes even when they’re not the one looking. They can point to a specific near-miss that triggered the system, describe how it actually works day to day, and say whether it’s been tested by a real failure since it went in.
Behavioural questions
- Tell me about a check or process you created after something went wrong.
- What went wrong first, specifically, that made you build the check?
- What does the check actually consist of—walk me through the mechanics?
- Who else uses it now, or is it still just you?
- Has it caught anything since you put it in place?
- Walk me through the last time you reviewed someone else’s work formally.
- Whose work was it, and what was the review meant to catch?
- What did you actually look for, specifically?
- What did you find, and how did you raise it with them?
- Did the review change anything about how they worked afterwards?
- Describe a situation where an existing process failed to catch a mistake.
- What was the process meant to catch, and what got through anyway?
- How did you find out the process had failed?
- What did you do about the process itself afterwards?
- Is the gap actually closed now, or just patched?
- Tell me about a recurring error you eliminated rather than kept catching.
- How many times had the error happened before you decided to fix the root cause?
- What was actually causing it, once you dug in?
- What did you change, specifically?
- How do you know it’s actually gone rather than just less frequent?
- Walk me through what you do differently now compared to two years ago.
- What’s the specific habit or check you do now that you didn’t then?
- What happened that caused the change?
- How did you build it into how you work, rather than just intending to?
- Has anyone else adopted it from you?
Situational scenario
You’ve just joined a team where the same type of error—wrong figures making it into client-facing decks—has happened three times in the last six months, each time caught by luck rather than any check. There’s no review step before decks go out. You’re not the manager, and the team is already stretched thin on time, so any new process has to survive people being busy.
Walk me through how you’d approach fixing this in your first month.
Then introduce a constraint: “You propose a second-reader step and your manager says the team doesn’t have time for another layer of review. What do you do?”
What to listen for
whether they investigate what actually caused the three errors before proposing a fix, whether they design something lightweight enough to survive a stretched team or just restate the ideal solution, and whether they find a way to make the case to their manager with evidence rather than dropping the idea.
Red flags to watch for when assessing Attention to Detail
They can’t name a single detail they deliberately deprioritised. This suggests they either don’t triage, or they triage unconsciously and can’t defend the calls they make. Both are a problem when the stakes rise.
Every error example is someone else’s error they caught, never their own they missed. Nobody’s record is that clean. This is either poor self-awareness or a candidate managing you, and neither improves after they start.
The mistake they own is always cosmetic. A typo in a headline, a wrong date on a calendar invite. Candidates who only confess to trivial errors are protecting something. Ask directly for the most expensive mistake they’ve made.
They describe checking as an emotional state rather than a behaviour. “I just have a really good eye” or “I can’t help noticing things” tells you nothing you can score. Real answers contain artefacts: a checklist, a second reader, a query they ran, a number they recalculated.
Their quality control depends entirely on themselves. No peer review, no automated check, no template, no handover step. Vigilance without system fails the first time they’re tired or absent.
They frame perfectionism as a virtue with no cost attached. If they can’t name a deadline it slipped or a colleague it frustrated, they haven’t examined it—and you’ll be managing that blind spot later.
How to Use These Questions in a Structured Interview
These questions only work if you probe—the first answer is rarely the full one. Pick one opener per capability area, ask the same few to every candidate for the role, and score with a 1/3/5 rubric. A 1 is a hypothetical or a philosophy—“I always double-check everything.” A 3 is a real incident with a real outcome but thin reasoning about why that detail mattered. A 5 is a specific incident where the candidate explains the trade-off they made, names what they let go, and can point to the mechanism that caught—or failed to catch—the problem. The probes carry more weight than the opener: almost nobody prepares for “what else were you not checking at the time?” or “who would have caught it if you hadn’t?”
Calibrate your panel before you interview, not after. Get two or three interviewers to score the same recorded answer independently and compare; if they land a full band apart on the same evidence, the rubric isn’t the problem—your shared definition of the competency is. See how Interview Intelligence solves this → by surfacing exactly where interviewers diverge on the same behaviour, before it costs you a hire.
Frequently asked questions
What's the difference between attention to detail and perfectionism?
Attention to detail is selective. It means identifying which details carry risk and applying rigour there while accepting rough edges elsewhere. Perfectionism is indiscriminate - the same standard applied to everything regardless of consequence, which reliably produces missed deadlines and blocked colleagues. In interview, the tell is triage. A detail-oriented candidate can name something they let go and explain why. A perfectionist usually can't, and often treats the question as a trap.
How do you assess attention to detail without a work sample test?
Behavioural questioning works well if you probe for mechanism rather than outcome. Ask what the candidate checked, what they didn't, how they knew where to look, and who would have caught the error if they hadn't. Real experience produces specific artefacts - a checklist, a query, a second reader. Rehearsed answers produce adjectives. Work samples are useful, but they test performance under observation, which is not the same thing.
Should I use spelling and grammar in a CV as an indicator?
No, or at least not as primary evidence. A CV is heavily edited, frequently reviewed by others, and sometimes professionally written, so it says more about the candidate's investment in this application than their day-to-day standards. It also disadvantages non-native English speakers and some neurodivergent candidates for reasons unrelated to the job. If written precision genuinely matters in the role, test it with a task that mirrors the actual work.
How many attention to detail questions should I ask in one interview?
Three or four openers, probed properly. Attention to detail is rarely the only competency you're assessing, and a single well-probed question yields more usable evidence than four asked at surface level. Budget roughly eight to ten minutes per opener if this is a core competency for the role, and use the same openers with every candidate so your scores are comparable.
What if the role doesn't obviously involve detailed work?
Almost every role has a category of detail where errors are expensive - a figure in a client proposal, a name in an offer letter, a permission setting, a date in a contract. Identify that category before you interview and anchor your questions to it. Assessing generic carefulness produces generic answers; assessing the specific detail that carries risk in this role produces evidence you can actually make a decision on.