RECREWD FIELD GUIDE · 8 MIN READ
A practical skills-gap analysis for your next role
Compare a target role with your current evidence and turn genuine gaps into a focused learning plan.
- For
- Professionals planning a move or career change
- Published
- Updated
SHORT ANSWER
The practical answer
A skills-gap analysis compares the work a target role requires with evidence you can already show. Classify each requirement as demonstrated, adjacent, learning or intentionally out of scope. Then prioritise only gaps that are important, recurring and realistically learnable.
Define the target with more than one posting
One job description may reflect an unusual team. Review several current descriptions for the same role family and use a recognised occupation framework such as O*NET or ESCO as a cross-check. Record the market and date because requirements change.
Separate core work outcomes from fashionable tool names. A transferable capability may remain relevant even when the named tool differs.
Score the evidence
Use four labels rather than a false percentage.
- Demonstrated: you can show recent, relevant work and explain your contribution.
- Adjacent: you solved a similar problem in another context.
- Learning: the requirement matters and you lack sufficient evidence today.
- Out of scope: the requirement is not important for the direction you chose.
Worked example
Suppose a product-operations role repeatedly asks for process mapping, SQL, executive reporting and change management. You may have demonstrated process mapping and reporting, adjacent spreadsheet analysis, and no SQL project. The useful plan is not “become 80% qualified.” It is to validate whether SQL is genuinely used in the roles you want, then build a small project using realistic but non-confidential data.
The output should name the evidence you will create, a review date and the person or test that can assess it.
Prioritise the next action
Rank a gap higher when it appears across credible sources, materially affects the job’s outcomes, and can be demonstrated in a reasonable time. Rank it lower when it is a rare preference or would pull you away from the chosen role.
- Choose at most two learning priorities for the next cycle.
- Define an observable output for each priority.
- Schedule practice and external feedback.
- Update your profile only after the evidence exists.
- Revisit the target role if the highest-priority gaps do not fit your goals.
PUT IT INTO PRACTICE
Worked worksheet: product operations
This fictional example turns a broad career ambition into two testable next actions. Its requirements are scenario inputs, not a survey of current vacancies. Replace them with dated evidence from your own target roles.
Target and constraints
Target: product-operations specialist at a software company. The candidate wants process improvement and reporting work, with time to learn SQL.
Research to complete: record three relevant vacancy URLs, their dates and the exact outcomes they repeat. Do not treat this example as that research.
Process mapping — demonstrated
Requirement: diagnose an onboarding bottleneck.
Evidence: a process map and action log from a previous internal onboarding project; the candidate owned interviews and documentation, while the team chose the changes.
Next action: prepare a redacted one-page walkthrough and ask a former collaborator to check the contribution statement.
Executive reporting — adjacent
Requirement: explain operational trends to senior stakeholders.
Evidence: weekly team-level spreadsheet reports. No board or executive presentation experience is claimed.
Next action: turn a synthetic dataset into a one-page decision brief. Ask a reviewer which decision the brief supports and what it leaves unclear.
SQL — learning, priority one
Requirement to validate: query operational data independently. Current evidence: spreadsheet analysis only.
Output: use synthetic customer and onboarding-event tables to calculate completion rates, identify missing records and explain a join that could duplicate customers.
Review after two weeks: a technical peer checks the queries against manually computed examples. Keep the label “learning” until the work can be explained and reproduced.
Change management — adjacent, priority two
Evidence: helped roll out a revised checklist; did not own adoption strategy.
Output: a stakeholder map, rollout plan and feedback loop for a fictional process change.
Review after three weeks: a peer challenges the assumptions and asks how resistance or low adoption would change the plan.
Decision after the review
Apply where the demonstrated and adjacent evidence fits the core outcomes; explain the SQL learning boundary honestly.
If SQL is essential from day one and the project is not yet defensible, change the target or continue practice. Do not convert four labels into a probability of getting hired.
Make your own working copy
Download the plain-text template or open it below to copy into your preferred notes editor. Your working copy stays with you.
Download blank template (.txt)View and copy the blank template
Recrewd — Worked worksheet: product operations Blank working template Use your own facts. Leave unknowns explicit. Do not include private or confidential material. Target role, market and work arrangement: [Complete here] Research date and vacancy/source URLs: [Complete here] Requirement and outcome it supports: [Complete here] Evidence label: demonstrated / adjacent / learning / out of scope: [Complete here] Your example, contribution and source: [Complete here] Gap or uncertainty to verify: [Complete here] Priority and reason: [Complete here] Observable output to create: [Complete here] Practice time and review date: [Complete here] Reviewer or acceptance check: [Complete here] Result, remaining gap and next decision: [Complete here]
Put this into practice
Bring your target role and current evidence to Rec for questions and a learning-plan draft you can assess.
Sources and scope
This guide provides general educational information. It does not promise that a particular search, CV, introduction or hiring method will produce an interview or hire.