TD
Key Takeaways
- "Missing" means the scan could not find evidence of the skill in your resume — not that you lack it.
- First question, always: do you actually have this skill? Be honest, then act on the honest answer.
- If you have it, the fix is naming it inside evidence, not adding it as a bare list item.
- If you genuinely lack it, three honest options exist — none of them is inventing the skill.
- Hard skills are more heavily weighted than soft skills in most matching, so this list deserves real attention.
A scan flags "missing hard skills" and hands you a list — Python, stakeholder reporting, Salesforce, whatever the posting named. Before doing anything with that list, answer one question for each item: do you actually have this?
Start Here: The Honest Split
Take the missing list and sort every item into one of two piles.
Pile 1 — I have done this. You have used the tool, performed the task, held the responsibility — your resume just does not say so clearly.
Pile 2 — I have not done this. Genuinely absent from your experience.
Everything below depends on which pile an item is in. Do not skip this step or rush it — the fix is completely different for each pile, and conflating them is how resumes end up either under-selling real experience or over-claiming absent experience.
Pile 1: You Have It, You Just Didn't Say So
This is usually the larger pile, and the good news is that it is fixable in minutes, honestly.
The mistake that causes this: people describe their work in their own words rather than the posting's words, and a system matching on specific terms cannot connect "built the process that pulled data from Salesforce nightly" to a posting asking for "ETL pipeline experience" unless the language overlaps somewhere.
The fix: find the bullet that already describes the work, and add the missing term into it directly.
Before: Built the nightly process that pulled data from Salesforce into our warehouse. After: Built and maintained the ETL pipeline moving Salesforce data into our warehouse nightly.
Nothing was invented. The claim is identical. It is now matchable, both to a parser and to a human scanning for that exact phrase.
Do this for every item in Pile 1. It is the highest-return activity available when a scan comes back with gaps, and it typically accounts for most of the achievable improvement. See which missing skills actually matter for prioritising when the list is long.
Pile 2: You Genuinely Lack It
This is the harder pile, and the wrong move is adding the word anyway. It works at the filter and fails at the interview — a worse outcome than the rejection you were trying to avoid. See improving your score without lying.
Three honest responses, depending on the specifics:
Option A — State genuine adjacent experience. If the posting wants Snowflake and you have deep BigQuery experience, say exactly that:
Data warehousing experience with BigQuery; comfortable learning adjacent platforms.
This is honest, it shows real relevant capability, and a reasonable hiring manager can evaluate the transfer themselves. What you should not write is "Snowflake" — that is a specific, checkable claim you cannot back up.
Option B — Acknowledge the role may not be the right fit yet. If the gap is substantial — years of experience, a required licence, a fundamentally different technical stack — the honest conclusion is that this specific posting is a stretch. That is useful information, not a failure. See required vs preferred qualifications to check whether the gap is actually a hard requirement or a wish-list item you can reasonably ignore.
Option C — Close the gap for real, if time allows. If you keep seeing the same missing skill across postings and you have weeks rather than hours, that is a genuine signal about what to learn next. A short course or a side project gives you something true to write, rather than something invented.
A Worked Example
Scan result on a marketing analyst posting: missing SQL, A/B testing, Looker, budget management, cross-functional collaboration.
Honest audit:
- SQL — you write queries weekly but your resume just says "data analysis." Pile 1. Fix: name SQL in the bullet describing that work.
- A/B testing — you have run three experiments this year. Pile 1. Fix: name it in the relevant bullet with a result if you have one.
- Looker — you have never used it, though you have used Tableau extensively. Pile 2, Option A. State Tableau explicitly and let the transfer speak for itself.
- Budget management — you have never owned a budget. Pile 2, Option B. A real gap; if it is stated as required rather than preferred, this posting may not be the best use of your time tonight.
- Cross-functional collaboration — a soft skill dressed as a hard one. Low priority regardless of which pile — see soft skills nobody can verify.
Out of five missing items, two are quick honest fixes, one is a reasonable adjacent-experience statement, one is a real gap worth noting, and one barely matters. That is a five-minute plan instead of a vague sense of being underqualified.
Why Hard Skills Get Weighted Heavily
Hard skills are specific, checkable and directly tied to whether you can do the work — a named tool, a certification, a technical method. That specificity is exactly why matching systems and human screeners both lean on them more than soft skills, which everyone claims and nobody can verify from a resume alone.
This means the effort you spend on Pile 1 for hard skills produces more return than almost anything else you could do to a resume in the same amount of time.
What Not to Do
Do not add a tool from a single tutorial and call it a skill. There is a real difference between having used something and having watched a video about it — an interview will find that difference quickly.
Do not pad the skills list with things unrelated to the posting, hoping something sticks. It dilutes the items that actually matter — see keyword stuffing.
Do not ignore Pile 1 because Pile 2 feels discouraging. The fixable items are usually the majority of the list, and fixing them is worth doing regardless of what else is missing.
Frequently Asked Questions
What if I'm not sure which pile something belongs in? Ask whether you could discuss it for two minutes under questioning. If yes, Pile 1. If you would be improvising, it is Pile 2.
Should I list a skill I used briefly years ago? Yes, honestly labelled with context — "prior experience with X" reads differently from implying current daily use.
Is it ever okay to list a skill I'm currently learning? State it accurately: "currently studying X" or "X (in progress)." Do not present it as an established skill.
How many Pile 2 items are too many to apply anyway? No fixed number — check whether they are required or preferred. Several missing preferred items is normal; one missing required item is a real signal.
Does fixing Pile 1 guarantee an interview? No, but it removes an avoidable failure. Everything after that — competition, level fit, timing — is a separate question.
Sort Your Own List
The plan above only works once you can see exactly what a specific posting says you are missing.
Scan your resume against the posting and go through the missing list item by item, honestly. Most people find the majority sits in Pile 1 — which means most of the fix is a wording change, not a skills gap.
Free, about a minute. See also which missing skills actually matter and how to match resume keywords to a job description.
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.
