Upskilling for a career change: picking skills employers actually ask for

Start with the job postings, not the course catalogue

Before you open a single learning platform, collect 20 to 30 real job postings for the role you want. Use LinkedIn, Indeed, Seek (Australia), or the employer career pages you actually care about. Save them somewhere you can search across all of them at once, a spreadsheet or a plain text file works fine.

Read the requirements sections carefully. Ignore the aspirational language like 'passionate self-starter' and focus on the concrete nouns: tool names, certifications, methodologies, and years of experience. These are the things a recruiter will scan for in the first 10 seconds.

• Copy the 'requirements' and 'nice to have' sections from each posting into one document
• Highlight every skill, tool, or certification mentioned more than once
• Note whether items appear under 'required' or 'preferred' so you know which to prioritise
• Pay attention to version numbers and recency, for example 'Python 3' or 'AWS certified within the last two years'

How to find the skills that actually repeat

Once you have your 20 to 30 postings in one place, do a simple word frequency check. Paste the text into a free tool like WordCounter or just use Ctrl+F to count how many postings mention a given term. Any skill that appears in more than half your sample is a core requirement. Skills that appear in fewer than a quarter are optional extras.

For a data analyst role in 2026, you would typically find SQL, Excel or Google Sheets, and at least one visualisation tool such as Tableau or Power BI appearing in the majority of postings. Python appears in roughly half, depending on the seniority level. That tells you where to spend your first 80 hours versus your next 40.

Choosing where to learn each skill

Not all credentials carry the same weight with employers. Some roles have a clear industry standard. Project management postings in the US, Canada, the UK, and Australia still list PMP or CAPM from PMI, or PRINCE2 for UK and Australian government roles. Cybersecurity postings list CompTIA Security+, CISSP, or CEH. Cloud roles list AWS, Azure, or GCP certifications by name.

For skills without a dominant certification, employers care more about demonstrated work than the name of the platform you used to learn. A portfolio project, a GitHub repository, or a case study you can walk through in an interview will outperform a certificate from a lesser-known provider.

Coursera, edX, LinkedIn Learning, and Google Career Certificates are broadly recognised. For technical skills, freeCodeCamp and The Odin Project are respected in developer communities. For data skills, Kaggle competitions give you something concrete to show.

• Match the credential to what postings name explicitly, not what the platform markets
• Prefer credentials that have a renewal or exam component, they signal current knowledge
• Build at least one portfolio piece per core skill before you start applying
• Keep learning time under 6 months per skill cluster so you stay current with what employers are asking for

Transferable skills you already have and how to name them

Career changers underestimate how much of their existing experience maps to the new role. The problem is usually language, not substance. A teacher who managed a classroom of 30 students has experience in stakeholder communication, curriculum design, and performance tracking. Those are the same activities a learning and development coordinator does, just described differently.

Go back to your frequency list and look at the soft skills and process skills that repeat. Then write one sentence for each that connects your past work to that skill using the exact phrasing from the postings. This is not spin. It is translation.

1. Pick a repeated skill from your posting analysis, for example 'cross-functional collaboration'
2. Write down two or three times you did that thing in your current or past role
3. Rewrite each example using the vocabulary from the postings, not your old industry's jargon
4. Test the sentence by asking whether a recruiter in the new field would recognise it immediately

When to start applying and how to close the gap on paper

A common mistake is waiting until you feel fully ready. Most job postings list more requirements than any single candidate meets. Research on hiring consistently suggests that candidates who meet 60 to 70 percent of listed requirements are competitive for a role, provided the core requirements are covered.

Once you have the top three to five repeated skills from your analysis and can demonstrate each one, start applying to roles where you meet the core requirements. Use the 'preferred' skills as your ongoing learning list while you are in the application process.

Break-In Bad's assistant Omar reads the full text of each posting, including location, visa requirements, and experience level, and scores your fit before you spend time applying. Roles scored 75 percent or above are submitted automatically. Roles between 45 and 74 percent are flagged for your review so you can decide whether the gap is worth closing first. This keeps you from applying to roles where a missing core skill will disqualify you immediately, and from skipping roles where you are stronger than you think.

Keeping your resume current as you build skills

Your resume needs to reflect new skills as you acquire them, not just at the end of a long learning period. Add a skill to your resume the moment you can demonstrate it with a project, a certificate, or a work example. Recruiters in 2026 use applicant tracking systems that parse skills sections and match them against posting keywords, so the phrasing matters as much as the substance.

Use the exact terms from the postings. If postings say 'Agile methodology', do not write 'agile approach'. If they say 'Salesforce CRM', do not write 'CRM tools'. Precision here is not pedantry, it is how the system finds you.

• Update your skills section after completing each credential or project
• Mirror the exact terminology from the postings you are targeting
• List tools with version or tier where relevant, for example 'Tableau Desktop' or 'AWS Solutions Architect Associate'
• Remove skills from your previous career that do not appear in any of your target postings and that you cannot connect to the new role