A candidate is perfect twice in a lifetime: once at birth, once on the resume. Everything in between is messier, and the resume is built to hide the mess. It is a marketing document, not a record of the person behind it. Yet most hiring authorities read it like a verdict, and the quality of the hire suffers for it.

I read resumes the way an underwriter reads a loan application: as a set of claims to price and probe, not facts to accept. The resume tells me what the candidate wants me to know, in the order they want me to know it. That is useful information about how they sell themselves. It is not evidence of how they work. The leaders who hire well are the ones who hold that distinction in their head from the first page. The lever was never the document. It is the judgment you bring to it.

So the real question is not whether a resume lies. Of course it does, by omission if nothing else. The question is what you can rightfully deduce from it, and where you have to stop deducing and start asking.

What a resume can mostly tell you

Some signals on the page are reasonably reliable, as long as you treat them as starting coordinates rather than conclusions.

  • Trajectory and industry experience. Has the candidate stayed in one sector or moved across several? Are they taking on more responsibility over time, or holding the same altitude for years? Growth in scope is visible. Its cause is not.
  • Technical skills and certifications. If a role needs a PMP, an OSHA 30, or specific software fluency, the credential should be on the page. Its absence is a real flag. Its presence is a claim you can verify.
  • The employment timeline, with caveats. You can see frequent moves, long stretches, and gaps. You cannot see why any of them happened. The dates are facts. The story behind the dates is not on the page.
  • How they present themselves. A clean, considered resume suggests attention to detail and effort. A sloppy one suggests carelessness, though not necessarily incompetence. Presentation is a proxy, and a weak one.

Read that list again and notice the pattern: every reliable signal is about what, never why. The resume sets up the right questions. It does not answer them.

What a resume cannot tell you, no matter how hard you stare

Here is where most bad hires are born: a leader treats an inference as a fact. Four blanks on the page get filled in by assumption, and the assumption goes unexamined.

Why they left. A short tenure does not mean job hopper. It might mean layoffs, a bad manager, a culture that never fit, a relocation, or a better offer. A long tenure does not mean loyal. It might mean risk aversion, comfort, fear of change, or simply no better door opening. Both readings are guesses until you ask: "What moved you to leave that company?" or "If I call your last boss, what will they say about why you left?"

How well they actually performed. A listed accomplishment does not prove the candidate drove it. A title does not prove they earned it or executed at that level. So make them show the work: "Tell me about a project where you directly moved the outcome." "If I call your peers, what will they say about your contribution?"

Work ethic, attitude, ownership. No resume reveals whether someone is humble, durable under pressure, or honest about their own mistakes. It will not show you whether they take ownership or hunt for someone to blame. Behavioral questions do that work: "Tell me about a mistake you made and how you handled it." "Describe a conflict with a coworker and what you actually did."

Whether they fit how your company runs. Personality, communication style, and values do not survive translation onto a page. Someone can look ideal on paper and grind against your team the first week. What you are listening for in the interview is consistency, humility, and self-awareness: "What kind of environment lets you do your best work?" "What feedback changed how you operate?"

The two ways assuming gets you

The danger runs in both directions, and most leaders only guard one.

Read too optimistically and the polish costs you. A clean resume can mask thin skills or a weak work ethic. An impressive title can sit on top of mediocre execution. A long run at a respected company does not certify a strong performer. You hire people, not documents, and the document is the least reliable part of the person.

Read too skeptically and you delete the best person in the pile before you ever speak to them. Short tenures can each have a clean explanation. A gap can be caregiving, a downturn, or a season of real growth. A plain resume can belong to an exceptional builder who simply never learned to sell themselves on paper. Disqualify on the page alone and you will miss matches that would have outperformed everyone you did interview.

Every reliable signal on a resume tells you what happened. None of them tell you why. The why is the entire job.

Read it as a roadmap, not a ruling

The resume earns its keep when you use it the way it was built to be used: as the opening map for a conversation, not the final word on a candidate.

  • Hunt for patterns across the whole document, not isolated facts you can react to.
  • Let it shape your questions around experience, motivation, and self-awareness.
  • Treat it as the candidate's sales pitch, because that is exactly what it is.

The underwriting mindset is curiosity with a paper trail. You take every claim on the page as a hypothesis, then build the interview to test the ones that matter most. The candidates who pass are not the ones with the cleanest formatting. They are the ones whose answers hold up when you stop reading and start listening.

The page can only ever set the questions. What you do with the next hour is what actually tells you who you are about to hire.