Switching careers into tech: a realistic plan for the first year
By Axyra Nova Editorial · 4 October 2026 · 5 min read · Careers
People move into tech from teaching, nursing, retail, hospitality, finance, the arts and many other fields. Some become developers; others become analysts, designers, project managers, testers or support specialists. The path is rarely as fast as advertisements suggest, but with a clear plan it is very achievable.
This guide sets out a realistic approach to a career switch into tech over roughly a year, using mostly free resources.
Be realistic about the timeline
Learning enough to be hired takes time, especially while working or caring for others. Progress depends on how many hours you can study, the role you are aiming for and the job market where you live. Some people find a first role within months; others take longer.
Plan for a steady pace you can keep up, rather than an intense burst that leads to burnout.
Step 1: Explore the options
"Tech" covers many roles. Before committing, spend a few weeks exploring:
- Web development: building websites and applications.
- Data analysis: turning data into insights with spreadsheets, SQL and visualisation tools.
- UX and design: researching users and designing interfaces.
- Project management: planning and coordinating technical work.
- Quality assurance: testing software to find problems.
- IT support: helping people and organisations with technology.
Occupational profiles on O*NET OnLine describe typical tasks, skills and tools for many of these roles. Try a short free course in two or three areas to see what you enjoy.
Step 2: Use what you already know
Your previous career is an asset, not a blank space:
- A teacher understands explaining complex ideas, which suits technical writing, training and education technology.
- A nurse understands healthcare workflows, valuable in health tech.
- A retail manager understands customers and operations, useful in ecommerce and data.
- An accountant understands financial data, a strong base for data analysis.
Look for roles where your domain knowledge plus new technical skills make you more valuable than someone with technical skills alone.
Step 3: Choose a structured learning path
Free, structured courses help you avoid jumping between random tutorials. Some well-regarded options:
- Web development: The Odin Project and freeCodeCamp.
- Computer science foundations: CS50x.
- Data analysis: Kaggle's Python course and SQL courses.
- Project management: introductory courses and the Scrum Guide.
Our learning platform collects free courses by track. Pick one path and finish it before starting another.
Step 4: Study consistently
A sustainable routine matters more than long sessions:
- Set aside regular time, even an hour a day.
- Keep a learning log of what you studied and what confused you.
- Build small things as you go instead of only watching videos.
- Join a community where you can ask questions.
Step 5: Build real projects
After the basics, projects become your main evidence. Aim for three that relate to the role you want and, ideally, to your previous field. A former pharmacist might build a medication reminder app or analyse public health data; a former shop manager might build a small inventory dashboard.
Our guide to building a tech portfolio that gets interviews explains how to choose and present projects.
Step 6: Get practical experience
Experience can come from many places before your first job:
- Volunteering for nonprofits that need websites or data help.
- Freelance projects for small businesses.
- Open source contributions.
- Internal projects at your current job, such as automating a spreadsheet process.
Each gives you real problems, real users and stories to tell in interviews.
Step 7: Prepare your job search materials
- CV: rewrite it to highlight technical skills, projects and transferable experience. Our guide to writing a tech CV explains how.
- LinkedIn: update your headline and summary to reflect your new direction.
- GitHub or portfolio site: make sure projects are easy to find.
Step 8: Look for first roles
First roles in tech often have titles like junior developer, associate analyst, technical support, QA tester or project coordinator. Consider:
- Roles that combine your old field with new skills.
- Smaller companies, which may value broad experience.
- Internal moves at your current employer.
- Apprenticeships and returner programmes.
Apply consistently, tailor each application and keep learning while you search.
A sample first-year plan
| Months | Focus |
|---|---|
| 1–2 | Explore roles, try short courses, choose a direction |
| 3–6 | Complete a structured course, build small projects |
| 7–9 | Build three portfolio projects, start volunteering or freelancing |
| 10–12 | Polish CV, LinkedIn and portfolio, apply for roles, network |
Adjust it to your own time and goals.
A worked example
A secondary school science teacher wanted to move into data analysis. He spent the first two months trying short courses in web development and data, and found he enjoyed working with data most. Over the next four months, he completed free Python and SQL courses in the evenings.
He then built three projects: an analysis of public school performance data, a dashboard tracking his own students' anonymised test results with the school's permission, and a SQL project combining several public datasets. He volunteered to help a local charity analyse its donation records.
When he started applying, he targeted education technology companies and data roles in schools and universities, where his teaching background was a clear advantage. His first role was as a data analyst for an education nonprofit.
Managing money and expectations
- Avoid expensive courses until you know the field suits you; many excellent resources are free.
- Be cautious of programmes promising guaranteed jobs or very high salaries.
- If possible, keep earning while you learn.
- Remember that early tech roles may pay less than your current senior position in another field, at least at first.
How Axyra Nova helps
Axyra Nova helps new freelancers find small business clients, which can provide practical experience and income while you build your career. See the features page.
Frequently asked questions
Am I too old to switch into tech?
People switch careers into tech at many ages. Previous experience is often an advantage, especially in roles that combine technical and domain skills.
Do I need a degree?
Many tech roles do not require a computer science degree, though some employers prefer one. A strong portfolio and relevant skills matter a great deal.
Should I do a bootcamp?
Bootcamps can provide structure and support, but they are expensive. Try free resources first to confirm your interest.
Which programming language should I learn first?
It depends on the role. JavaScript suits web development; Python and SQL suit data analysis.