In this guide
Career changes and transitions
Moving into tech: coding and non-coding routes
Tech roles that use skills you may already have, which ones need coding, the evidence employers look for and how to build a small portfolio as you learn.
Roles and what they need
| Role | Coding needed? | Useful background |
|---|---|---|
| Customer or technical support | Rarely | Customer service, troubleshooting, patience |
| Customer onboarding or training | No | Teaching, training, account management |
| Project or delivery coordination | No | Planning, scheduling, stakeholder management |
| Quality assurance testing | Sometimes, increasingly helpful | Attention to detail, process thinking |
| Data analysis | Spreadsheets and query languages | Reporting, finance, research |
| Software development | Yes | Problem solving and persistence; demonstrable projects |
Start from what you already do well
The fastest route is usually the one closest to your existing strengths. A support agent at a software company, a project coordinator in a digital agency or a trainer for a technology product can learn the industry from the inside and move further later.
Illustrative example
Three people choosing different routes
- A hotel duty manager targets customer support at a booking software company, using incident handling and escalation experience.
- An events coordinator targets project coordination at a digital agency, using schedules, suppliers and budgets.
- A finance assistant learns spreadsheet modelling and a query language and targets junior data analyst roles.
Build evidence as you learn
Courses help you learn, but employers want to see what you can do. For each role, a small piece of real work beats a long list of certificates.
Evidence ideas by route
- Support: a short knowledge-base article you wrote explaining how to fix a common problem.
- Project coordination: a project plan you used for a real event or change.
- Quality assurance: a set of test cases and bug reports for an app you use.
- Data analysis: an analysis of a public dataset with clear charts and conclusions.
- Development: two small working projects with readable code and a short write-up.
Learn the vocabulary of the role
Read job adverts and team blogs for your target role and note the terms that keep appearing. Use them accurately on your resume and in interviews where they describe what you have genuinely done, and say plainly when you are still learning something.
Common questions
Am I too old to move into tech?
Many people move into technology roles later in their careers, especially non-coding roles that reward experience with customers, projects and operations.
Do I need a computer science degree?
For most roles, no. Some employers prefer degrees for certain technical roles, but many hire on demonstrated skills and relevant experience.
Put it into practice
See how Luceria helps with thisDrafted with AI assistance and checked against Luceria’s editorial standards. Examples are illustrative, not real people’s results. Spotted something out of date? Tell us.