You have decided that you want to explore a career in tech.
What should you learn first?
Cloud computing? Cyber security? Coding? Data? Artificial intelligence? Project management? A long list of certifications you had never heard of last week?
This is where many people become overwhelmed.
They start researching tech and quickly feel that they need to understand all of it before they can apply for anything.
You do not need to learn all of tech.
You need to learn what matters for the role you are aiming for.
Choose a role before choosing a course
This is the most important step.
“I want to get into tech” is too broad to guide your learning.
A project coordinator, business analyst, service desk analyst, customer success manager, product manager and data professional need different knowledge.
Before you buy a course, choose one or two roles to explore.
Then:
- read several job descriptions
- compare the responsibilities
- note the skills and knowledge that appear repeatedly
- speak to people doing the role
- understand what an ordinary week looks like
- decide whether the work genuinely appeals to you
Your learning plan should be built backwards from the work.
Understand the difference between knowledge and experience
A knowledge gap is something you can learn.
Examples include:
- understanding basic project terminology
- learning how requirements are gathered
- knowing what cloud computing means
- understanding service management principles
- learning the purpose of data governance
An experience gap is something you need to do.
Examples include:
- running a stakeholder meeting
- mapping a real process
- supporting a system rollout
- analysing a dataset and explaining the result
- creating training for a new tool
- managing a customer issue through to resolution
People often try to solve both gaps with courses.
That does not work.
Learning can give you knowledge and confidence. Experience gives you evidence.
You need to know which gap you are closing.
Build a small foundation in how technology works
Even if your target role does not require coding, a basic conceptual understanding will help you communicate and learn.
Useful foundation topics may include:
- how organisations use hardware, software and networks
- the difference between on-premises systems and cloud services
- why identity, access and cyber security matter
- how data is collected, stored and used
- how technology projects move from an idea to delivery
- how services are supported after implementation
- the difference between a product, project and service
You do not need expert depth in all of these areas.
The goal is to understand the language and how the pieces connect.
Then go deeper only where your target role requires it.
What should different roles learn first?
Project coordination or project management
Start with:
- project stages and terminology
- plans, actions, risks and dependencies
- stakeholder communication
- common delivery approaches such as Agile and waterfall
- how technology projects differ from general business projects
Then look for an opportunity to support or organise a real piece of work.
Business analysis
Start with:
- how to define a problem
- stakeholder interviews
- process mapping
- requirements gathering
- the difference between a need and a proposed solution
- how to document and communicate findings
Practise by mapping a process you already know and identifying where it could improve.
Customer success
Start with:
- customer goals and outcomes
- adoption and value
- relationship management
- customer journeys
- renewal risk and escalation
- how the product or service solves a real problem
Build evidence from customer service, account management, training or stakeholder work.
Change management or digital adoption
Start with:
- why people respond differently to change
- stakeholder analysis
- communication planning
- training and support
- adoption measures
- common change frameworks
Look for a current change where you can support communications, feedback or learning.
Service desk or IT support
Start with:
- basic computer, network and cloud concepts
- common user problems
- troubleshooting approaches
- identity and access basics
- ticket handling and escalation
- customer service in a technical environment
Practical labs and entry-level certifications may be useful here, but the ability to communicate calmly remains essential.
Product management
Start with:
- customer problems and user needs
- product discovery
- prioritisation
- roadmaps and outcomes
- working with design and delivery teams
- measuring whether a product creates value
Seek examples where you have gathered needs, balanced priorities or shaped an improvement.
Data roles
Start with the level required for the specific role.
For data analysis, this may include:
- spreadsheet confidence
- data quality
- basic statistics
- data visualisation
- querying data
- explaining insight clearly
For data governance, the focus may be ownership, standards, quality, policy and responsible use rather than coding.
Start free before you spend money
Before committing to a large qualification, test the subject.
Use a relevant free course, vendor learning platform, webinar, video series or community resource for a few weeks.
You are testing two things:
- Can I understand and apply this?
- Do I actually enjoy the subject enough to continue?
Set a small commitment, such as two hours a week for four weeks.
At the end, ask what you can now do or explain that you could not before.
If the answer is unclear, the resource may not be working for you.
Be careful with certifications
A certification can help when it is recognised, relevant and connected to the role.
It can also become an expensive distraction.
Before paying, ask:
- Does this appear in the roles I am targeting?
- Will it teach knowledge I genuinely need?
- Is there a practical element?
- Could an apprenticeship or workplace budget fund it?
- Am I choosing it because it is useful, or because studying feels safer than applying?
A certificate proves that you completed an assessment.
What gets you hired is your ability to explain what you learned, why it matters and how you would apply it.
Speak to real people early
It is easy to spend months watching videos without learning what the role is actually like.
Speak to someone doing the work.
Ask:
- What do you spend most of your time doing?
- Which knowledge did you need on day one?
- What did you learn after starting?
- Which skills matter more than the job advert suggests?
- What would you recommend to someone changing careers?
One useful conversation can prevent you from following the wrong learning path.
Turn learning into evidence
After each topic, ask how you can use it.
If you learn process mapping, map a process.
If you learn stakeholder analysis, apply it to a real project.
If you learn data visualisation, create a simple dashboard and explain the insight.
If you learn digital adoption, create a short plan for introducing a tool to a group of users.
If you learn service management, examine how an issue is logged, escalated and resolved where you work.
Application makes learning easier to remember and gives you something to discuss.
Know what to ignore for now
You will see interesting topics that are not relevant to your immediate direction.
Keep a “later” list.
This allows you to stay curious without abandoning the plan every time a new course appears.
For now, ignore learning that:
- does not connect to your target role
- is far more advanced than the work requires
- duplicates something you already understand
- has no practical application
- is only attractive because it sounds impressive
You can return to it later if your direction changes.
When have you learned enough to apply?
Not when you know everything.
You have learned enough to begin applying when you can:
- explain the purpose of the role
- understand the common language used in job adverts
- demonstrate relevant core skills
- discuss several practical examples
- identify your remaining gaps honestly
- show how you are continuing to learn
Applying is part of the learning process.
It shows you what employers respond to and which gaps are real rather than imagined.
A focused first thirty days
1
Week 1
Choose one role. Read five job descriptions. Write down the repeated skills and knowledge.
2
Week 2
Speak to one person doing the role. Compare their experience with the adverts.
3
Week 3
Start one free learning resource focused on the most important knowledge gap.
4
Week 4
Create one small practical example or identify a real opportunity to gain experience. At the end of the month, decide what should continue, what should stop and what your next action will be. That is a learning plan. It is small enough to begin and specific enough to matter.
So, what should you learn first?
Learn enough about the industry to choose a direction.
Then learn the knowledge your chosen role genuinely requires.
At the same time, look for experience that allows you to apply it.
Do not measure progress by the number of courses you complete.
Measure whether you are becoming more able to understand the work, demonstrate the skills and make a credible case for yourself.
Getting Into Tech (Without Starting Over) helps you work out what technical knowledge is actually expected and what you can ignore. The companion workbook helps you separate knowledge gaps from experience gaps, choose a starting resource and decide whether paid learning is genuinely necessary.
Focus first.
Learn with intention.
Then use what you learn.