Credentials are a map, not the territory
Credentials tell you where someone has been. Competency tells you what they can do next.
Most hiring mistakes happen because description gets mistaken for demonstration. Real competency shows up in specifics — the decisions made under pressure, the problems still remembered years later — not in prepared interview answers. Interviews that follow a candidate's own logic, rather than a fixed rubric, surface signal that no resume can carry.
Description is not demonstration
There is a difference between knowing where someone went and knowing what they can do. Most hiring processes are designed to assess the first thing while believing they are assessing the second. A resume lists employers, titles, and dates. An interview asks candidates to describe what those titles meant. But description is not demonstration, and the gap between the two is where most hiring mistakes live.
What competency actually sounds like
Competency is specific. It shows up in the details — the decision that wasn't obvious at the time, the system that broke in a particular way, the judgment call made with incomplete information. Someone who genuinely owned a product launch describes it differently than someone who was adjacent to one. The words they reach for, the parts they dwell on, the problems they're still thinking about years later — these are real signals. They don't fit on a resume.
Why most interviews miss it
The interview, in theory, is where those signals should emerge. In practice, most interviews are structured to confirm what's already on the resume rather than to discover what isn't. Candidates prepare answers. Interviewers ask questions they found on a hiring guide. The conversation is essentially a recitation — a verbal resume, with the same limitations as the written one.
What changes when you give space to talk
What changes when you give a candidate space to actually talk? They stop performing and start explaining. The difference is audible. Someone explaining a problem they've solved will loop back, correct themselves, add context that wasn't in the question. Someone performing a practiced answer will stay on script. Neither looks different on paper. In a real conversation, they are immediately distinct.
Competency interviews — ones that start open and follow the candidate's own logic rather than a fixed rubric — surface things that structured interviews miss. They catch people who are genuinely brilliant in ways that don't map to traditional markers. They also catch people who present confidently but don't go very deep when the follow-up questions get specific. Both kinds of signal matter, and both are invisible in a resume stack.
The proxy was never the thing
The move toward skills-based hiring is, at its core, a recognition that the proxy was never the thing. A degree from a prestigious institution is a proxy for learning ability, work ethic, and intellectual baseline. Those are worth caring about. But the proxy was always a shortcut, not a measure. When the shortcut became the standard, hiring optimized for the shortcut — and stopped asking whether the underlying thing was actually there.
What a good interview measures is not what someone has done. It is how they think about what they have done, what they understand about it, and what they would do differently. That understanding is the asset a company is actually hiring. The resume is just the cover of a book. Competency is what's inside.