A job description may use terminology you do not recognize even when you already have equivalent experience.

Before calling something a "skill gap," classify it correctly.

List the important requirements

Do not analyze every phrase.

Start with:

  • hard constraints;
  • core responsibilities;
  • repeated technical skills;
  • important methods;
  • required tools;
  • major domain knowledge.

Ignore low-value boilerplate until later.

Normalize similar skills

Different employers may use different names for similar work.

Examples:

  • Power BI vs Tableau → both BI/reporting tools, but not identical products;
  • Jira vs another issue tracker → transferable workflow knowledge may exist;
  • demand forecasting vs sales forecasting → overlapping methods, different context;
  • Python vs R → transferable analytical programming, but not the same language.

Do not automatically mark either "match" or "gap."

Ask whether the underlying task transfers.

Check evidence

For each requirement, ask:

Can I point to something I actually did that demonstrates this?

Evidence can come from:

  • professional work;
  • project;
  • coursework;
  • volunteering;
  • freelance work;
  • lab;
  • capstone;
  • open-source contribution.

If you can perform the skill but cannot show any concrete example, that is often an evidence gap.

Classify each requirement

Use four categories.

1. Have it

You have relevant experience and can explain it.

2. Equivalent experience

You used a related tool or method and can explain the transfer.

Example:

Job asks for Looker; you have substantial Power BI dashboard experience.

That is not identical experience, but it may not be a fundamental skill gap.

3. Evidence gap

You know the skill but the resume does not demonstrate it.

4. True gap

You cannot yet perform the work to the level required.

Prioritize by importance

Not every true gap deserves immediate action.

Use:

Impact = importance to role × gap size

A core missing capability deserves attention.

An optional platform preference may not.

Example

Job asks for:

  • SQL;
  • Power BI;
  • stakeholder presentations;
  • Python preferred;
  • retail experience preferred.

Candidate has:

  • SQL at work;
  • Tableau dashboards;
  • monthly management presentations;
  • no Python;
  • no retail experience.

Diagnosis:

  • SQL → have it;
  • Power BI → transferable tool experience;
  • presentations → have it, perhaps poorly evidenced;
  • Python → true but preferred gap;
  • retail → domain gap, also preferred.

That profile may still be credible.

Avoid false gaps

Do not label these as automatically missing:

  • synonym changes;
  • tool-family differences;
  • different industry terminology;
  • responsibilities described at a higher level.

But also do not pretend adjacent experience is identical.

A useful gap analysis reduces unnecessary learning. It tells you what you genuinely need to build.

Related content

Sources