TL;DR: Farah Sharghi, a recruiter who has screened resumes at Google, TikTok, Uber and The New York Times, wrote for CNBC that the biggest resume mistake she sees is one candidates literally cannot see: writing the resume for the one reader who already knows the whole story, which is you. She names four ways this red flag shows up. All four are real. But there’s a fifth, and it hides inside the bullets that look like they already passed the test.
Every so often a mainstream outlet publishes career advice that names the exact problem we built Resumes Coach to fix. This CNBC piece by ex-Google recruiter Farah Sharghi is one of those.
Her core claim: when you write about your own work, you know what the project was, why it mattered, and what the results meant. The recruiter reading it knows none of that, and has about six seconds to figure it out. So the mistake she’s pointing at isn’t a typo or a formatting sin. It’s writing every line for a reader who was in the room. That mistake is invisible to you for the same reason it exists: you were in the room.
Her test for it is simple and worth stealing. Cover your name at the top of the page. If what’s left could belong to any other candidate, the value of your work is not translating.
She breaks the mistake into four red flags. Here they are, briefly, with what we’d add to each. Then the fifth.
The four red flags Sharghi names
1. The “you had to be there” language. Her example: “Conducted financial analysis on operating spending and budget trends to support strategic planning and decision-making.” The writer knows exactly what that meant. To anyone else it’s fog. Her fix is to add context: what the organization does, what your role was inside it, explained the way you’d explain it to a friend.
We’d add: this is also the line a generic rewriter produces when it has nothing specific to work with. Recruiters have learned to skim past that cadence, which is a problem of its own.
2. The number that never explains itself. “Add metrics” is the most repeated resume advice there is, and she’s careful to say it’s still good advice. It is, when you do it right. But “$630,000 in Q2” means nothing on its own. Sales? Savings? Donations? A number only becomes an accomplishment when the reader knows what it measures.
Hold this one. It’s where the fifth red flag lives, and we’ll come back to it.
3. The insider shorthand. “Owned the Atlas migration via the FRED pipeline” is a foreign language outside your old team. Internal tool names, project codenames, company acronyms: her fix is to describe what the thing actually was, plainly enough that someone in a different industry could follow it.
We’d add: the codename doesn’t just confuse, it shrinks. “Owned the Atlas migration” could be a weekend script or a two-year program spanning forty teams, and the shorthand flattens that scale to zero. Screening software is an even colder reader than the recruiter, and it can’t match “Atlas” to the plain skills the job description actually names.
4. The “skill” that’s really an adjective. “Excellent communication. Team player. Detail-oriented.” Nearly every resume claims these, which is exactly why they carry no weight. Her rule: if you can’t prove it with a specific example, it’s an adjective, not a skill, and it should go. “Supported English- and Spanish-speaking customers for four years” shows communication. The word “communication” only claims it.
We’d add: every adjective on that list is a bullet you haven’t written yet. “Detail-oriented” is the ghost of a story about the error you caught before it shipped. Find the incident behind the adjective and write that instead.
All four share one root. Each one leaves out something the writer knew so well they forgot the reader wouldn’t. Context, referent, translation, evidence. Which is why the checklist approach works: you can hunt each form down and fix it.
Except the fifth red flag survives the checklist.
The fifth red flag: the number that hides its difficulty
Remember the number we asked you to hold back in red flag two. This is where it comes back. Sharghi’s rule there was that a metric has to explain what it measures, and it does. But a number can clear that bar, and every other bar she sets, and still quietly undersell you.
Take a bullet that passes all four of her tests:
“Grew quarterly revenue from $2.1M to $2.4M as regional sales lead.”
Context is there. The number explains itself. No jargon, no adjectives. By the checklist, this bullet is done.
Now read the version the same person could have written:
“Grew quarterly revenue from $2.1M to $2.4M as regional sales lead, with the team at half strength through a company-wide hiring freeze.”
Same numbers. Same role. Completely different accomplishment. The first version is a decent quarter. The second is the same quarter won short-handed. And the only difference is one clause naming the thing that made the result hard.
Where the clause sits matters too. A skimming reader catches the front of a bullet and fades by the tail, so a constraint buried at the end of a long line can go unread. When the difficulty is the story, let it lead: “Through a company-wide hiring freeze, grew quarterly revenue from $2.1M to $2.4M with half the team.” Either way, one clause usually carries it. The constraint is there to add weight, not to take over the bullet.
That clause, the circumstance that made the result hard, is what we call the missing constraint: the piece of context that turns an ordinary-looking number into a feat.
It disappears from resumes for exactly the reason Sharghi describes: you forgot the reader wasn’t there. You lived the hiring freeze, the budget cut, the legacy system, the half-sized team. To you, that was just the weather.
So when you sit down to write the bullet, the difficulty doesn’t feel like information. It feels like background. It gets left off the page, and with it goes the part of the story that made a hiring manager lean in.
This is why the fifth red flag is nastier than the other four. The first four produce bullets that look wrong once you know what to look for. Vague verbs, naked numbers, codenames, adjectives: they show up on a second pass.
The fifth produces bullets that look finished. The metric is there, the context is there, and the bullet still undersells you, because a result without its constraint reads as easier than it was.
Recruiters can’t ask for what they don’t know is missing. They read “grew revenue 14%” and file it as ordinary. The market decided years ago that everyone should quantify, so quantified-but-flat is now the baseline.
What separates bullets in 2026 isn’t the presence of a number. It’s whether the number comes with the circumstances that give it weight.
If you want the full argument for why the difficulty is the load-bearing part of a bullet, we wrote about it in You Didn’t Forget to Quantify. You Forgot It Was Hard.
One caution. The constraint has to be real, and the numbers have to be yours. Reconstruct what happened, never invent it, because a circumstance you can’t back up in an interview is worse than a flat bullet.
And choose the headwind with care. A hiring freeze, a budget cut, a legacy system all read as things you overcame. A setback a reader could pin on you, like losing your biggest accounts, isn’t a question your resume should raise, and anything your old employer would call confidential stays off the page too.
All of which assumes you can spot the missing constraint in the first place, and that is the part you cannot do alone.
Why you can’t see any of the five
Sharghi’s cover-your-name test works because it forces a cold read. But your own read can only get so cold. You can’t unknow your own context, so every one of the five forms stays hidden from the one person editing for them: you.
After the fortieth pass, the jargon looks normal and the naked number still feels impressive, because you can see the brutal quarter behind it. The cold reader can’t. That’s why the same number lands as ordinary on their side of the desk, the difficulty has quietly faded into “just my job.”
The reliable fix is what Sharghi points to, and what we built: let a reader who wasn’t in the room see the page.
Her version is a friend, or your grandmother, or a stranger. Ours is a cold read you can run in two minutes: the free resume score reads your resume with zero context, no account needed, and shows you where the writing assumes a reader who was there. And if you’re already with us, a Deep Dive goes bullet by bullet and points to the constraint your own read skipped.
Cover your name and read the page. If it could be anyone’s, the recruiter reading it will agree. The four fixes above will get you most of the way back. The fifth is remembering that what made the work hard was never background. It was the point.