I’ve sat through thousands of interviews and reviewed countless resumes over the years. The pattern that emerges is consistent: the candidates who get hired rarely owe it to their credentials alone. Experience matters, certainly, but it’s rarely the deciding factor. What moves someone from a stack of qualified applicants to an actual offer comes down to things that don’t fit neatly into a resume bullet point.
The first thing I notice is how someone handles a question they can’t answer. This happens in nearly every conversation I have with candidates. Someone asks about a specific tool, methodology, or situation, and the candidate doesn’t know the answer. What happens next tells me far more than any previous job title could. Do they freeze? Do they deflect? Or do they acknowledge the gap, ask clarifying questions, and think through it out loud? The last response signals someone who can actually work in an unfamiliar space, which is what most roles demand once you’re past the first few months.
Reliability is another thing that barely registers on resumes but dominates hiring decisions. I’m not talking about showing up on time, though that matters. I mean the kind of reliability where someone says they’ll do something and it gets done without constant follow-up. This sounds obvious, but it’s genuinely rare. In interviews, you can sense this in how someone talks about past commitments. Do they describe projects they owned, or do they describe what happened around them? Do they mention obstacles they worked through, or do they explain why things didn’t go as planned? The distinction is subtle but revealing.
How People Respond to Setbacks
I’ve learned to listen closely to how candidates describe failures or difficult situations. Everyone has them. What varies wildly is how they frame them. Some people describe a failure and immediately pivot to what they learned. Others describe a failure and spend most of the time explaining why it wasn’t really their fault. Both types exist in the workforce, but only one type tends to move forward effectively when problems arise – which they always do.
The ability to work with ambiguity is something I’ve come to value more as organizations have become less structured. A candidate might have ten years of experience in a highly defined role, but if that experience taught them to wait for clear instructions and perfect information before acting, they’ll struggle. Conversely, someone with less experience who has worked in startup environments or fast-moving teams often brings a comfort with incomplete information and the ability to make reasonable decisions with what’s available. This isn’t about being reckless; it’s about knowing when to move forward despite uncertainty.
Communication and How People Listen
Communication skills get mentioned constantly in job descriptions, but most people interpret this as “speaks clearly.” What I’ve found matters more is how someone listens and responds to feedback. During interviews, I’ll often ask a follow-up question that slightly contradicts or complicates something a candidate just said. Some people defend their original answer. Others pause, consider the new information, and adjust their thinking. The second group tends to integrate feedback more effectively once hired.
I’ve also noticed that people who ask good questions during interviews tend to be people who ask good questions on the job. This seems obvious, but it’s not universal. Many candidates treat the interview as a performance where they’re supposed to demonstrate knowledge rather than understand the role. The ones who ask about team dynamics, decision-making processes, or how success is measured are usually the ones who figure out their role more quickly and cause fewer problems in the first months.
Initiative without needing permission is harder to assess than it sounds. Some candidates describe situations where they identified a problem and solved it. Others describe situations where they were assigned a problem and executed well. Both are valuable, but the first type tends to require less management overhead. In established organizations with clear processes, this matters less. In growing companies or teams dealing with change, it’s often the difference between someone who makes the team better and someone who fills a seat.
Technical Depth Versus Adaptability
There’s a tension I encounter regularly between candidates who are very deep in one specific area versus candidates who are broadly capable across several domains. Neither is inherently better. But I’ve learned that the right choice depends entirely on the role’s stability. If the role is well-defined and unlikely to change significantly, deep expertise in exactly the right area is valuable. If the role will evolve, if the team is small, or if the organization is navigating change, adaptability and the ability to learn quickly often outweigh specific expertise.
The candidates I’ve seen struggle most are those who are genuinely skilled in their domain but have never had to learn something outside it quickly. They often underestimate how long learning takes and overestimate how much their existing knowledge transfers. The candidates who thrive are those who have done this before – who know what it feels like to be incompetent at something and have worked through it.
I’ve also paid attention to how people talk about their previous employers and colleagues. This isn’t about whether they’re positive or negative. It’s about whether they demonstrate understanding of other people’s constraints and motivations. Someone who can explain why a previous manager made a decision they disagreed with, or why a colleague approached something differently, tends to navigate team dynamics more effectively. Someone who only describes situations from their own perspective often struggles to understand why people don’t immediately agree with their ideas.
At the end of the hiring process, what separates a strong candidate from a merely qualified one usually comes down to whether they seem like someone who will figure things out when they encounter something unexpected. This doesn’t require perfection or extensive experience. It requires honesty about what you know and don’t know, a track record of following through, and genuine curiosity about how things work. These qualities don’t appear on a resume, but they’re visible to anyone paying attention during a conversation.
