By Johnny Campbell
Introduction
Humility has nothing to do with how modestly someone talks about themselves. Some of the most humble operators I’ve interviewed were also the most self-assured people in the room — they knew exactly how good they were and said so. The difference was what happened when they hit information that contradicted them. They changed position, they did it out loud, and they named the person who moved them. That’s the whole competency in one sentence: humble people update, and they say who updated them. The opposite isn’t loudness. It’s the person who quietly holds their original view, lets the meeting move on, and takes the credit anyway when the other approach works.
Most interviewers assess this badly, and they do it in three predictable ways. The first is rewarding candidates who downplay their achievements. “I was lucky”, “the team did most of it”, “I just helped where I could” — that’s a speech pattern, often a culturally learned one, and it tells you nothing about whether the person can take a correction. The second is asking about a weakness and getting back a rehearsed humblebrag, delivered with practised sheepishness — every candidate has that answer loaded before they sit down. The third is the biggest miss: interviewers almost never ask who the candidate was wrong about, or who corrected them, or what happened to their thinking afterwards. Humility is relational. If you only ask about the candidate, you can’t see it.
What follows is 24 behavioural and situational questions across four capability areas: admitting error in public, coachability and acting on feedback, giving credit and sharing attribution, and updating a strongly held view. Every question asks for a specific instance with a named person, a date, and a consequence, because that’s the only version of this competency that resists coaching. Use them alongside the red flags and scoring guidance that follow — humility is one of the easiest competencies to mis-score, and knowing how it goes wrong matters more than the questions themselves.
Admitting Error in Public
What good looks like
A strong candidate has told other people they were wrong while the consequences were still live, not once the risk had passed. They can name who they told, how soon after the mistake surfaced, and what it cost them to say it out loud — a redone piece of work, an uncomfortable conversation, a dent in how someone saw them. The error itself is usually unremarkable; what matters is that they owned it in public rather than managing the story.
Behavioural questions
- Tell me about a decision you got wrong that your team found out about.
- What was the decision, and how did the team find out — did you tell them or did they discover it?
- What was the immediate cost of the mistake, to the work or to how people saw you?
- What did you say to the team, specifically, once it was clear you’d got it wrong?
- What did you do differently on your next comparable decision?
- Walk me through the last time you told your manager you’d made a mistake.
- What was the mistake, and how much time passed between it happening and you telling them?
- What made you decide to tell them rather than let it surface on its own?
- What was their reaction, and what did they say back?
- What changed about how they managed you afterwards, if anything?
- Describe a situation where you had to correct something you’d already presented as fact.
- What had you presented, and to whom?
- What told you it was wrong, and how long after you’d presented it?
- How did you make the correction — did you go back to everyone, or let it surface naturally?
- What did it cost you in credibility, and did it recover?
- Tell me about a time you were the reason a project missed its deadline.
- What was the project, and what specifically did you do or fail to do that caused the slip?
- Who had to be told, and how did you tell them?
- What was said to you in response that you remember clearly?
- What did you change about how you work as a direct result?
- Walk me through how you handled being wrong in front of a customer or client.
- Who was the customer or client, and what were you wrong about?
- What did you say to them in the moment, as close to verbatim as you can recall?
- What did it cost — the relationship, the deal, your own standing internally?
- What would you do differently if it happened again tomorrow?
- Describe a mistake you made that someone else initially got blamed for.
- Who got blamed, and how long did that last before you corrected it?
- What made you decide to correct it, and to whom did you say it?
- What did it cost you to set the record straight?
- What happened to the person who’d been wrongly blamed once it was corrected?
Situational scenario
You approved a vendor contract six weeks ago based on numbers you now know were wrong — you misread a discount clause, and the actual cost is 30% higher than what you told your leadership team. The budget has already been signed off on your figure. Your leadership team meets tomorrow morning to review quarterly spend.
Walk me through what you do between now and that meeting.
Then introduce a constraint: “Your manager tells you privately that you could quietly correct it in the next budget cycle instead of raising it tomorrow, since the difference won't be visible until then. What do you do?”
What to listen for
whether they surface the error before it's found rather than waiting for cover, whether they tell their manager directly that they disagree with sitting on it, and whether their plan protects the people who relied on the wrong number rather than just their own position.
Coachability and Acting on Feedback
What good looks like
A strong candidate can describe a specific piece of feedback that changed what they actually did, not just how they felt about themselves. They can name who gave it, what it was, and the concrete behavioural change that followed — something they started, stopped, or did differently from a specific point onward. Receiving feedback well is not evidence of coachability; a documented change in behaviour is.
Behavioural questions
- Tell me about a piece of feedback you rejected at the time and later accepted.
- Who gave it, and what was your reaction when you first heard it?
- What changed your mind — a specific event, a second conversation, more evidence?
- How long was the gap between rejecting it and accepting it?
- What did you do differently once you’d accepted it?
- Walk me through the most difficult performance conversation you’ve had about your own work.
- Who was the conversation with, and what was the substance of the feedback?
- What was your reaction in the room, versus what you did afterwards?
- What specifically changed in how you worked from that point on?
- How did that person’s view of you shift over the following months?
- Describe a time a junior colleague changed your mind about something.
- Who was the colleague, and what was their role relative to yours?
- What did they say or show you that moved you?
- What was your position before, and what is it now?
- Did you tell them they’d changed your mind, and how?
- Tell me about a skill you were worse at than you realised.
- What was the skill, and how did you find out you were worse than you thought?
- Who told you, or what evidence surfaced it?
- What did you do about it once you knew?
- How would you rate yourself on it now, and how do you know?
- Walk me through a change you made to how you work because of something someone told you.
- Who told you, and what did they say?
- What specifically did you change — describe the before and after?
- How soon after the conversation did the change happen?
- Has anyone noticed the difference, and what have they said?
- Describe a time you asked for feedback and got an answer you didn’t expect.
- Who did you ask, and what were you expecting to hear?
- What did they actually say?
- What was your first reaction, and what did you do with it after that?
- Did you act on it — what, specifically, changed as a result?
Situational scenario
A direct report gives you feedback in a one-to-one that your communication style makes people afraid to disagree with you in meetings. You don’t recognise the description of yourself at all — it doesn’t match how you see the last six months of team discussions.
Walk me through how you handle the rest of that conversation and the weeks after it.
Then introduce a constraint: “Two other people on the team later tell you, separately, that they agree with the original feedback but wouldn't have raised it themselves. Does that change what you do?”
What to listen for
whether they resist the urge to relitigate whether the feedback is fair before checking it against other evidence, whether they go looking for corroboration rather than waiting for more feedback to arrive, and whether the change they make is specific enough that someone could notice it.
Giving Credit and Sharing Attribution
What good looks like
A strong candidate gives credit to named individuals for specific contributions, not to “the team” in general, and can describe a time they corrected a wrong impression about who did what — including when the correction cost them recognition. They can point to a colleague, often a junior one, whose idea or catch mattered more to an outcome than their own, and say so plainly.
Behavioural questions
- Tell me about a success you were publicly credited for that you didn’t deserve.
- What was the success, and who else actually did the work?
- Where and how were you credited — a meeting, an email, a review?
- What did you do once you realised the credit was misplaced?
- What did it cost you to correct it, if you did?
- Walk me through the last time you put someone else’s name forward for something.
- Who was it, and what were you putting them forward for?
- What did they actually do that earned it?
- Who did you say it to, and what did you say specifically?
- What happened to them as a result, and what happened to your own visibility?
- Describe a piece of work where a colleague’s contribution was more important than yours.
- Who was the colleague, and what was the work?
- What specifically did they contribute that mattered more than what you did?
- How did you make that visible to others, if you did?
- Would most people looking at the outcome know that, or would they assume it was yours?
- Tell me about someone on your last team who knew something you didn’t.
- Who was it, and what did they know that you didn’t?
- How did you find out you were missing it?
- What did you do once you realised — did you go to them?
- What did you do with what you learned?
- Walk me through how a mentor or peer shaped a decision you’re known for.
- Who was it, and what’s the decision you’re known for?
- What specifically did they say or do that shaped it?
- How much of the credit for that decision, honestly, is theirs versus yours?
- Have you told them, or told anyone else, what their part was?
- Describe a time you corrected the record about who did what.
- What was the record, and who had it wrong?
- Who benefited from the wrong version, and who lost out?
- What did you actually say, and to whom?
- What did it cost you to say it?
Situational scenario
A piece of work you led is being praised in a leadership meeting, and the credit is landing entirely on you. In reality, a junior colleague on your team solved the hardest technical problem in it, working nights to do it, while you managed the timeline and the stakeholders. The junior colleague isn’t in the room.
Walk me through what you say in that meeting, and what you do afterwards.
Then introduce a constraint: “Your own manager is in the room, and this is the kind of moment that shapes whether you get considered for the next promotion. Does that change what you say?”
What to listen for
whether they name the colleague specifically and describe what they actually did, whether they do it in the room rather than only after the fact, and whether the promotion stakes visibly change what they're willing to say.
Updating a Strongly Held View
What good looks like
A strong candidate can name a position they held with genuine conviction and then abandoned, along with the specific evidence or person that moved them. They describe the update as a change in what they believe, not a concession made to keep the peace, and can say what they thought before, what changed, and what they think now. The absence of any such example is itself the signal.
Behavioural questions
- Tell me about the last thing you were confidently wrong about.
- What was the belief, and how confident were you — on what basis?
- What specifically proved you wrong?
- Who else knew you’d held that view, and did you tell them you’d changed it?
- What do you believe now instead?
- Walk me through a strategy you argued for that turned out to be the wrong call.
- What was the strategy, and who did you argue it against?
- What evidence eventually showed it was wrong?
- What did you say, and to whom, once you knew?
- What did you argue for instead the next time a similar decision came up?
- Describe a time the data contradicted something you believed about your own function.
- What did you believe, and how long had you believed it?
- What data contradicted it, and who brought it to you?
- What was your first reaction to seeing it?
- What did you change about how your function operates as a result?
- Tell me about a person you misjudged.
- Who was it, and what was your initial judgement of them?
- What changed your mind, and over what period of time?
- Did you tell them you’d misjudged them? What did you say?
- How do you treat first impressions differently now, if at all?
- Walk me through a view you held two years ago that you no longer hold.
- What was the view, and how strongly did you hold it at the time?
- What changed it — one event, or an accumulation of evidence?
- Who, if anyone, gets credit for shifting your thinking?
- What do you now think of the version of you that held the old view?
- Describe a time you changed your position after losing an argument.
- Who won the argument, and what was it about?
- What was the moment you knew you’d lost — what did they say?
- How did you concede, in the room or afterwards?
- What did you do differently afterward because of it?
Situational scenario
You’ve spent the last year publicly arguing for a strategic direction that you personally proposed and defended against real internal opposition. New data has just come in that seriously undermines your original case — not fatally, but enough that a fair reading suggests you were substantially wrong. The people who opposed you originally are in the room when the data is presented.
Walk me through what you do in that meeting.
Then introduce a constraint: “The data is ambiguous enough that you could reasonably argue it doesn't change anything, and nobody would call you out for making that case. What do you actually do?”
What to listen for
whether they name what specifically the data changes about their original view rather than defending the whole position, whether they say it in front of the people who opposed them rather than softening it in private later, and whether they can distinguish what they got wrong from what they still think they got right.
Red flags to watch for when assessing Humility
Every mistake is a mistake of over-ambition. “I cared too much”, “I pushed the team too hard”, “I set the bar too high” — that’s the humblebrag pattern, and it’s a rehearsed answer wearing a costume. Genuine error is usually boring: bad judgement, missed detail, wrong hire.
They can’t name a single person who has changed their mind on something that mattered. If the only people who influence them are books, podcasts or general “learnings”, the influence is abstract and probably invented.
Credit collapses into “we” the moment things go well, and sharpens into “I” the moment things go badly for someone else. Track the pronouns across the whole interview, not question by question.
The mistake is always safely historic. Everything they got wrong happened five years and two employers ago. Nothing recent, nothing from the role they’re leaving.
Feedback is described as received but never as acted on. “I took it on board” with no behavioural change attached is the tell. Ask what they did differently on the Monday.
Corrections only ever come from above. Managers and executives moved their thinking; direct reports, junior colleagues and support functions never did. That’s deference to hierarchy, not humility.
How to Use These Questions in a Structured Interview
Pick two or three capability areas rather than racing through all four — six to eight questions with real follow-up beats twenty-four skated over. Score on a 1/3/5 rubric: a 1 is no specific instance, or the only mistakes described are flattering ones; a 3 is a genuine, specific error or correction with a named source, but the consequences are vague and the behavioural change is asserted rather than described; a 5 is a specific instance, a named person who influenced or corrected them, a described cost, and a concrete change in behaviour the candidate can date. The probes matter more than the opener — ask who found out, what you said to them, what they said back, what you did the following week. A candidate who can’t populate a mistake with other people’s names and reactions is describing a mistake they’ve constructed for interviews.
One calibration warning worth taking seriously: humility is among the most frequently mis-scored competencies because interviewers read communication style as character. Quiet, self-effacing candidates score high without producing a single instance of updating; confident, direct candidates score low despite naming three people who changed their minds last quarter. Neither speech pattern is evidence — score the instances, not the delivery, and if you can’t point to the moment in the transcript that earned the score, you didn’t have evidence. See how Interview Intelligence solves this → by showing you what was actually asked and actually answered, not just the score someone wrote down afterwards.
Frequently asked questions
What is humility as an interview competency?
Humility is the ability to recognise the limits of your own judgement and act on that recognition. In practice it shows up as three behaviours: admitting error while the consequences are still live, changing your position when better information arrives, and attributing credit accurately to the people who earned it. It is a behavioural competency, not a personality trait, which means it can be evidenced with specific past instances rather than inferred from how someone talks.
How do you tell humility apart from low confidence?
Low confidence is uncertainty about your own ability. Humility is accuracy about it. A humble candidate will tell you plainly that they're excellent at something and then, in the next breath, name the person on their team who is better at a specific part of it. Low confidence produces hedging across the board and an inability to claim any achievement. Test it by asking what the candidate is genuinely best at — humble people answer directly.
Why is 'what's your biggest weakness' a poor humility question?
Because it is the most rehearsed question in interviewing. Every candidate arrives with an answer prepared, usually one engineered to sound like a flaw while functioning as a strength. It measures preparation, not self-awareness. Replace it with questions about specific incidents — the last thing they were confidently wrong about, or a piece of feedback they initially rejected — where the candidate has to produce named people and dated events.
Can you assess humility in a first-round screen?
Yes, with one or two questions. 'Tell me about someone on your last team who knew something you didn't' works well early because it's easy to answer honestly and hard to fake specifically. Save the harder probes on public error and reversed positions for a later stage, where you have the time to follow up properly and a second interviewer to calibrate against.
Which roles most need humility assessed?
Any role where being wrong is expensive and correction depends on other people flagging it — engineering leadership, clinical roles, senior sales, and anything with people management attached. It matters most where the candidate will hold more positional authority than the people closest to the information.