Choose a role path from the work you want to do

Start with tasks, then compare titles

Technology job titles can describe different work at different employers. A frontend developer might spend a day improving accessibility; another might maintain a design system. A data engineer might build batch pipelines or operate a streaming platform. Start by reading the tasks in several real vacancies, rather than choosing a title in isolation.

Write down the work that interests you, the skills you already practise and the constraints that matter to you. Location and working arrangements are useful preferences to keep separate from your skills.

Describe your evidence honestly

In Career Compass, Learning means you are developing a skill. Project experience means you have used it in a practical project. Professional experience is self-reported use in a work setting. These labels provide context; they do not certify proficiency.

Role suggestions compare your choices with curated core and supporting skills. A strong overlap means the selected terms overlap with the profile. It does not mean that an employer will consider you qualified.

Try one small project

Use a suggested role’s practice prompt to build something small enough to finish. Keep a short account of the problem, your choices, what worked and what you would improve. The aim is to learn whether you enjoy the work and create something concrete to discuss.

• Compare three vacancies for the same path.
• Choose one missing skill to practise in context.
• Review your direction after the experiment rather than committing to a title immediately.