The guide
How to get into tech
What the industry actually is, the roles nobody explains properly, what you already bring, and how long it really takes. No jargon, no gatekeeping.
Most people who would do well in tech never apply.
Not because they tried and were turned down. Because they ruled themselves out early, usually before anyone had explained what working in tech actually involves.
The picture in most people’s heads is a developer at a keyboard.
That picture is not wrong, it is just very small. It covers a fraction of the industry and leaves out almost everything else that makes technology reach the people who use it.
This guide is the wider view. What the industry actually is, what the roles are, what you already bring, what you would genuinely need to learn, and how long it realistically takes. No promises that anyone can code in ninety days. No pretending the job market is easy. Just the honest picture.
1. You do not have to be technical to work in tech
This is the belief that stops more people than anything else, so it is worth dealing with first.
Technology companies are companies. They plan work, manage budgets, talk to customers, run projects, handle risk, write documentation, train people, sell things, support users and keep everything legal. Very little of that involves writing code.
The people doing that work are not standing outside the real business, helping out at the edges. They are the reason the technology reaches anyone at all. Something nobody can use, nobody has been trained on and nobody has sold is not a product. It is a file sitting on a server.
You will need to understand technology conceptually. You will need to follow a conversation about how a system fits together, ask sensible questions, and know roughly what is difficult and what is straightforward. That is a very different thing from being able to build it yourself.
Tech only works because of the people across every part of it, not just the ones writing code.
Going deeper: Can you work in tech without coding?
2. What the industry actually is
Tech is not one thing. It is six distinct areas, each with its own culture, its own roles and its own kind of people. They all connect and depend on each other to make technology work.
Most people find they are drawn to one or two. As you read, notice which descriptions make you lean forward, and notice which feel completely out of reach. Both reactions tell you something useful.
Area 01: Building it
Creating technology. Designing systems, building applications and solving technical problems. This is the area most people picture when they think of a career in tech, and it is the one that most commonly requires formal technical training. That does not make it off limits, it does mean it is a longer journey for most career changers. The good news is that the other five areas are genuinely open to you right now.
Example roles: Software Developer, Cloud Engineer, Solutions Architect.
Area 02: Running it
Supporting and maintaining technology. Helping users, fixing issues and keeping systems running. This is one of the most common entry points into the industry and a brilliant way to learn how organisations actually operate. You become the person people rely on when things go wrong, which means you build knowledge and credibility fast.
Example roles: IT Support Analyst, Service Desk Analyst, Infrastructure Manager.
Area 03: Securing it
Protecting systems, data and users. Monitoring threats, managing access and investigating issues. Worth knowing: not all security roles are deeply technical. Governance, risk and compliance work, the rules and policies and audit processes that keep organisations safe and legal, is heavily people-focused.
Example roles: Cybersecurity Analyst, GRC Analyst, Data Protection Officer.
Area 04: Understand it
Working with data and information. Analysing, reporting and identifying trends, then turning what you find into something useful. You do not need to be a mathematician. You need to be curious, methodical and good at asking the right questions. The tools are learnable. The instinct to question what the data is really telling you is the harder skill to teach, and you may already have it.
Example roles: Data Analyst, Business Analyst, UX Researcher.
Area 05: Enabling it
Planning how technology is introduced, supporting change and helping people get real value from it. The technology itself is rarely the hardest part of a project. Getting people to understand it, trust it and actually use it is. This is where experience from outside tech is not just useful, it is a genuine advantage.
Example roles: Project Manager, Change Manager, IT Trainer.
Area 06: Selling it
Communicating the value of technology to customers. Understanding their challenges and helping shape the right solutions. This is not the stereotypical hard sell. At its best it is consultative, helping organisations work out what they actually need rather than pushing products at them. Many of the highest earners in tech work in this area and never write a line of code.
Example roles: Account Manager, Pre-Sales Consultant, Customer Success Manager.
Going deeper: The six areas of tech. The book covers each area in full, including which backgrounds transfer most naturally into each one.
3. The roles nobody explains properly
Job titles in tech are unhelpful. They are inconsistent between companies, full of jargon, and they rarely describe what the person actually does all day.
A business analyst at one company spends their time in workshops with stakeholders. At another they are deep in process mapping and requirements documents. Same title, quite different days.
So when you are exploring roles, ignore the title first and ask three questions instead:
- What does this person actually do on a Tuesday?
- Who do they spend their time with?
- What does good look like in this role, and how would anyone know?
The answers tell you far more than a job title ever will. They also give you something real to talk about at interview.
Going deeper: What are the non-technical jobs in tech?
4. What you already bring
People changing career into tech tend to assume they are starting from zero. Almost nobody is.
If you have worked in retail, hospitality, healthcare, education, admin, finance, logistics or any other field, you have been doing things tech employers need. Handling frustrated people calmly. Spotting when a process is broken. Explaining something complicated to someone who does not want to hear it. Keeping several things moving without dropping any of them.
Those are not soft extras. They are the skills that separate people who do well in tech from people who struggle, and they are far harder to teach than a piece of software.
Your industry knowledge matters too. Someone who has worked in a hospital understands how clinical staff actually behave under pressure. That is genuinely valuable to a company selling into healthcare, and no amount of training produces it.
The work is not acquiring these skills. It is learning to recognise them, name them properly, and evidence them.
Going deeper: The skills you already have that tech employers want
5. Working out where you fit
This is the hard part, and most advice skips it entirely.
It is tempting to pick the role with the best salary or the most job adverts. That approach tends to end badly. You spend six months learning something that does not suit you, then conclude tech was not for you after all, when actually that one role was not for you.
Better questions to sit with honestly:
- Do you want variety and interruption, or depth and focus? Both exist in tech, in different roles.
- Do you get energy from people, or does a day of meetings leave you empty?
- Do you prefer being handed a clear problem, or working out what the problem even is?
- How do you feel about pressure that arrives without warning?
- What have you enjoyed most in any job you have had, including jobs nothing to do with tech?
There is no scoring system that tells you the answer. What helps is being honest rather than aspirational, because the version of yourself you would like to be is not the person who has to do the job every day.
Going deeper: Is tech even for me?
6. What to learn, and what to ignore
The most common mistake is trying to learn all of tech at once. Someone starts a coding course, then a cloud certification, then a data course, gets six weeks into each, and finishes none of them.
Pick a direction first. Not forever, just for now. Then work backwards from the role to the learning.
Read several real job adverts for that role. Not one, several. Write down what keeps appearing. That list is your curriculum, and it is written by the people who do the hiring.
Some things worth knowing before you spend money:
- A great deal of quality learning is free. Vendor learning platforms, foundation-level courses and open documentation cover more than most people expect.
- Certifications help most where they are genuinely expected for the role. Elsewhere they matter less than being able to talk sensibly about the work.
- Applying something badly teaches you more than watching a course perfectly. Volunteer for the thing at work nobody wants to own.
- Expensive bootcamps are not automatically better. Ask what their graduates are actually doing now, and be wary of anyone who will not tell you.
Going deeper: What do you actually need to learn first?
7. How long it really takes
Longer than the adverts promise, shorter than you fear.
It depends on where you are starting, which role you are aiming at, and how much time you can genuinely give it each week. Someone already working alongside a technical team has a shorter route than someone starting completely cold.
What is consistent is this: the people who move fastest are the ones who picked one direction and stayed with it. Not the ones who studied hardest. The ones who stopped changing their mind.
It also rarely happens in one jump. A sideways move into a role that touches technology, then a move into tech properly, is a very common route and a perfectly respectable one. Your first role is a way in, not your destination.
Going deeper: How long does it really take to get into tech?
8. How to position yourself
You can have the right skills and still get nowhere, because you are describing yourself as someone who is trying to get into tech rather than someone who does this work.
The shift is small and it matters enormously.
- Lead with the work, not the gap. Do not open with what you lack. Open with what you have done that is relevant.
- Translate your experience. Coordinating a ward rota is resource planning under constraint. Say it in the language the role uses.
- Give evidence, not adjectives. Nobody believes organised. Everybody believes a specific example with a result attached.
- Make your CV match the advert. Generic applications are one of the most common reasons capable people get rejected.
- Have a straight answer for why tech. Vague enthusiasm reads as a lack of thought. A clear reason reads as someone who has decided.
Your LinkedIn should say what you do and what you are moving towards, in plain words. Not a list of buzzwords. People hire people they can picture in the role.
9. What nobody tells you
A few honest things that rarely make it into career advice.
Everyone is making it up more than you think. The confident person in the meeting is often confident about one narrow thing and lost about the rest. Technology changes fast enough that nobody has caught up.
You will not understand half the acronyms for a while. That is normal. Asking what something means is treated far better than pretending, and the people worth working with will simply tell you.
Other people sometimes see your strengths before you do. Feedback that stings can be the most useful thing you get. Someone may point you at a role you had dismissed as too technical or too senior, and be right.
The industry has real problems. Some workplaces are exhausting. Some people will make assumptions about you. Restructures happen. It would be dishonest to describe tech as uniformly welcoming, because it is not.
Staying still has a cost too. It is easy to weigh up the risk of moving and forget to weigh up the risk of not moving. Another five years in work that is slowly flattening you is not the safe option it looks like.
Nobody is going to give you permission. There is no point at which you become officially ready. Most people who made this move did it while still feeling underqualified.
Where to go from here
If one section of this landed harder than the others, start there. Follow the link, read properly, then come back.
If you want the whole thing in one place, with the detail this page cannot hold, that is what the books are for. Getting Into Tech (Without Starting Over) covers all six areas in full, the roles in plain English, what you can realistically earn, what to learn, and how to position yourself, with reflective exercises throughout. The Companion Workbook goes further into you specifically: your strengths, your working style, and a plan you write yourself.
Keep going
The door into tech is wider than you think
You just need someone to show you where it is. The books walk you through the roles, the reality, and the routes in. The resources are free, and they are a decent place to start.