Skip to content

Careers

How to pull the right keywords out of a job description

A repeatable method for extracting the terms that matter from a job posting, deciding which belong on your resume, and placing them where they read naturally instead of stuffed.

7 min read · updated 10 September 2026

"Add keywords" is the most repeated and least explained piece of resume advice. Which words? How many? Where? Done badly it produces a skills section that lists forty tools you have touched once, which reads as noise to a recruiter and helps you with none of them.

Here is the method I use, which takes about fifteen minutes per application and is deliberately boring.

Step 1: separate the posting into four buckets

Read the description once with a notepad open and sort every requirement into four buckets: systems, methods, domain and behaviours.

  • Systems are named products: SAP, Ariba, Power BI, Tableau, Oracle, SQL, Excel, Python.
  • Methods are activities: forecasting, variance analysis, month-end close, budgeting, reconciliation, data modelling.
  • Domain is context: manufacturing, FMCG, capex-heavy projects, shared services, listed-company reporting.
  • Behaviours are how the work happens: business partnering, stakeholder management, working with auditors.

Step 2: mark each term honest, partial or absent

Against each term, mark whether you could talk about it for five minutes under questioning. Honest means yes, with an example. Partial means you have used it under supervision or adjacent to it. Absent means no.

Honest terms go on the resume. Partial terms go on only where you can attach the true scope — "supported" or "contributed to" is fine and defensible. Absent terms stay off, permanently. A skills line you cannot defend costs you the interview, not the screen.

Step 3: place terms where they earn their space

Keywords work best distributed across three zones rather than piled into one list. The summary carries your function and two or three headline systems. The skills block carries the rest of the systems and the methods, grouped so a reader can scan. The experience bullets carry the same terms again, but attached to evidence.

That repetition is not stuffing. It is the difference between claiming a skill and demonstrating it: "Power BI" in a skills list plus "rebuilt the weekly spend dashboard in Power BI, cutting refresh from 40 minutes to 3" in a bullet.

Step 4: match the employer's vocabulary, not your own

Companies name the same work differently. Management reporting, MIS, business reporting and performance reporting can all describe one job. Search is literal, so use the phrase from the posting as the primary and keep your own preferred phrase as a secondary mention if it is also common in your market.

The same applies to titles. If you are a "Finance Executive" applying for "Financial Analyst", put the target title in your headline and keep your official title in the experience block where it belongs. That is accurate, not inflated.

Step 5: cut before you submit

A skills section is more persuasive at twelve items than at thirty-five. Remove anything that is assumed at your level (email, MS Word), anything you marked absent, and anything unrelated to the role you are applying for. The signal comes from concentration.

Frequently asked questions

How many keywords should a resume contain?
There is no target count. Cover the must-have systems and methods from the posting, each mentioned once in a list and ideally once in evidence. Beyond that, extra terms dilute rather than help.
Do I need a separate 'Keywords' section?
No. A grouped skills block does the same job and reads like a document written for humans.
Is it dishonest to use the employer's job title in my headline?
Not if your actual titles appear correctly in the experience section. A headline states the role you are applying for; the history states fact.

Put it into practice

The readiness check lists the missing terms and the exact section each one belongs in.

Score a draft against a job description

Written by Syed Danish Arafat, a financial analyst working in FP&A, reporting and finance automation. Shared for educational purposes — review anything here against your own circumstances before acting on it.