SS
Key Takeaways
- A list of 12 missing skills is not 12 tasks. Usually two or three matter and the rest are noise.
- Rank by two axes: is it required or preferred, and do you have it or not.
- The highest-value pile is "required, and I have it but did not write it" — fix that first, always.
- Soft skills in a missing list are almost always safe to ignore.
- Never add a skill from the missing list that you cannot discuss for two minutes.
You ran a scan, and it returned a list of missing skills longer than you expected. The instinct is either to add all of them or to conclude you are unqualified. Both are wrong. Here is how to triage.
The Two-Axis Sort
Every missing item falls into one of four boxes. Take your list and place each one.
Axis 1: Does the posting require it or prefer it? Find the term in the original posting and read the surrounding language. "Must have", "required", "minimum X years" and named credentials are requirements. "Nice to have", "a plus", "familiarity with", "exposure to" are preferences.
Axis 2: Do you actually have it? Be honest. Have you used this tool in real work, or only read about it?
That gives you:
| You have it | You don't | |
|---|---|---|
| Required | 🔴 Fix now — highest value | ⚫ Probably skip the role |
| Preferred | 🟡 Add if quick | ⚪ Ignore |
🔴 Required + You Have It — Fix These First
This is the pile that changes outcomes, and it is usually bigger than people expect.
These are things you genuinely do, described in your resume using different words. The posting says "stakeholder management"; your resume says "worked with department heads." The posting says "ETL pipelines"; your resume says "moved data from Salesforce into the warehouse nightly."
You are not missing the skill. You are missing the phrase.
How to fix: put the posting's term into the bullet that already describes the work. Do not create a new bullet claiming the skill abstractly — attach the language to the evidence:
Before: Built the nightly process that moved Salesforce data into Redshift. After: Built and maintained nightly ETL pipelines moving Salesforce data into Redshift.
Same claim, same truth, now matchable. This is what keyword matching actually means — not stuffing, but naming.
⚫ Required + You Don't Have It — Read the Role Again
If a genuine requirement is genuinely absent, adding the word does not help. It gets you past the filter into an interview you will lose, which costs you more time than the rejection would have.
Two exceptions worth considering:
Adjacent experience. You do not know Snowflake but you have three years of BigQuery. That is worth stating honestly — "data warehousing (BigQuery; comparable platforms)" — because a hiring manager can evaluate the transfer. Do not write "Snowflake."
Requirements that are softer than they look. "5+ years" often means "we want someone senior." If you have four years with unusually relevant depth, apply. A named licence, on the other hand, is rarely negotiable.
If most of your missing-required list is genuinely absent across many postings, the useful conclusion is about role selection, not resume writing.
🟡 Preferred + You Have It — Add If It's Quick
Worth doing, low urgency. Add it to the skills section, reorder so it is visible, move on. Do not restructure the resume for a preferred item.
The exception: if you have several of these, adding them together can meaningfully lift a borderline score. Five minutes well spent.
⚪ Preferred + You Don't Have It — Ignore Completely
This is the pile people waste the most time on, because it is the longest.
Postings accumulate wish-list items from multiple stakeholders. Nobody expects one candidate to have all of them. Missing four preferred skills is normal and is not why you were rejected.
Leave them. Do not learn a tool over a weekend to add a line. Do not apologise for them in a cover letter.
The Special Case: Soft Skills
If your missing list contains "communication", "teamwork", "problem-solving", "attention to detail" or "leadership" — these are almost always safe to ignore.
Two reasons. First, everyone claims them, so they differentiate nothing. Second, stating them does not evidence them: "excellent communicator" is a claim, while "presented monthly forecasts to a 40-person sales org" is proof. A human reads the second and infers the first.
The exception is when a posting names a soft skill as a stated requirement in a role where it is genuinely central — client-facing roles, people management. Even then, evidence it in a bullet rather than listing the phrase. See soft skills nobody can verify for the longer argument.
A Worked Example
A scan returns 12 missing items on a data analyst posting:
SQL · Tableau · stakeholder management · Python · dbt · A/B testing · communication · retail experience · Looker · attention to detail · Snowflake · cross-functional collaboration
Sorted:
- 🔴 Required + have it: SQL (in a project bullet, not the skills section), stakeholder management (described as "worked with department heads"), retail experience (your last job was retail — never stated as industry)
- ⚫ Required + lack it: dbt
- 🟡 Preferred + have it: Tableau, A/B testing
- ⚪ Ignore: Python, Looker, Snowflake (preferred, lack), communication, attention to detail, cross-functional collaboration (soft)
So: three edits that matter, two quick additions, one real gap, six items to ignore. Twenty minutes of work, not an afternoon — and the list went from intimidating to specific.
What Order to Fix In
- Required + have it — put the posting's term into the bullet that already proves it.
- Summary rewrite — name the target role and the two or three central requirements.
- Skills section reorder — required items first.
- Preferred + have it — add to skills.
- Re-scan — confirm the specific items cleared, not just that the number moved. See what to expect when you re-scan.
Frequently Asked Questions
Should I add every missing keyword? No. Most of them do not matter, and adding ones you lack creates interview risk.
How do I know if something is required or preferred? Find it in the original posting and read the surrounding sentence. The language is usually explicit.
What if I have the skill but only from a course? Say so accurately — coursework or certification, not work experience. Do not let a course become an implied job.
What about skills from five years ago? List them, but recency matters to human readers. Foreground current tools; keep older ones lower.
Does adding keywords guarantee a higher score? Adding them where you have evidence usually helps. Adding them abstractly moves the number less and reads worse.
Get Your Sorted List
The triage above only works once you can see which items the posting actually asked for.
Scan your resume against the posting, then take the missing list and run it through the two-axis sort. Most people find two or three items in the red box — and those two or three are the entire job.
Free, about a minute. See also what is a good ATS match score and improve your score without lying.
What is your resume scoring right now?
Scan it against a job description and get your ATS match score in about a minute.
Drop your resume here or choose a file
PDF only. Max 2 MB.
We never share your data or use it to train AI models.
Templates that keep this structure intact
This template is ATS-tested — start from it and the formatting rules in this guide are already handled.
Was this guide useful?
Be the first to rate it.
