Turn a broad career interest into a shortlist
A target role is a type of position you deliberately investigate and prepare for. A shortlist helps you focus your CV, learning, and search terms. It is a working hypothesis, not a permanent commitment.
By the end of this lesson, you should be able to compare related job titles, check entry requirements and constraints, and choose a small set of roles that match your current evidence and goals. You can revise that shortlist as you learn from vacancies and conversations.
Start with interests, experience, and constraints
Write down the activities you enjoy and the problems you can already help solve. Use specific examples from employment, study, volunteering, caring responsibilities, or personal projects. Separate what interests you from what you can currently demonstrate.
- Interests: Do you prefer building interfaces, investigating data, supporting users, or troubleshooting systems?
- Evidence: What have you made, analyzed, organized, explained, or improved?
- Goals: What work do you want to learn, and what support would help you grow?
- Constraints: Where can you work, which hours are possible, and which eligibility or qualification conditions must you meet?
Research role families and related job titles
Titles are useful search terms, but employers use them differently. Investigate related titles and compare daily responsibilities. The examples below are options to research, not verified demand rankings or promises of easy entry.
A junior label does not remove an employer’s requirements. Cloud and security roles may expect earlier IT experience; check each listing. Do not practice security work on systems without authorization.
| Area | Example search titles | Work and evidence to investigate |
|---|---|---|
| Software development | Junior Software Engineer; Junior Frontend Developer; Junior Web Developer | Building and testing features; a documented project and explanation of your contribution. |
| Data and business intelligence | Junior Data Analyst; Reporting Analyst; Junior BI Analyst | Cleaning data, querying it, and explaining findings; an analysis or dashboard with assumptions. |
| Cybersecurity | Junior Cybersecurity Analyst; SOC Analyst; Security Support Analyst | Networking, monitoring, investigation, and reporting; a safe practice lab or written analysis. |
| Cloud or IT operations | IT Support Technician; Service Desk Analyst; Junior Cloud Support Engineer | Troubleshooting and supporting systems; a documented lab, support scenario, or relevant experience. |
Compare entry requirements and responsibilities
For each possible target, read several relevant vacancies. Write down the main work, what is expected on day one, required credentials, and the experience level described. Distinguish responsibility for a whole system from contributing under supervision.
Your evidence can come from different settings, but describe that setting honestly. A personal API project may show useful skills; it is not the same as operating a production service for paying customers.
- Collect vacancies for related titles in locations you can work in.
- Underline repeated tasks and essential requirements.
- Match each requirement to something you have done; give a specific example or mark it as a gap.
- Check whether missing items are essential, preferred, or unclear. Ask for clarification when appropriate.
Separate manageable gaps from major mismatches
A skill gap is the difference between a requirement and what you can currently demonstrate. Prioritize recurring, relevant gaps. Choose a concrete output, such as a tested query or a troubleshooting explanation, rather than a vague goal to ‘learn everything.’
Choose a primary target and suitable alternatives
A primary target is the role family you will focus your materials and research on first. An alternative should share meaningful skills and fit your constraints, not simply have an attractive title. Keeping a small shortlist makes it easier to learn what employers want.
Do not reduce eligibility to an average score: an explicit constraint can rule out a vacancy even when other aspects fit well. Revisit the shortlist after a planned review rather than changing direction after every rejection.
| Question | Role A | Role B | Role C |
|---|---|---|---|
| Main responsibilities | Record tasks | Record tasks | Record tasks |
| Essential requirements I can demonstrate | Add evidence | Add evidence | Add evidence |
| Gaps and a realistic next action | Name one priority | Name one priority | Name one priority |
| Location, hours, eligibility, credentials | Check constraints | Check constraints | Check constraints |
| Interest and decision | Primary, alternative, or revisit | Primary, alternative, or revisit | Primary, alternative, or revisit |
Common mistakes when choosing roles
Avoid choosing only by salary headlines, copying someone else’s path, or treating a role family as a single job. Review the requirements of your target employer and adapt your approach to your circumstances.
- Searching one title only: test related titles and read the responsibilities.
- Targeting senior work because you recognize the tools: compare ownership, scope, and experience expectations.
- Listing interests as proven skills: keep separate columns for evidence and learning goals.
- Ignoring practical constraints: check location, working arrangements, and eligibility early.
Practical activity: select a realistic shortlist
Choose three titles from one or two related families. Complete the comparison worksheet using at least one actual vacancy for each, then validate your initial impressions with additional listings.
- Write a sentence explaining your interest in each role.
- Record the tasks, requirements, constraints, and your strongest evidence.
- Identify one gap for each and estimate the work needed to produce evidence.
- Choose one primary target and one alternative, with reasons tied to the vacancies.
- Save the comparison, request feedback from someone familiar with the work, and set a review date.