How to choose a job-ready course when there are ninety of them

A catalogue of ninety-odd role-based courses is useful right up to the moment you have to pick one. Job titles are a bad filter: they are invented by whoever wrote the advert, they mean different things at different companies, and the interesting part of a role is rarely visible in its name.

Start with the Tuesday test

For any role you are considering, ask what a person in it does on an ordinary Tuesday. Not the best day, not the interview answer. A support technician spends it working a queue of other people's problems. A data analyst spends most of it cleaning data, not presenting findings. A QA tester spends it writing down precisely what broke, in enough detail that somebody else can reproduce it.

If the ordinary Tuesday sounds tolerable, the role is a candidate. If it sounds like the part you would be enduring to get to the good bit, it is worth looking at what the good bit actually occupies: usually less of the week than people imagine.

Where most people here start

Support and service roles are the most common starting point on CertClue, and that matches how people get into technology generally. Support is the entry point that does not require you to already have the job in order to get the job: it hires for aptitude and attitude more than for a portfolio, and it puts you next to every system in the company, which is the fastest education available.

Three questions that narrow it quickly

1. Do you want to work with people, systems or numbers? Support and onboarding are people. Infrastructure and security are systems. Analysis, finance and operations are numbers. Most bad course choices ignore this and pick on salary.
2. What would you have to show at interview? Look at the projects the course produces and ask whether they would survive being read by somebody who does the job.
3. What is the next rung? A course that leads somewhere (support to systems administration, analysis to engineering) beats a dead-end with a better title.

Check the shape before you commit

A course worth your evenings should have four things: material that teaches the work rather than a syllabus, checks that make you retrieve rather than recognise, a simulated week where you make decisions and get told why they were wrong, and projects that produce an artifact you keep. If any of those is missing, you are reading rather than practising.

On CertClue that is the standard structure, and the courses finish on the website where the projects are submitted and the completion certificate is issued. It is free, which mostly matters because it means you can start one, discover in week two that the Tuesday sounds wrong, and switch without having bought anything.

Switching is not failure

Two weeks into a course is the cheapest possible moment to discover a role is not for you, and it is a better outcome than finding out in month three of the job. The information you gain is real: you now know something concrete about what you do not want, which is most of how people find what they do.

What is worth avoiding is the loop of starting five courses and finishing none. Give a course a fixed trial, a fortnight is plenty, then decide deliberately rather than drifting.