You Can Be Qualified and Still Look Unqualified on Paper

You can be capable of doing a job and still look unqualified for it. I know because I've watched my own resume do exactly that.

Chemistry graduate. Laboratory intern. Customer service representative. Science tutor. Give that fifteen seconds and you could probably guess what kind of person wrote it. You'd be wrong about the part that matters most.

Nothing on that page is false. Every line is true. That's what makes the problem interesting. My resume isn't lying to anyone. It's just incomplete. It doesn't say I've spent months teaching myself SEO, building a real portfolio, researching how people actually search for things, writing articles, learning how content gets surfaced in AI search, and figuring most of it out by doing rather than being told. None of that shows up in a bullet point because none of it happened inside a job title someone gave me.

I used to think this was just my problem, a career changer's problem. It isn't. In a recent U.S. survey, more than half of job seekers said they'd been turned down for roles they were genuinely qualified for, while nearly half of hiring decision-makers said candidates can lose out because they struggle to demonstrate their skills clearly. So the feeling isn't just mine. It has a pattern behind it.

Take the one line on my resume about the portfolio. It says I built and published a portfolio blog covering SEO, AI search optimization, and content writing. Accurate, and almost useless as a description of what actually happened.

It doesn't say I had to pick a subject worth writing about. Research what people were genuinely typing into a search bar. Look at what was already ranking and figure out what was missing. Decide how to structure the piece so it actually answers the question instead of just filling a word count. Publish it. Wait. Check what happened. Notice what didn't work and change it. Do that again.

A sentence took five seconds to read. The work behind it took months.

The same compression happens to people whose experience has nothing to do with a career change. Someone's resume might say they taught Biology and Chemistry. That tells you what subject they were responsible for. It tells you nothing about whether they can take the same idea and explain it three different ways to three different students until it actually lands.

Someone else's resume says they handled customer inquiries. That could mean someone who read from a script all day. It could just as easily mean someone who spent months talking down angry strangers, figuring out what they actually needed underneath what they were shouting about, and knowing exactly when a problem needed to go over their head instead of staying with them.

Same words. Completely different person underneath.

None of this means resumes are useless, and I don't think that's actually the honest complaint here. A recruiter can't spend an hour learning who you really are, so they reach for something faster. A degree stands in for education. Years of experience stand in for exposure. A job title stands in for whatever you were responsible for while you held it. A resume, in the end, stands in for capability.

All of that is fair, and all of it is necessary. The problem was never that employers use these shortcuts. The problem starts when the shortcut gets treated as the actual thing it was only ever standing in for.

The hiring world is already half aware of this. A lot of employers now say they've moved toward hiring for skills rather than credentials. At the same time, most are still leaning on resumes to figure out what those skills even are. That's the industry catching itself mid-contradiction.

So if the old evidence—the job title, the years, the degree—can't fully speak for someone who's grown past it, the honest answer isn't a better resume. It's more evidence sitting next to it.

A writer publishes something instead of just calling themselves one. A designer shows something they built instead of describing an eye for it. Someone learning data analysis actually analyzes a real dataset instead of listing the skill.

Don't tell someone you're capable. Give them something they can actually judge for themselves.

My own portfolio exists for exactly this reason, because my employment history was never going to be the one telling this particular story.

If you'd looked at my resume a year ago, you'd have seen someone with a Chemistry degree trying to work out what came next.

Look at it now and you'll still see a Chemistry graduate, a lab intern, a customer service representative, a tutor.

That's the strange thing about a resume.

It's very good at telling you where someone has been.

It's much worse at telling you where they're going.

Sometimes the person applying for the job has already become someone their resume hasn't caught up with yet.