When a resume gets passed over, the reflex is to stuff it with terms from the job posting. That backfires in two ways: a recruiter spots hollow buzzwords in seconds, and you set yourself up to answer for skills you can't demonstrate in an interview. There's a better move — close the real gaps, and name the ones you can't.
Read the posting like a checklist, not a wish list
Start by pulling the concrete, repeatable terms out of the job description: tools, methods, certifications, domains, and named responsibilities. Ignore the soft filler ("fast-paced environment," "team player") and mark the hard nouns — "incident response," "Snowflake," "SOX compliance," "A/B testing." Those are the terms a reviewer and an automated screen both look for. Now sort them into three buckets:
- Terms you've done but didn't name. You ran the work; your resume just uses different words.
- Terms you've touched. Adjacent or partial experience — you supported it, learned it, used it once.
- Terms you genuinely lack. No honest claim available.
Rephrasing real work vs. fabricating
The first bucket is where most legitimate gains live. Rephrasing is renaming work you actually did to match the posting's vocabulary. If you "wrote automated checks that ran on every merge" and the posting says "CI/CD," those are the same thing — use their term. If you "cleaned and joined data from three source systems," and they say "ETL," say ETL.
Fabricating is different: it's claiming a tool you never opened, a scope you never owned, or an outcome that didn't happen. The test is simple — could you talk for five minutes about a specific time you did this? If yes, it's rephrasing and you should use their words. If you'd have to invent the story, it's a fabrication and it stays off the page.
When a keyword isn't supported
Some terms in the posting you just don't have. That's not a failure of the resume — it's information. You have three honest options:
- Leave it off and lead with strength. A partial match with real depth beats a full match built on air. Most roles don't require every listed item.
- Name it as a gap you're closing. If you're mid-way through learning a tool, say so accurately: "currently building X through a project" is a true statement, not a claim of mastery. A cover letter is a natural place to address a visible gap directly.
- Re-target. If a posting's core requirements are terms you'd have to invent, that role may be a stretch worth skipping in favor of ones your evidence actually fits.
Anchor every term to evidence
A keyword should always trace back to something you can point to — a project, a metric, a shipped feature, an artifact. This is where working from a collected record of your own career pays off: when you keep a running Memory Board of real projects and outcomes, matching a posting becomes a lookup rather than a guess. Tools like FilterProof lean on exactly this — surfacing which posting terms your evidence supports and which are honest gaps, so you rephrase where you can and address the rest openly.
The goal isn't to mirror the job description word for word. It's to make sure every term a resume claims is one you'd be glad to be asked about. Depth you can defend will always read as more credible than a wall of keywords you can't.