Job-ready skill paths
Most "learn to code" or "learn finance" material is organised around a syllabus rather than around getting hired. These paths are organised the other way round: each one starts from a job that exists, works backwards to the skills that job screens for, and ends in something you can put in front of an employer.
They are honest about time. A career change is three to six months of consistent part-time work, not a weekend, and no path here pretends otherwise. They are also honest about certificates: in every field below, employers weight demonstrated work far more heavily than course completion, so each stage ends in an artefact rather than a badge.
Choose your goal
Or start from the job title
The paths above are organised by subject. If you already know the job you want, start from the role instead — each page below covers the realistic ways in, what to learn in what order, what the role actually pays measured from live postings, which employers are hiring it now, and what gets people rejected.
- ›How to become a accountant
- ›How to become a android developer
- ›How to become a backend developer
- ›How to become a business analyst
- ›How to become a cloud engineer
- ›How to become a content writer
- ›How to become a customer success manager
- ›How to become a customer support
- ›How to become a cybersecurity analyst
- ›How to become a data analyst
- ›How to become a data engineer
- ›How to become a data scientist
- ›How to become a database administrator
- ›How to become a devops engineer
- ›How to become a digital marketing manager
- ›How to become a executive assistant
- ›How to become a financial analyst
- ›How to become a frontend developer
- ›How to become a full stack developer
- ›How to become a graphic designer
- ›How to become an hr manager
- ›How to become an hr recruiter
- ›How to become a ios developer
- ›How to become a machine learning engineer
- ›How to become a marketing manager
- ›How to become a network engineer
- ›How to become a operations manager
- ›How to become a procurement
- ›How to become a product designer
- ›How to become a product manager
- ›How to become a project manager
- ›How to become a qa engineer
- ›How to become a relationship manager
- ›How to become a sales representative
- ›How to become a scrum master
- ›How to become a site reliability engineer
- ›How to become a social media manager
- ›How to become a software engineer
- ›How to become a solutions architect
- ›How to become a supply chain analyst
- ›How to become a systems analyst
- ›How to become a technical writer
- ›How to become a ui/ux designer
How to actually finish one
The failure mode is not difficulty, it is drift. People restart the first stage repeatedly because starting feels productive and finishing feels exposed. Set a fixed weekly slot, work in the order given, and treat each stage's artefact as the gate to the next one rather than something to come back to later.
Start applying before you feel ready, roughly two-thirds of the way through. Interviews are the fastest diagnostic available for what you are still missing, and waiting until you feel fully prepared usually means waiting several months longer than necessary.
Still at school?
These paths assume you are preparing to enter the workforce rather than starting from scratch. If you are earlier than that, begin with the coding lessons, which start at variables and build up, or English for work if the language is the bottleneck rather than the subject.
Common questions
Are these courses free?
Yes. The learning paths, the practice tools and the interview question bank are all free and need no account. Where a path points at outside material we say so plainly.
Do I get a certificate?
No, and we would be cautious about paying for one. Employers in these fields hire on demonstrated ability — a repository, a model you built, an analysis you can walk through — far more than on course certificates.
How long does a path take?
Realistically three to six months of consistent part-time study for a career change, less if you are building on an existing degree. The stage estimates are deliberately honest rather than motivational.
What if I'm still at school?
Start with the foundations on our sister site Syllab, which covers school-level coding and computer basics, then come back to these paths when you are preparing to apply for work.
Then put it to work: resume tools · interview prep · job search tools
What divides a deep resource from marketing
Free material ranges from genuine to thin. The distinction is not always obvious, especially for beginners who cannot yet judge the subject. A practical filter: does the course make you do something, or does it show you something? Showing a concept, no matter how clearly, builds recognition. Doing — solving problems with incomplete guidance, building something from partial specification, explaining your work — builds recall and transferable skill. The best resources force struggle. A tutorial that feels effortless is teaching visibility, not mastery.
Watch for two red flags. First, outcome inflation: a course that claims you will build an end-to-end application but shows you clicking buttons in a pre-built scaffolding has not taught you to build. You have learned to follow, which is not the same thing. Second, scope sprawl: material that touches fifty topics at surface depth looks comprehensive until you interview and discover you have depth nowhere. A course that teaches five things thoroughly beats one that touches fifty.
The strongest resources often have constraints. A language course designed specifically for workplace communication, a statistics text written for analysts rather than mathematicians, a guide to hiring in a specific role — these are narrower, but they are deeper within the boundary. Generalist material that tries to serve everyone ends up serving no one well, because it cannot make the choices about what to omit.
Why the path you pick is less important than finishing it
Each of the five paths below leads to employable work within three to six months of consistent effort. The time varies depending on your starting point and the time you can sustain weekly, but the order does not. Data analysts always learn SQL before Python; software developers always practice coding before algorithms; accountants always consolidate double entry before tackling tax. But people often restart paths rather than finishing them, because starting is psychologically easier than shipping.
The mechanism is familiar. The first stage feels productive — you are learning new concepts, following tutorials, making visible progress. By the third or fourth stage, progress feels slower. You are refining one project instead of starting fresh. You are fixing bugs instead of learning. You are explaining your work to people instead of discovering new techniques. These are the stages that actually teach judgment, but they do not feel like learning because they are not visibly adding knowledge. The people who restart early have not learned that productiveness and progress are different. Productivity is motion; progress is change in a direction you chose.
Set a weekly slot you can keep. Two hours weekly is far more effective than ten hours once a month, because skill compounds from repetition. Treat each stage's artefact as a lock on the next one — you do not move forward until the thing you built in stage two works, because moving forward anyway leaves an unfilled gap in your foundation. Apply to jobs before you feel ready. Interviews are the fastest feedback available for what you are still missing, and people who wait until they feel prepared usually wait three months longer than necessary.
The gap between coursework and the interview room
Course content is organized by topic: SQL joins, then aggregation, then window functions. Interviews are organized by judgment: here is a situation, what do you do? The course teaches the building blocks; the interview tests whether you can see which blocks to use without instruction. This gap exists in every field, and it is the reason generic completeness is not enough. You can finish a course without being interview-ready.
The second gap is format. A course gives you the same problem twice and you solve it; an interview gives you a problem once and you must think out loud. The course lets you look up syntax; interviews test whether you know it. The course lets you refine your answer; interviews test your first thought. These are not harder versions of the same skill — they are different skills entirely. An analyst who can write perfect SQL in their own time but freezes on a whiteboard has learned the syntax but not the performance under pressure.
The third gap is context. A course teaches skills in isolation. A real job requires judgment about priority: this data request matters because of what a manager needs to decide. The candidate who produces the most technically sophisticated analysis but misses the business point does not get hired. Each path below includes this step explicitly, because it is worth separate practice. Learn the skill first, then practice applying it in context that has a real human decision behind it.
Frequently asked questions
How do I know which path to start with if I am interested in multiple fields?
Start with the field that compounds fastest toward income. If you want to be both a developer and an analyst, start as a developer — the higher salary lets you fund a later transition. If torn between two at similar pay, start with the one you have evidence you can sustain: which subjects did you engage deeply with at school? Which problems do you voluntarily spend time solving? Starting is easier when the topic already holds your attention.
Can I learn multiple paths at once?
Not effectively. Skill building requires sustained weekly focus. Two half-hours weekly on two paths is worse than four hours on one, because you lose context-switching time and each path hits diminishing returns before it hits depth. Finish one path, use it to earn and build confidence, then add the second path as a specialization or pivot.
What happens if I get stuck on a particular stage?
Stalling usually means one of three things: the resource is a bad fit for how you learn, you are leaning on tutorials instead of building independently, or you are trying to be perfect before moving forward. If a resource is not working after two weeks, switch it. If you are watching tutorials, close the video and build from a blank file. If you are held up perfecting stage one, move to stage two and come back — the next stage will teach you what stage one assumed.
How much of a path should I complete before applying for jobs?
Apply when you have two-thirds of the way through, even if it feels early. Interviews provide real feedback for what you are missing far faster than you will discover it alone. A company applying to five places 70% ready beats applying to fifty places 99% ready, because the five get feedback cycles while you are studying the remaining 30%.
Do I need stable internet or a powerful computer to do these paths?
A working laptop and a consistent connection are the baseline. You do not need latest hardware. Most of the work runs locally or on free tiers. The constraint is time and focus, not equipment. If your internet drops frequently, download resources when you can and practice offline work (code editing, problem-solving) during drops.