Every Resume Looks Perfect Now: How to Find the People Who Can Actually Do the Job

If you have hired for anything in the last year, you have probably noticed what I have: the applications look great. All of them.

A resume used to carry a signal. Writing a good one took effort, self-awareness, and enough judgment to know what mattered for the role. That filter is gone. Anyone can produce a polished, keyword-matched application in a few minutes now.

So the stack in your inbox looks stronger than it ever has, and it tells you less than it ever did. For a lot of founders, that feels like a reason to slow down hiring altogether. I would argue the opposite. It is a reason to change what you are measuring.

Presentation and performance were always different things

Even before AI, a resume showed where someone had been. It has never shown how they think. It cannot tell you how someone handles an ambiguous situation with a client, what they do when a project goes sideways three weeks before delivery, or whether they can operate at the size you are now rather than the size of the company they came from.

Those are the things that determine whether a hire works out. None of them appear on paper, and no amount of careful resume reading will surface them.

Think about hiring a contractor to renovate your kitchen. Their website looks professional, the photos are beautiful, and the quote is well written. You would still ask to see the last three kitchens they finished, and you would still call the homeowners.

Hiring works the same way. The application gets someone into the conversation. It should never be the thing that carries a person through the conversations.

The problem compounds as you grow

One open role means more applications to review. Three open roles at once and review time becomes the bottleneck in your entire process.

Founders respond the way anyone would. They skim faster and lean harder on surface signals like recognizable company names and familiar job titles. That is exactly when strong candidates get passed over, and polished ones move forward.

Build a process that tests for the work

The fix is to evaluate for capability rather than presentation. Four things make most of the difference:

1. Scenario-based questions built from your actual business. Hypotheticals produce rehearsed answers. Real situations produce thinking.
2. Live problem solving. Give candidates something to work through in front of you. Watching someone think tells you more than hearing them describe how they think.
3. The same questions for every candidate. Consistency is what makes comparison possible. When every interview goes in a different direction, you compare impressions instead of evidence.
4. Reference checks that verify. Confirming employment dates is not a reference check. Ask former managers about the specific behaviors your scenarios surfaced.

None of that requires a large team or expensive software. It requires deciding what "good" looks like for the role before you start talking to people.

What that looks like in practice

Here is an example of the first two working together. When a professional services firm hires its first salesperson, we run a live role-play. The candidate takes a discovery call with a prospect who looks exactly like the firm's real buyer, and we watch how they handle it.

What we are listening for has almost nothing to do with polish. Do they ask about the problem before they start describing services? Do they follow the thread when the prospect mentions something offhand about their team? Can they sit in a pause without filling it?

Candidates who have sold in a large company with inbound leads often struggle here, and that surprises founders who were impressed by the resume. The role at a 20-person firm requires someone who can create the conversation, not manage one that already exists.

Verification matters more than it used to

We run reference checks through Crosschq, which has built-in fraud detection. It has flagged candidates whose references were submitted from the same IP address as their own application. That has happened more than once, and it has changed hiring decisions.

Every step in a hiring process exists to surface something specific. When you skip steps to move faster, you remove the checks that catch problems before they cost you a year of salary and a year of momentum.

What this looks like when the process holds

One accounting firm came to us after paying roughly $60,000 in agency fees for two hires who were both gone within six months. They were out the money, out both employees, and close to turning away client work because they could not serve everyone.

The person we hired for them has been with the firm for three years and plays a significant role in the organization. Speed alone would have produced another vacancy. A defined role and a process built to test for it produced someone who stayed.

Start with two questions

When you are hiring for a role right now, write two scenario questions before you review another application. Pull them from situations that actually happened at your company in the last 90 days, and ask every candidate the same two questions.The answers will differ more than the resumes did.

Every candidate can look qualified now. Only some of them can do the job, and the only way to tell the difference is to build a process that asks them to.

If you are working through a hire right now and want a second opinion on your process, you can book a 30-minute conversation here.