"Tech" is not one career. It covers dozens of roles with very different daily work, from supporting users' computers to analysing data, designing interfaces, managing projects, testing software or writing code. Career changers often fixate on software engineering when another role would suit their background, temperament and timeline better. This note maps the main entry routes, explains how to test your interest cheaply and suggests how to build credible evidence. It does not predict hiring conditions, which change and vary by area.
Map the roles first
Here are common technology-related roles career changers consider, grouped by the kind of work involved. Look each up in the BLS Occupational Outlook Handbook and O*NET for current details on tasks, typical entry requirements and pay.
- Supporting people and systems: computer support specialists, help desk and IT support, network and systems administration. Strong fit for people who enjoy troubleshooting and helping others.
- Working with data: data analysts, database work, business intelligence. Suits people who like spreadsheets, patterns and questions about numbers.
- Building software: software developers, web developers, quality assurance testers. Suits people who enjoy logic, detail and building things.
- Designing experiences: UX research and design, web design. Suits people interested in how others use products.
- Coordinating work: project and product management, technical writing, implementation and customer success roles. Often suits people with domain experience and communication skills.
- Protecting systems: information security. Usually requires solid IT fundamentals first.
Many career changers find their best entry point is a role that combines their existing domain knowledge with technology, for example a nurse moving into clinical informatics, an accountant into finance systems, or a teacher into instructional technology.
Check the real entry requirements
For each role, the Handbook's "How to Become One" tab describes typical education and training. Then check ten local postings for the exact title. Note degree requirements, certifications, tools and years of experience. Postings often list more than employers strictly require, but repeated items tell you what matters. Our guide to researching careers with BLS and O*NET explains the process.
Test your interest cheaply
Before paying for a bootcamp or degree, spend a few weeks on free or low-cost material:
- Complete an introductory course or tutorial in the core skill: basic programming, spreadsheets and SQL, networking fundamentals or design principles.
- Do one small, real task: automate a repetitive spreadsheet job at work (with permission), build a simple personal website, or analyse a public dataset.
- Notice how you feel after several sessions of focused practice. Frustration is normal; complete lack of interest is a signal.
The 90-day exploration plan can help you structure this testing period.
Choose a training route deliberately
Options include community college programs, bootcamps, vendor or industry certifications, apprenticeships and self-study. Each has trade-offs in cost, time and recognition, explored in our comparison of bootcamps, community college and certificates. For IT support and some other roles, entry-level certifications are common; CareerOneStop's Certification Finder lists them by occupation. Apprenticeship.gov includes registered apprenticeships in some technology occupations.
Be wary of programs that promise specific salaries or guaranteed jobs, especially with high-pressure enrolment or complex financing. See our training scams note.
Build evidence, not just credentials
Employers hiring career changers want proof you can do the work. Useful evidence includes:
- Projects that solve a realistic problem, ideally connected to your current field. Document what you built, why and what you learned. Label independent projects honestly.
- Work you did in your current job using technology: a reporting process you automated, a system rollout you helped coordinate, training you delivered on new software.
- Contributions to open-source projects, community organisations or volunteer groups that need technical help.
- Writing that explains what you learned, which shows communication skills.
Our transferable skills note explains how to present past experience truthfully.
Use your current job as a bridge
Before you leave, look for technology-related work where you are: volunteer for a system implementation, become the go-to person for a tool, help analyse data for your team. Some employers support internal moves into technical roles. This builds evidence while you are still paid.
Expect a process, not a leap
Hiring for entry-level technology roles can be competitive, and timelines vary. Plan finances accordingly with the cash runway calculator, and estimate training costs and potential returns cautiously with the retraining payback tool. Informational conversations with people in your target role, covered in our informational interview guide, will tell you more about local conditions than any general article, including this one.
Evidence to gather next
- Choose two specific tech roles and read their Handbook and O*NET profiles.
- Complete one free introductory course or tutorial in each before paying for anything.
- Build one small project relevant to your current field and document it clearly.
- Find three people in your target role for informational interviews.
Do I need a computer science degree to work in tech?
Some roles and employers require one, many do not. Requirements vary by role, employer and region. Check the How to Become One section of the relevant Occupational Outlook Handbook profile and a sample of local postings for the specific role you want, rather than relying on general claims either way.