I've interviewed hundreds of people across Adobe, Zendesk, and Intelegencia. The candidates who became exceptional had one thing in common that never showed up on a CV, a skills test, or a reference check. Here's what it is - and how to spot it in 20 minutes.
A few years ago, I was interviewing someone for a senior role on my team. Strong background, good references, clear communicator. About twenty minutes in, I asked about a project that hadn't gone well - a detail from their CV that I'd noticed but not flagged. I wasn't trying to catch them out. I just wanted to understand what happened.
They paused. And then they said something I didn't expect: "Honestly, I made a call that seemed right at the time and it wasn't. I had more certainty than the situation deserved, and I didn't listen to the two people on the team who were flagging concerns. I learned more from that six months than from anything that went well."
No deflection. No reframing. No "the team didn't execute" or "the scope changed on us." Just a clear account of what they got wrong and what they took from it.
I hired them. They were one of the best people I've ever worked with.
The Thing That Actually Predicts Performance
After interviewing hundreds of people across Adobe, Zendesk, and now Intelegencia - across customer success, operations, digital marketing, and delivery teams - I've come to believe that one quality predicts long-term performance more reliably than anything else on a CV.
It isn't intelligence. Smart people are everywhere and the delta between the smartest candidate in the room and the most capable hire is often enormous. It isn't experience - experienced people can be the most difficult to work with when they stop being curious. It isn't confidence, ambition, or even the specific skills the job description asked for.
It's intellectual honesty. Specifically: the ability to say "I was wrong" without it threatening who they are.
This sounds simple. It is extraordinarily rare.
Why This Trait Is So Hard to Find
Most hiring processes inadvertently screen for the opposite. The interview is a performance context. You've been taught since your first job application to put your best version forward, talk about your strengths, frame failures as learning experiences without dwelling on them, and project certainty and confidence.
So when I ask "tell me about a time something went wrong," most candidates have a rehearsed answer. They describe a situation, a challenge, their actions, and a positive outcome. The failure becomes a setup for a personal victory narrative. It's technically responsive and reveals almost nothing.
The candidates who stand out aren't the ones with the smoothest answer. They're the ones who get slightly uncomfortable - not because they're unprepared, but because they're actually thinking about it. They might say something like "I've been thinking about this one for a while and I'm still not sure I got it right." They don't rush to the resolution. They sit in the complexity for a moment before explaining their thinking.
That discomfort is information. It means they're actually engaging with the question rather than retrieving a pre-packaged answer. And the way they emerge from it - whether they're honest about the mess, or whether they quickly reassemble the narrative into something that makes them look competent - tells you almost everything about how they'll function inside a team.
What It Actually Looks Like in Practice
Intellectual honesty in the room shows up in specific ways. The candidate asks a clarifying question rather than confidently answering something they don't fully understand. They say "I'm not certain about this part" rather than bluffing through it. When they disagree with something you've said, they say so - not aggressively, but directly - instead of nodding along.
These feel like small things. They're not. In an enterprise context, in customer-facing delivery, in any role that involves making decisions under uncertainty and then adjusting when new information arrives - these behaviours compound over time into the difference between a team that surfaces problems early and one that surfaces them after they've become crises.
I've seen this play out across large account teams at Adobe and Zendesk. The pattern is consistent: the people who are most afraid of being wrong in the room are the ones who let things run longer than they should before raising their hand. The data point that should have changed the strategy gets buried for another quarter because admitting it feels like admitting failure. The client conversation that should have happened in month four doesn't happen until month eleven.
The person who can say "I think I read this wrong and here's what I'm seeing now" - they surface that problem in month four. That's the difference between a fixable situation and a lost account.
The Hiring Question That Reveals It
There is one question I come back to in almost every interview. It's not original - I've heard variations of it from other leaders - but I've found no better version of it.
"Tell me about a position you've held where you were the most uncertain about whether you were doing the right thing. Not a project - the role itself. What was that uncertainty and what did you do with it?"
The answers fall into two camps, clearly.
One camp answers with a story about a difficult situation that they navigated, where uncertainty was external - the company was going through change, the market was unclear, the brief kept shifting. They were the stable point in an uncertain environment. These are often well-told stories and sometimes impressive. But the uncertainty is always outside them.
The other camp answers with something more personal. The uncertainty was about themselves - whether they were growing fast enough, whether the way they were approaching relationships with their team was actually right, whether a decision they'd made was good or just defensible. Whether their instincts were trustworthy. These answers are harder to listen to, less polished, and almost always more revealing.
The second camp is who I hire.
Why It Matters Even More Now
There's a specific reason this trait has become more important, not less, as organisations pile AI tools into their operations.
When you have AI surfaces generating outputs, making recommendations, flagging risks - and a team member who cannot question their own certainty sits between the AI and the decision - you get confident, fast, wrong conclusions. The AI told them X, they believed it without interrogating it, and the decision got made. Intellectual honesty is the human check on automated systems. Without it, automation doesn't reduce error - it accelerates it.
I work with teams who are integrating AI into customer success, operations, and delivery workflows. The team members who are most effective with AI tools are not the most technically proficient ones. They're the ones who look at an AI-generated output and say "this doesn't quite fit what I know about this account - let me check." They hold the output lightly. They engage with it as a starting point rather than an answer. That disposition - sceptical, curious, willing to be wrong and willing to question what looks right - is the same one that shows up in the interview answer I described above.
It's the same trait. Just in a different context.
What This Means If You're Looking for a Role
I've written this from a hiring perspective, but I think there's something here for people on the other side of the table too.
The candidates who get stuck in job searches - strong backgrounds, doing all the right things, not landing the roles - are often performing confidence rather than demonstrating capability. The CVs are polished. The answers are rehearsed. The self-presentation is tight. And something in the interview feels slightly off to the hiring manager, though they often can't articulate exactly what.
What's missing is texture. The mess. The moment where something didn't work and the person engaged with that genuinely rather than retreating to a polished narrative. That texture is what makes a person feel real across a table. It's what makes a hiring manager think: I know what I'm getting. I trust this.
If you're currently looking for a role, I'd try this: in your next interview, find one moment to be honest about something that didn't go perfectly without immediately pivoting to the silver lining. Not to dwell, not to invite sympathy - just to let the complexity sit for a sentence or two before you move forward. See what it does to the energy in the room.
In my experience, it tends to change something. The conversation stops feeling like a performance and starts feeling like one person talking to another.
That's when the interesting conversations begin.
