Identify skills you need to develop for your next career move. Compare your current skills with target role requirements and find learning resources.
A skills gap is the distance between the skills you have today and the skills your target role expects. The strategic guide here covers how to think about gaps, how to prioritize them, how to build evidence as you close them, and how to know when a gap is actually closed. The tool at /tools/skills-gap runs the actual analysis — comparing your current skills to a target role and ranking gaps by impact. Use both: this page for the framework, the tool for the data. Closing one gap deeply produces interview answers; touching ten gaps superficially produces nothing.
Use cases
Building a focused 90-day learning plan. Pick the top 3 gaps from the analyzer. Sequence them — usually 1 hard skill, 1 tooling skill, 1 process skill. 60–90 days of focused practice with one shipped artifact per gap closes more career distance than a year of scattered course-watching.
Deciding whether a gap is realistic to close. Some gaps are 3-month closes (a new framework). Some are 12+ month closes (a new programming paradigm, a new domain). Be honest about the time cost before committing. Underestimating closes you cannot afford to make is the most common career-change failure mode.
Knowing when a gap is actually closed. When you can ship a small but real project using the skill end-to-end without help, and explain the tradeoffs you made out loud. If you cannot teach it, the gap is not yet closed — you have just been exposed to it.
How it works
Run the analyzer to surface ranked gaps. The tool at /tools/skills-gap compares your current skills to the target role and ranks gaps by frequency in real listings. Use the ranking; do not pick gaps by gut feel.
Pick 3 gaps to focus on for 60–90 days. One hard skill, one tooling skill, one process skill is the typical mix. Above 3 gaps, depth suffers and nothing reaches the threshold of demonstrated knowledge.
Pair each gap with a course + project. Course is the on-ramp; project is the proof. Course gets you to working knowledge in 20–40 hours; project takes you from working to demonstrated. Ship one project per gap.
Build evidence in public. GitHub repo, blog post, public talk, open-source contribution. Visible evidence is what recruiters scan; private evidence does not exist for them. Public artifacts compound search outcomes.
Confirm the gap is closed before moving on. You can teach it = closed. You can use it with help = not closed. Self-grade harshly; the bar is "would a senior person in this role recognize me as competent?", not "do I feel productive?".
Examples
An engineer closing a systems-design gap. 90 days: book + course + 5 paper designs + 1 production-grade side project. Public blog post explaining tradeoffs. Lands senior systems-design interviews at month 4; the visible artifact moved the conversation from "do you know systems design?" to "let's discuss your approach".
A career changer underestimating a domain shift. Initial plan: 90 days from finance to ML engineering. Realistic plan: 12 months. The honest re-estimation early prevents 6 months of disappointment when the original timeline cannot hold.
Frequently asked questions
How is this different from the skills gap tool at /tools/skills-gap?
This page is the strategic guide — how to think about gaps, how to prioritize, how to track progress. The tool runs the actual analysis comparing your current skills against a target role and produces a ranked list of what to learn.
How many skills should I work on at once?
One to three. More than that and depth suffers. Pick the highest-impact gap (the skill that shows up in the most listings for your target role), build it for 60–90 days, then move to the next. Sequential beats parallel.
Should I learn a skill from a course or a project?
Both, in that order. A course gets you to working knowledge in 20–40 hours; a project takes you from working knowledge to demonstrated knowledge. Recruiters care about the project; the course is just the preparation that makes the project possible.
How do I know when a skill gap is closed?
When you can ship a small but real project using the skill end-to-end without help, and explain the tradeoffs you made out loud. If you cannot teach it, the gap is not yet closed — you have just been exposed to it.