Learning Path Recommender - Free Skill Development Resources
Discover free learning resources for career development. Build skills in programming, data analysis, cloud computing, and more. Plan your career path.
The learning path tool builds a 60–90 day skill plan tied to a target role, with each step producing visible evidence of progress. Most candidates over-invest in courses (low-leverage proof) and under-invest in projects (high-leverage proof). The plan flips that ratio: courses get you to working knowledge; one shipped project per skill takes you from working to demonstrated. Recruiters care about the project. The tool sequences skills (foundations first, then advanced), maps each to a credible learning resource, and adds a portfolio milestone every 30 days so the learning is visible by the time you start applying.
Use cases
Closing skill gaps surfaced by the skills-gap analyzer. Run /tools/skills-gap; pick the top 3 gaps; the learning path tool builds a 60–90 day plan covering each. Output includes specific resources (course, book, project idea) and the sequencing — what to learn first, what builds on what.
Self-directed upskilling between roles. Between jobs is the highest-leverage learning window. Use the time on 2–3 deep skills with shippable projects rather than 10 shallow course completions. The output: a portfolio that visibly shifts what level of role you can target.
Career-change preparation alongside current job. 5–10 hours per week on the path is the sustainable target while working full-time. The plan accounts for that and stretches accordingly — most career-change paths run 6–9 months at that cadence rather than the 60–90 days of full-time learning.
How it works
Pick the target role. Specific role + seniority + industry. Vague targets produce vague paths. The plan derives skills from real listings for the target role, not from generic curricula.
List 3–5 skill gaps in priority order. Prioritize 1 hard skill, 1 tooling skill, 1 process skill. Focus produces depth; depth produces interview answers. Above 5 gaps, the plan dilutes and nothing reaches mastery.
Map each gap to a course + project. Course is the on-ramp; project is the proof. The plan pairs each skill with one credible course (Coursera, Educative, free quality alternatives) and one shippable project (1–2 weeks of focused work).
Schedule 30-day milestones. Day 30: first skill course done + small project shipped. Day 60: second skill done + larger project. Day 90: third skill + capstone project that integrates all three. Public artifacts (GitHub, blog post) at each milestone.
Update your resume + LinkedIn as evidence ships. Resume bullets shift to reflect the new skills as projects complete. LinkedIn posts about each milestone build inbound recruiter interest before the formal search begins.
Examples
A backend engineer learning systems design. 90 days: book + course foundation, designs 5 systems on paper, ships one production-grade design as a side project, writes a public blog post explaining tradeoffs. Resume shifts; landed senior systems-design interviews at month 4.
A career changer building bridge skills toward PM. 6 months at 8 hours per week: PM course, 3 public PRDs, owned one launch end-to-end at current job. Built portfolio visible to recruiters. Lands first PM offer at month 9, two months earlier than expected.
Frequently asked questions
How do I pick what to learn next?
Run /tools/skills-gap against your target role to surface ranked gaps. Pick the top 3 — usually 1 hard skill, 1 tooling skill, 1 process skill. Focus produces depth; depth produces interview answers.
How long should it take to learn a new skill?
60–90 days from "starting" to "shippable demo" for most skills. Longer for foundational shifts (a new language, a new domain). Shorter for tools that build on existing skills (a new framework, a new database).
Should I prefer courses or projects?
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 preparation.
How do I prove I learned the skill?
Ship one visible artifact: a side project, an open-source contribution, a written explainer with code, a public talk. Course-completion certificates rarely move the needle on their own.
Tips
Project beats course for proof. Course-completion certificates rarely move the needle alone.