Why resumes are no longer enough to decide who to interview

You open the applications folder and there are forty. Then eighty. All with action verbs, all “results-oriented,” all with the same tool list you asked for in the posting. You read ten in a row and they start to blur: nobody stands out, nobody fails, and you have to choose who to call tomorrow. The resume did its job of selling itself. The problem is that it told you almost nothing about who performs.

This isn’t the applicant’s fault, or yours. It’s a limitation of the format. The resume is a document the person writes about themselves, optimized to pass the screen. When most people have learned to write it well —and with writing assistants, almost everyone does— the resume stops separating candidates. You end up deciding by intuition, by the name of the previous company, or by the order in which they arrived. And that is exactly what you wanted to avoid.

The resume states; it doesn’t demonstrate

A resume is a list of claims: “I led,” “I implemented,” “I improved.” They are statements with no verifiable counterpart at the moment of screening. It’s not that they lie —it’s that there is no way to tell a solid claim from an inflated one just by reading it. “Three years in customer service” can mean someone who resolved complex cases on their own, or someone who escalated everything to their manager. Same line, opposite performance.

Origin bias creeps in here too. We tend to trust the resume that comes from a known brand or a familiar university more, even though that says nothing about how the person will handle the actual work. Screening by the reputation on the letterhead is comfortable, but it isn’t the same as screening by the ability to do the job. If you want to go deeper into that difference, we develop it in resume vs. evidence.

When everyone looks good, you need another layer

The hardest moment of screening isn’t discarding the weak ones —that’s quick. It’s choosing among ten profiles that look equally competent on paper. That’s where the resume has already given everything it had and falls short.

What does help is adding a layer of comparable evidence before the interview: a signal of how each person performs in situations similar to the role, measured the same way for everyone. It doesn’t replace what you see in the resume; it complements it. The resume tells you what the person says about themselves; the evidence shows you how they respond to what the role actually demands.

What changes when you compare against the same yardstick

When you define which competencies matter for that role and observe each candidate facing the same situations, two things happen. First, a role fit indicator appears that orders the stack by something more than the prose of the resume. Second, the team stops debating loose impressions (“I liked how they express themselves”) and starts talking about common, comparable criteria.

That doesn’t mean automating the decision. It means you arrive at the interview knowing what you want to confirm about each person, instead of discovering it on the fly. The interview stops being a blind first contact and becomes a focused conversation.

How this translates into your process

In practice, this flips the order of your funnel. Instead of reading forty resumes and guessing, you let each candidate show how they approach tasks relevant to the role, and you use that signal to prioritize who to spend your interview time on. The resume is still part of the reading —it tells the career story— but it no longer carries the whole decision alone.

To build that screen, it helps to combine competencies based on what the position actually needs, rather than copying a generic template. You can see how those combinations are built in the library and review a step-by-step process in deciding who to interview.

The team keeps the final decision

None of this makes the decision for you. The evidence orders the conversation and gives you backing to justify who you call and who you don’t —useful when someone on the team asks “why this one and not the other?”. But reading the context, the team culture, and the final judgment remain with people. Kokoro supports the decision; it does not make it.

This matters for being fair to applicants too: a common yardstick reduces the weight of who wrote a better resume or which brand they carry on their letterhead, and lets you decide by how they respond to the work.

In short: if your resume stacks all look the same, it’s not that you lack candidates —you lack evidence to tell them apart. Define the role’s competencies, add a comparable layer before interviewing, and reserve your interview time to confirm, not to discover. The resume opens the door; the evidence tells you who to let through first.