Keywords from job descriptions – Page 2

Include them when the posting mentions a version or when the version shows you are current. Otherwise, the plain tool name is usually enough.

Examples:

• If the posting says "SAP S/4HANA", write that rather than just "SAP".
• If the posting says "Python", "Python" is enough; you might add the libraries you use, such as "Python (pandas, NumPy)".
• For older versions, listing the year can make your skills look dated, so leave it out unless needed.

Keep the base tool name in the text so a search for it still finds you.

Write the full degree name, and add the abbreviation if you like. Some application systems look for degree level in your education section, and some employers screen on it, so being clear helps.

Examples:

• "Bachelor of Science (BSc) in Mechanical Engineering"
• "Master of Business Administration (MBA)"
• "Bachelor of Commerce (BCom), Accounting"

Include the subject, the institution and the year. If the posting asks for "a bachelor's degree in finance or a related field" and yours is in economics, write the exact name of your degree; do not change it to "finance". You can show related coursework or experience instead.

Use the title in the posting for your headline and summary, and keep your real past job titles as they were. Different employers use different titles for similar roles, so recruiters may search for any of them.

Example:

• Your past title: "Software Developer"
• Posting title: "Software Engineer"
• Headline: "Software Engineer | Java, Spring Boot, AWS"
• Summary: "Software developer with five years building backend services..."

This puts the employer's term at the top without changing your employment history. If your past title was unusual, you can add a short clarification in the bullets that describes the work in standard terms.

Put them where they are naturally true and easy to find: your headline, summary, skills section and, most importantly, your experience bullets. Each place does a different job.

• Headline: the target job title, such as "Financial Analyst".
• Summary: two or three of the most important skills or qualifications.
• Skills: a short, scannable list of tools and methods.
• Experience: the same terms used in context, showing where and how you used them.
• Education and Certifications: exact names of degrees, licences and courses.

Example of a keyword in context: "Built monthly variance reports in Excel and Power BI for a portfolio of 12 retail stores."

Keywords in your experience matter because they prove the skill. A term that appears only in a skills list is a claim; the same term in a bullet with a result is evidence. Recruiters notice the difference, and some systems may also consider where terms appear.

Avoid placing important terms only in headers, footers, text boxes or images, which some systems may not read.

Choose two or three of the most important terms and build a normal sentence around them. A summary should still sound like a person describing their work.

Robotic: "Results-driven SAP SQL Excel reporting analyst with stakeholder management skills."

Natural: "Finance analyst with four years of SAP and Excel reporting, preparing monthly management accounts for a regional distributor."

Tips:

• Lead with your target title or a close match.
• Add one or two hard skills from the posting.
• Add one result or area of focus.

Read the summary aloud. If it sounds like a search query, rewrite it.

Start with what you actually did, then use the employer's term for it. Good bullets combine an action, the keyword and a result.

Pattern: action verb + task using the keyword + result or scale.

Examples:

• Posting term "vendor management": "Managed 15 vendors for facilities services and renegotiated three contracts at lower rates."
• Posting term "patient education": "Delivered patient education on diabetes management to around 20 patients a week."
• Posting term "reconciliation": "Completed monthly bank reconciliation for four company accounts."

Use each important keyword in one or two bullets where it fits. Do not stretch a bullet to include a term you did not use in that job.

Usually not. A skills list helps searches and quick scanning, but it does not show that you used the skill. Recruiters look for proof in your experience, and some systems may also give weight to terms that appear in context.

Compare:

• Skills only: "Salesforce"
• Skills plus experience: "Salesforce" in skills, and "Tracked a pipeline of 80 accounts in Salesforce and updated forecasts weekly." in a job entry.

The second version answers the recruiter's real question: where and how did you use it?

Aim to have your most important keywords in both places. Less important ones can stay in the skills list alone.

They can help, but your resume matters more. Some application systems store and search cover letters, others do not, and many recruiters read the resume first. So put your important keywords in your resume, and use the cover letter to add context.

In the cover letter, use the employer's terms naturally while explaining why you fit:

Example: "In my current role I lead month-end close and IFRS reporting for three entities, which matches your need for a hands-on financial controller."

Do not paste a list of keywords into the cover letter. It should read as a short, personal letter.

A clear file name helps people, but adding keywords to it is unlikely to make a difference to screening. Use your name and the document type, and the role if you like.

Good examples:

• "Priya-Nair-Resume.pdf"
• "Priya-Nair-Data-Analyst-Resume.pdf"

Avoid file names stuffed with terms, such as "Data-Analyst-SQL-Python-PowerBI-Excel.pdf". It looks odd when a recruiter downloads it, and it does not replace keywords in the document itself.

Also avoid generic names like "Resume-final-v3.pdf", which are easy to lose among many applications.

Mention important keywords where they naturally belong, which is often two or three times, but do not repeat them for the sake of it. Repetition that serves no purpose makes your resume harder to read and can look like an attempt to game the system.

A natural pattern for a key skill such as "AutoCAD":

• Summary: "Civil engineer experienced in AutoCAD and Civil 3D."
• Skills: "AutoCAD, Civil 3D, Primavera P6"
• Experience: "Prepared road layout drawings in AutoCAD for two highway projects."

That is three useful mentions, each telling the reader something different. If you find yourself adding a word to a bullet only to raise a count, remove it.

No. "Keyword density" is a term from old website search techniques, and there is no published standard for resumes. Applicant tracking products and employer settings differ, and anyone quoting an exact density is guessing.

What actually helps:

• Each important, true skill appears clearly at least once.
• Key skills are shown in context in your experience.
• The text reads naturally to a person.

Chasing a density figure tends to produce awkward, repetitive writing, which recruiters dislike. Concentrate on clear coverage of the requirements you meet, not on how often a word appears.

For human readers, yes: recruiters often decide whether to keep reading from the first part of the page. Whether software weights terms by position varies and is not publicly documented, so do not rely on it.

That is still a good reason to put your strongest, most relevant terms early:

• A headline with the target title.
• A summary naming your key qualifications or tools.
• Your most relevant role first, with keyword-rich bullets.

Example top lines: "Registered Nurse | ICU | BLS and ACLS certified" followed by a summary describing your critical care experience. A recruiter sees the match within seconds.

Keyword stuffing means cramming a resume with job-posting terms to try to beat the software, whether or not they describe your experience. It often looks like long lists of repeated words, phrases copied from the posting, or hidden text.

Common forms:

• A "Keywords" block listing dozens of terms.
• The same skill repeated in every bullet.
• Pasting the job description into the resume, sometimes in white or tiny text.
• Listing tools you have never used.

Why it backfires:

• Recruiters usually read the resume themselves, and stuffed text is easy to spot.
• Hidden text can show up when a resume is copied, parsed or viewed in a different format, which can end your application and damage trust.
• In interviews, you will be asked about the skills you listed.

The honest alternative works better: use the employer's terms for work you have actually done, once or twice each, inside clear sentences. That gives the software the words it needs and gives the recruiter a reason to call you.

Yes, if you label it honestly. Show the level you have reached and how you are learning it, so the employer knows exactly what to expect.

Honest ways to include it:

• In Skills: "Python (basic, completing online course)"
• In Training: "Introduction to Python, [Course Provider], in progress, expected March 2027"
• In Projects: "Wrote a Python script to clean survey data for a university project."

Do not list it alongside your expert skills with no qualifier. If a recruiter assumes you are fluent and you are not, it will come out at interview and undermine your other claims.

Only if you can describe what you did with it, and with a qualifier that reflects your real level. Brief exposure is different from working knowledge, and recruiters often probe listed tools in interviews.

Options:

• Leave it out if it is not important to the job.
• Mention it in context: "Used Tableau to build a one-off sales dashboard for a quarterly review."
• Use an honest level in your skills list: "Tableau (basic)".

A good test: could you answer three practical questions about it in an interview? If not, leave it off or label it clearly.

No. Adding skills you do not have is dishonest, and it usually fails anyway. Even if your resume gets through the software, a recruiter or interviewer will ask about those skills, and a background check, test or reference may expose the gap. It can also cost you the job later if discovered after hiring.

Better options:

• Show related experience honestly: "Used Excel pivot tables for reporting; currently learning Power BI."
• Highlight the requirements you do meet very clearly.
• Apply anyway if you meet most of the requirements; many postings list more than they strictly need.
• Build the missing skill through a course or project, then add it truthfully.

Often, yes, if you meet most of the other requirements. Job postings frequently describe an ideal candidate, and employers may consider applicants who are close. Be honest about the gap rather than hiding it with a false keyword.

What to do:

• Make every requirement you do meet easy to find.
• Show the closest related experience. Example: posting asks for "Oracle"; you write "ERP reporting in SAP, including purchase-to-pay and month-end close."
• Mention any training you have started.
• Use the cover letter to address the gap briefly and positively.

If the missing item is a legal licence or a hard requirement stated as essential, check the posting carefully before applying.

Copying short terms is fine; copying whole sentences is not. Using the employer's name for a skill or tool, such as "accounts payable" or "stakeholder reporting", helps your resume match. Pasting their full sentences into your bullets makes it look generic and can suggest you have not described your own work.

Example:

• Posting: "Responsible for preparing weekly sales reports for senior management."
• Copied: "Responsible for preparing weekly sales reports for senior management."
• Your own words with their terms: "Prepared weekly sales reports for the regional director, highlighting slow-moving stock across eight branches."

The second version uses the key term and adds your real detail.

No. Pasting a job description into your resume, visibly or in hidden text, is a well-known trick and recruiters treat it as dishonest. It may also display when the resume is parsed, previewed or printed, making it obvious.

It does not help in the way people hope either. A recruiter who sees the employer's own text in your resume will doubt everything else in it.

Instead, compare the posting with your resume, find the terms that describe your real experience, and use them in your own sentences. A comparison tool can show which of the posting's frequent terms already appear in your resume, so you can see what you may have described differently.

Yes, usually quickly. Stuffed resumes have tell-tale signs: long lists of terms with no context, the same word in every bullet, unnatural sentences, and skills that do not fit the person's job history.

What recruiters tend to think:

• The candidate is trying to trick the system.
• The listed skills may not be real.
• The resume is hard to read, so the useful parts get lost.

A clean resume that uses the right terms once or twice, with clear results, makes a better impression. Remember that a person usually reads the resume and decides who to interview, whatever software is used.

No. A separate list labelled "Keywords" looks like an attempt to game the system, and it tells the recruiter nothing about what you actually did. Some people add it with dozens of terms copied from the posting, which is a form of stuffing.

Put the same effort into a proper Skills section and strong experience bullets instead.

Example of a useful Skills section:
"Skills: Accounts payable, Bank reconciliation, VAT returns, SAP FI, Excel (pivot tables, VLOOKUP)"

This list is short, specific and backed up by your experience, which is exactly what a keywords block is not.

You should not. Hiding keywords anywhere, whether in document properties, invisible text or tiny fonts, is a form of stuffing. There is no reliable evidence that it helps, and if it is noticed it can make you look dishonest.

Document properties are mainly used by file managers and search tools, not for judging your experience. A recruiter judges what is in the visible text.

What you can do is make sure the PDF title property, if your tool sets one, is simply your name and "Resume". Keep all the content that matters, including your real keywords, in the visible text of the document.

It might help in systems that show a match level, but nobody outside the vendors knows exactly how each product ranks applicants, and employers configure them differently. Many recruiters also review applications without relying on a ranking at all.

What you can control:

• Clearly showing the requirements you genuinely meet.
• Using the employer's terms for your real experience.
• Keeping the resume easy for software to read, with simple formatting.

Even if more matches did raise a ranking, a person still decides who gets an interview. A resume that matches honestly and reads well serves you at both stages.

Write for the person first, then check that the important terms are present. A resume that reads well and uses the employer's language serves both the software and the recruiter.

A practical routine:

• Write each bullet in plain, active language about what you did and achieved.
• Compare your draft with the posting and list any key terms you have but did not use.
• Swap in those terms where they describe the same thing.
• Read the result aloud and remove anything awkward.

Example edit: "Looked after the team's suppliers" becomes "Managed supplier relationships for the kitchen team, ordering produce from six vendors." Same truth, clearer language, and the employer's term included.

It shows which of the job description's most frequent terms appear in your resume, so you can spot important words you may have left out or described differently. It is free to use in the builder.

How to use it well:

• Paste in the full job posting.
• Look at which frequent terms are missing.
• For each one, ask: have I actually done this? If yes, use the term in a bullet or your skills. If no, leave it out.
• Ignore frequent words that are not skills, such as the company name or general words.

The comparison is a guide, not an official score. It does not tell you how any employer's system will rank you, and a full match is not the goal. The goal is to make sure your real, relevant experience is described in the employer's language.