9 min read
You've added every keyword from the posting. The skills line is full, and the match score still looks flat. That isn't a sign you're underqualified. It's a placement problem.
Check your resume for free and look at which required terms appear only once. A term that lives in one list and nowhere else is the first one to fix.
This page shows how keyword context affects resume ranking through before and after bullets, role by role. You'll leave with a formula you can paste into your own file tonight.
If you've been told to stuff more keywords in, you've probably been given advice that makes the page worse. Repetition without context reads as noise to a human and carries little weight as evidence.
Quick Wins
- Pick the three required skills in the posting. Find the most recent job bullet where you used each one.
- Rewrite that bullet so the skill sits in the first eight words, followed by an object and an outcome.
- Trim the skills list to the terms you can back up with a bullet.
One keyword, two placements, two different signals
Take the word Salesforce. In a skills list it says you've heard of it. In a bullet it says what you did with it, for whom, and what changed.
Before: Skills: Salesforce, Excel, SQL, Tableau, Communication, Leadership
After: Built a Salesforce renewal dashboard for 14 account managers, which cut missed renewals in the first quarter.
Recruiters read the second line as proof. Software that scores for context tends to treat a term with a verb, an object, and a result around it as stronger evidence than a bare token.
Run a two-minute audit before you rewrite anything. Open the posting and your resume side by side, then work through this short list.
- Circle the five terms the posting repeats or lists as required.
- Search your resume for each one and count where it appears.
- Mark any term that shows up only in the skills section.
- Mark any term that shows up only in a job from several years ago.
Every mark is a rewrite target. Terms with no mark are already doing their job, so leave those bullets alone.
A skills list names the tool. A bullet shows the tool in use. That gap is the whole lesson, and the rest of this page is practice.
Six rewrites that move a keyword into context
Each pair below starts with a bare term from a skills list and ends with a bullet that earns it. The names and numbers are illustrations of a fictional candidate's file, not claims about the market.
Customer support: Zendesk
Before: Skills: Zendesk, CRM, Customer Service
After: Resolved 60 weekly tickets in Zendesk by building macros for refund requests, which kept first replies under two hours.
Data analyst: SQL
Before: Skills: SQL, Python, Looker
After: Wrote SQL queries against the orders database to build weekly churn dashboards in Looker, cutting reactive tickets 11% in Q3.
Recruiting coordinator: Greenhouse
Before: Skills: Greenhouse, Scheduling, Sourcing
After: Scheduled 25 interviews a week in Greenhouse and kept candidate status current, so hiring managers stopped asking for manual updates.
Project manager: Jira
Before: Skills: Jira, Agile, Stakeholder Management
After: Ran two-week Jira sprints for a team of eight and cleared a 40-ticket backlog before the product launch.
Marketing coordinator: HubSpot
Before: Skills: HubSpot, SEO, Email Marketing
After: Built three HubSpot email sequences for trial users and lifted trial-to-paid conversion by 6 points over one quarter.
Healthcare administration: Epic scheduling
Before: Skills: Epic, Scheduling, HIPAA
After: Managed Epic scheduling for a six-provider clinic, reducing same-day gaps by filling cancellations from a standing wait list.
I've read stacks of these in Greenhouse, and the skills line rarely decides it. The bullet under the latest title does.
The bullet formula to paste into your own file
Here's a copy-paste skeleton. Fill the brackets from your real work, and keep the keyword in the first eight words.
[Action verb] [keyword from posting] to [object you worked on], [outcome with a number or a named result].
Example:
Built Looker dashboards for the support team to track ticket volume, which cut reactive tickets 11% in Q3.
If you can't add a number, add a named result instead: a faster handoff, a cleaner report, a launch that shipped on time. If you can't name any result, the bullet isn't ready yet.
Edge case: the skill came from a project, class, or volunteer role. Put the bullet under that role and label it plainly. A real project with a named tool and a result is better evidence than a bare term in a list, and it keeps you honest if the recruiter asks about it.
Put the strongest rewrites under your most recent job first. A term from your latest role reads as current. The same term in a job from several years back reads as history.
Where context rewrites go wrong
Stuffing the same keyword into every bullet. Three bullets that all start with Salesforce read as filler. Use the term where you used the tool, and stop.
Adding a skill you can't discuss. A recruiter will ask about it in the first call. If the bullet is thin, so is your answer.
Keeping an unrelated list. A skills section with twenty terms and no matching bullets weakens the ones that do have proof. Cut the list to the terms you can show.
Writing the keyword last. A bullet that mentions the tool at the end of a long sentence hides it. Move it up, then add the object and result.
This won't turn a poor match into a good one. If the posting needs five years of a tool you haven't used, no placement fixes that. It does keep a real skill from sitting unseen in a list.
If your bullets read well but get rejected anyway, why strong experience still gets rejected covers what happens beyond keywords.
Check which terms still sit alone
Run HireFlow's free ATS resume checker against your target posting and note every required term that shows up only in the skills section. Those are your rewrite targets.
When a term only has proof in a side project or volunteer role, generate a cover letter that names that project in one sentence, so the recruiter sees the evidence even if the bullet sits lower on the page.
Do this now: Choose one posting, find the three terms with no bullet behind them, and rewrite one bullet per term before you apply.
Make each keyword earn its place
Keywords matter, but where they sit matters more. Your skills list opens the door, and the bullet under your current job proves you belong in the room.
- Keep the skills list short and honest.
- Repeat each key term once, inside a recent bullet.
- Pair the term with an object and an outcome.
- Skip any keyword you can't discuss out loud.
Run one more free ATS check after the rewrites to confirm each term now lives in a bullet.
Read more
Frequently asked questions
Usually twice: once in a short skills list and once in a recent job bullet with an object and an outcome. More repetition rarely helps and can read like stuffing. If a term matters to the posting, make the bullet stronger instead of adding another mention.
Recruiters read the most recent roles first, so a term in your current job reads as active use. A term from an older job still helps as background. If a required skill appears only in old roles, add it to a current bullet where it honestly applies.
No. A short skills section helps both parsers and quick human scans. Keep only the terms you can back up with a bullet, and group them in a few plain lines. A long list of unproven terms weakens the ones that have proof.
Use a named result instead of a number: a report that shipped on time, a process that replaced a manual step, a launch that met its date. If you can't name any outcome, the bullet isn't ready, so describe the work in more detail first.
