It's 11pm and you're adjusting the margins again. You've read that recruiters spend six seconds per resume, so you've moved your strongest bullet up, swapped the font, tightened the summary, and run the whole thing through a free ATS checker that gave you an 87 and a green checkmark. You submit to four more jobs before bed. Two weeks later, the count stands where it stood last month: thirty applications, one automated rejection, twenty-nine silences.
So you do what everyone does — you go looking for the flaw in the document. Wrong template, maybe. Missing keywords. A formatting quirk that's tripping the software. The entire resume-advice industry is built on this assumption: that somewhere between your experience and the page, something got lost in transmission, and if you just fix the transmission, the callbacks come.
Here's the thing that took me too long to understand: for most people, the document is fine. The transmission is fine. What's failing is the thing being transmitted.
The polish ceiling
There's a level of resume quality below which formatting genuinely costs you interviews — unreadable layouts, walls of text, a file the software can't parse. Most people who are actively job searching cleared that bar months ago. Past it, polish stops mattering, because polish was never what anyone was screening for. You can't format your way into a callback any more than you can fix a weak argument by improving the kerning.
What a hiring manager is actually doing in those six seconds is running one question against your resume: has this person solved problems shaped like mine, at a scale that matters to me? Every resume that gets a callback answers that question fast and concretely. Every resume that doesn't — including beautifully formatted, keyword-complete, ATS-approved resumes — fails to answer it. The silence you're getting isn't the software rejecting your document. It's a human being reading it, finding no proof, and moving on.
What "no proof" actually looks like
Pull up your resume and look at your bullets honestly. Most of them probably describe responsibilities: "Managed a team of five." "Oversaw the quarterly planning process." "Responsible for client relationships across the eastern region." These sentences are true, and they prove nothing. They describe the chair you sat in, not what happened because you were the one sitting in it. Every other candidate for the role sat in a similar chair, and their resumes say nearly identical things. The hiring manager can't tell any of you apart, so they pick the candidates whose resumes make the differences visible.
The differences live in outcomes and situations. "Managed a team of five" proves nothing; "took over a team of five that had missed three consecutive quarters and got them to plan in two" proves quite a lot. The second version isn't better-written — it contains different information. It has a starting condition, a problem with stakes, and a measurable change. That's evidence. The first version is a job description wearing your name.
This is the diagnosis most people resist, because it's harder to fix than a template. The reason your bullets describe responsibilities instead of outcomes usually isn't laziness. It's that you never captured the outcomes when they happened, and now, sitting at the keyboard months or years later, you can't reconstruct them. You know the quarter went well. You don't remember the number. You know the project was a mess before you got there. You can't articulate what made it a mess. The evidence existed once, and nobody taught you to keep it.
The second failure nobody checks for
There's a quieter version of the same problem, and it gets even strong resumes ignored: the evidence is real but it's pointed at the wrong target. You're a generalist applying to a specialist role, or a specialist applying one level up, and your resume — full of legitimate, well-quantified accomplishments — never quite answers the specific question this specific posting is asking. The hiring manager isn't looking for proof that you're good. They're looking for proof that you're good at this, and proof of adjacent things doesn't transfer the way you'd hope.
The honest test: take the last job you applied to and write down, in one sentence, the problem that role exists to solve. Then find the bullet on your resume that proves you've solved it before. If you can't find the bullet, the silence isn't mysterious. Either the evidence exists in your history and never made it onto the page — a selection failure, fixable tonight — or it doesn't exist yet, which means you're applying to roles one notch outside what your record supports. That's fixable too, but not with a resume edit. It's fixable by aiming at roles where your proof is direct, or by building the missing evidence where you work now.
Notice that neither failure has anything to do with fonts.
What to actually do
Stop editing the document and start auditing the evidence. Go through your last three roles and, for each one, write down every situation where something was broken, behind, ambiguous, or at risk — and what changed because of what you did. Get numbers where numbers exist. Where they don't, get honest specifics: how long it had been broken, how many people were affected, what would have happened otherwise. This takes a few hours and it is worth more than every template you will ever download, because it's the raw material every application draws from.
Then, for each job you apply to, do the one-sentence problem test before you submit. Lead with the evidence that hits that problem hardest. If you run the test and keep coming up empty across many postings, take the data seriously — it's telling you where the gap actually is, and a gap you can name is a gap you can close.
The applications that get callbacks aren't the most polished ones. They're the ones where a tired hiring manager, forty resumes deep, hits a bullet that makes them stop scrolling and think: this person has been where I am. You can't format your way to that sentence. You can only have done the thing, remembered it, and put it on the page.
Tell me if this tracks with what you're seeing. I'm especially curious about people who fixed the evidence and still hear silence — that's a different problem, and I'd want to know about it.
Prism Tree exists for the evidence audit — it interviews you about your career, extracts the situations and outcomes you never wrote down, scores them against the competencies that matter, and builds every resume from your strongest proof instead of your job titles. Try it here.