How do I find out which skills I am missing to switch careers?

Take ten to twenty current job postings for the role you want, list every skill they ask for, count how often each one appears, and mark the ones you can already prove. Whatever appears often and you cannot prove is the gap. That is the whole method, and a tool can do the counting for you.

Most people never do this. They pick a role, feel behind, and start learning whatever course is in front of them. Six months later there is a folder of certificates and still no clear idea whether they are ready, because the gap was never measured, so it never closed.

Why guessing does not work

A career change is a comparison between two lists: what the role asks for, and what you can show. Both lists are fuzzy in your head. The role list is fuzzy because you have never sat inside the job, so you fill it with whatever the loudest advice says. The evidence list is fuzzy because you underrate the work you did in your old field and overrate the things you have only read about.

Guessing tends to fail in the same direction. People learn the fashionable skill that appears in one posting out of twenty and skip the boring one that appears in nineteen. A teacher moving into instructional design spends a month on a video tool and never opens a learning management system. A nurse moving into operations learns a dashboard product and never touches a spreadsheet at the level the job needs.

The manual method, step by step

Set aside an evening. You need a browser and a blank spreadsheet.

Pick one role title, not a field. "Data analyst" is a role. "Something in data" is a field, and fields do not have postings. If you are torn between two roles, do the exercise twice; the overlap between the two lists is itself useful information.

Collect ten to twenty postings. Use the boards where the role is advertised, and take postings from the last month, because requirements drift. Mix company sizes. Skip the ones that are clearly copied from a template, and skip the ones asking for ten years of experience if you are aiming at entry level.

Pull out every skill, in the posting's own words. Tools, methods, and the softer things too: "presents findings to non-technical stakeholders" is a skill and it will appear again. Keep the wording close to the original, because the wording is what a hiring manager searches for and what you will need to echo on your CV.

Count. One row per skill, one tick per posting that mentions it. Sort by ticks. The top of the list is the core of the role. The bottom is noise, and it is surprising how much of what you assumed was essential turns out to be noise.

Mark your evidence. Next to each skill, write what a stranger could look at that proves you have it. A project, a repository, work from your last job, a certificate with a practical exam behind it. If the honest answer is "I watched a course on it," leave the cell empty. That empty cell is the point of the exercise.

Read the two columns together. Where the count is high and the evidence cell is empty, that is your gap, and it is usually shorter than the list of things you were planning to learn. Where the count is high and the evidence is strong, that is what your CV should lead with, and in my experience it is often work from the old career that people had been discounting. Anything with a low count can be parked, however interesting it looks.

What a real list looks like

Here is a shortened version of what someone moving from hospitality management into project coordination might end up with after fifteen postings.

Scheduling and resource planning appears in fourteen of them, stakeholder communication in thirteen, a specific project tool in eleven, budget tracking in nine, risk logs in six, a certification in four, and Agile terminology in three.

The evidence column tells a different story than they expected. Scheduling, communication, and budget tracking were their daily job for years, so those three cells fill immediately, in plain language a hiring manager would recognise. The project tool is empty, and so are risk logs. Agile appeared in three postings out of fifteen and had been the thing they were about to spend a month on.

The gap is two items. One is a tool that takes a fortnight to learn properly and a small project to evidence. The other is a document type they could produce from a past event they ran. The month of Agile study goes back on the shelf.

Where the method breaks

It only works with real postings. A list of skills from a blog post, or from a course syllabus, is someone's opinion of the role. Postings are the opinion of the people who will pay you, which is the one that counts.

It only works with honest evidence. The temptation is to count a course as proof. Employers do not, and the first technical conversation exposes it. A safer rule: if you would be nervous being asked to demonstrate it on the spot, the cell stays empty.

It goes stale. Requirements move, especially in roles touched by AI tooling, where the skill list for the same title can shift within a year. A list from eighteen months ago is a list for a role that may not exist in that form any more.

And it is slow to repeat. The first pass is an evening. Doing it again each time you refine the target, or for a second role, is where most people stop, which is where a tool earns its place.

Doing it with a tool

A skills check does the same comparison with the counting removed. You upload your CV, name the role, and it reads current postings for that role, tallies what they ask for, and lines that up against what your CV shows. The output is the same two columns: what the role wants, and what you can evidence, with the gap between them in the middle.

What the tool cannot do is be honest for you. If your CV claims a skill you cannot demonstrate, the check will believe the CV. So the evidence rule still applies, and it is worth going through your CV first with the same question: could someone inspect this?

The advantage is repetition. Run it for two roles and compare. Run it again in three months after you have closed a gap and see what moved. That is the loop the manual method makes too expensive to sustain.

Where do your skills stand? Run the free career check and get the two columns for the role you are aiming at: what postings ask for, what your CV already shows, and the gap between them, without an evening of counting.

What to do with the gap

Order it by count, not by interest. Close the top item with the smallest project that would satisfy the evidence rule, then put that project where a hiring manager can see it. Then the next item. Two or three closed gaps against a role's real requirements will do more for an application than a year of learning against an imagined one.

If you have been in tutorial hell, this is the way out that the courses could not give you: a short list of things to build, each one chosen because a posting asked for it.