Switching into tech, data or AI without a degree: a realistic roadmap

Plenty of people work in tech without a computer science degree. Many came from teaching, retail, finance, healthcare, hospitality or the military. But the route has changed. Entry-level roles are more competitive than they were a few years ago, and AI tools now handle some of the simplest tasks junior staff used to do. The people who succeed tend to choose a specific target, build real proof of skill, and use what they already know from their previous career. Here's how.

Step 1: pick a target role, not 'tech'

Tech is hundreds of jobs. Choosing one gives you a clear learning list and makes your applications coherent. These are common entry points for career changers, roughly from least to most technical:

• IT support and service desk: troubleshooting, accounts, devices. A classic first step, and a route into networks, cloud and security.
• Technical or customer support for software products: ideal if you've worked with customers.
• Data analyst: spreadsheets, SQL, dashboards and clear explanations. Strong fit for people from finance, operations, retail or research.
• QA and software testing: checking that products work, increasingly with automated tests.
• Business analyst or product operations: translating between users and technical teams.
• Junior developer: building software. Still achievable, but expect a longer path and stronger competition.
• Cybersecurity analyst: usually reached via IT support or networking rather than directly.
• AI-adjacent roles: AI operations, data annotation quality, AI trainer or automation specialist. Often open to subject experts who learn the tools.

Step 2: check real demand where you live

Before investing months, look at real postings for your target role in your city or for remote work you can do. Note how many there are, how many say 'entry level' or 'junior', which skills keep appearing, and what they pay. Use JobRipe jobs and the salary explorer. If almost no junior roles exist locally, consider a neighbouring role or remote options.

Step 3: learn the core skills, in order

Free and low-cost learning is plentiful; the challenge is focus. For each path, a sensible order:

• IT support: operating systems, networking basics, troubleshooting, accounts and permissions, then one cloud platform's fundamentals. Vendor-neutral entry certifications are widely recognised.
• Data analyst: spreadsheets in depth, SQL, one dashboard tool (Power BI, Tableau or Looker Studio), basic statistics, then Python. See the data analyst resume example.
• Developer: one language well (JavaScript or Python), Git, how the web works, databases, testing, then a framework. Use AI coding assistants, but make sure you understand every line.
• AI-related roles: how large language models work at a high level, prompting and evaluation, data quality, privacy, and automating workflows with the tools your target employers use. See the AI specialist resume example.

Step 4: build proof employers trust

Without a degree or job title, proof is everything. Aim for three to five projects that look like real work, not tutorial copies.

• Solve a real problem: a dashboard for a local business, a script that automates a task from your old job, a small app a community group uses.
• Write each up clearly: the problem, what you did, the tools, the result, and what you'd improve.
• Publish them: a simple portfolio page, GitHub for code, or a short write-up on a professional network.
• Get verifiable signals: JobRipe's skill checks add a 'Skill check passed' badge recruiters can see. They're not certifications, but they're quick evidence for core skills.

Step 5: get experience before your first tech job

• Inside your current employer: volunteer for the reporting, systems or automation work. An internal move is often the easiest way in.
• Freelance or volunteer projects for charities and small businesses.
• Apprenticeships and return-to-work programmes, which some employers run specifically for career changers.
• Open-source contributions, starting with documentation and small fixes.

Step 6: apply like a career changer

1. Use a resume that leads with a summary naming your target role, then a projects section, then experience rewritten to highlight the transferable parts.
2. Tailor every application to the posting's language, honestly. Check it with the ATS resume checker.
3. Explain the switch in one confident line in your cover letter: why this field, what you've done to prepare, what you bring.
4. Practise technical and behavioural interviews out loud with mock interview practice, and review common questions on interview questions by role.
5. Ask for referrals from anyone you know in the field. A warm introduction can matter more than the degree you don't have.

How long does it take?

It depends on your starting point, the hours you can give and the job market where you live, so be wary of anyone promising a fixed timeline. Many people need many months of steady part-time effort, and some need longer. Plan your finances for a longer search than you hope for, and keep your current income while you learn if you can.

Quick answers

• Am I too old to move into tech? No. Many employers value maturity and domain experience. Lead with what you've delivered. Our post on changing careers at 30, 40 or 50 has more.
• Should I do a bootcamp? It can help with structure and motivation. It isn't required, and it's not a guarantee. Compare the cost with free routes plus your own projects.
• Is AI making junior tech jobs disappear? It's changing them. Juniors who use AI tools well and can check their output are still hired; the bar for basic tasks is higher.