Missing a Skill the Job Asks For? What to Do on Your Resume
The job wants a skill your resume doesn't show. How to find out if you really have it, how to show it honestly, and what to do if you don't, without inventing anything.
You find a job that fits you well, except for one line: "experience with Tableau", "A/B testing", "stakeholder management". Your resume doesn't mention it. Should you apply? And what should you put on your resume?
First: should you still apply?
Usually, yes. Job ads are wish lists. Hiring managers rarely expect every candidate to tick every box, especially for the "nice to have" items. A reasonable rule: if you meet most of the essential requirements and can show you'd pick up the rest quickly, apply.
Be more careful with hard requirements: a licence, a degree a regulator requires, a security clearance, or a language you'll use every day. Those usually can't be learned on the job.
Step 1: check whether you really have it
Often the skill is there; your resume just doesn't say so in the job's words. Ask yourself:
- Have I done this under another name? "Ran experiments on our pricing page" is A/B testing. "Kept the regional heads updated every week" is stakeholder management.
- Did I use it in a project, a course or volunteer work? It still counts, if you say where.
- Have I used a similar tool? Power BI and Tableau, Jira and Asana, AWS and Azure share most of their concepts.
Step 2: if you have it, show it with evidence
Don't just add it to your skills list. A keyword with no proof is easy to spot. Add it to a bullet point that shows you doing it, using the job's own term:
- Before: "Worked on the checkout page."
- After: "Ran 6 A/B tests on the checkout page, raising completed orders by 4%."
Only use numbers that are true. If you don't remember the exact figure, leave a placeholder like [X]% and look it up before you send the resume. RURU marks every unfilled [blank] and reminds you before you download, so none slips through.
Step 3: if you have something close, show the bridge
When you lack the exact skill but have the closest thing, show that honestly:
- In your skills section: list what you have ("Power BI"), not what you don't ("Tableau").
- In your cover letter: one line is enough. "My dashboard work is in Power BI, and I'm keen to build on it with Tableau."
- In the interview: explain how what you know transfers, and how you'd close the gap.
Step 4: if you don't have it, don't add it
It's tempting to add the missing keyword "for the ATS". Don't. It is the first thing an interviewer may ask about, and a skill you can't discuss costs you the job and your credibility. Instead:
- Start learning it now, and say so: a course in progress is real and you can name it.
- Do a small project with it. A weekend project you can show is stronger than a line on a resume.
- Lean on your other strengths. Make the rest of your resume so clearly matched to the job that one gap doesn't matter.
How AI tools should help, and how they shouldn't
A good AI resume tool should help you find the skills you already have and say them in the job's words. It should never write experience you don't have. When RURU's Tailor suggests a new bullet for a missing requirement, it leaves [blanks] for every specific and marks it "add only if this is true". You decide what goes on your resume.
The short version
- Apply if you meet most essential requirements; job ads are wish lists.
- Look for the skill under another name in your own experience.
- Prove it in a bullet point with a result, using the job's words.
- If you don't have it, say what's closest and that you're learning, and never invent it.
Read next: how to tailor your resume to a job description.