How to Break Into Tech Without a Computer Science Degree
A practical route from a non-technical job into support, QA, web or design work — what employers check instead of a degree, and how long the switch takes.
By Daniel Ortiz · Sep 29, 2026 · 15 min read
You can get hired in tech without a computer science degree, but not in every role and not without evidence. Some occupations hire on demonstrated ability: the U.S. Bureau of Labor Statistics notes that education for web developers and digital designers ranges from a high school diploma to a bachelor's degree, and that candidates may not need specific credentials if they can show prior work or projects (BLS, 2025). Others, notably software development and QA, typically expect a bachelor's degree (BLS, 2025) — which means you compete on portfolio and referrals rather than on paper.
This guide covers which doors are open, what your current job already gives you, a twelve-month plan, and the money you should have set aside before you start. Requirements, training prices and hiring norms vary by employer and country, so treat every range here as something to verify locally.
Is it right for you? (checklist)
Answer each of these yes or no, honestly, before you spend anything.
- Can you protect 8–12 hours a week for study for a year, including the weeks when your current job is bad?
- Do you stay with a problem you cannot solve in the first ten minutes, or do you look for something else to do?
- Are you willing to be a beginner in public — asking obvious questions in a team channel, taking code review comments, being corrected by someone ten years younger?
- Can you take a lateral move or a pay cut for roughly the first 12–18 months?
- Will you accept an unglamorous first job — password resets, ticket queues, manual test scripts, content updates — rather than holding out for a developer title?
- Do you write clearly in short form? Tickets, incident notes and pull request descriptions are most of the written output in junior tech roles.
- Have you spoken to at least two people who currently do the job you are aiming at, rather than only reading about it?
How to read your answers. Mostly yes: start the plan below this month. A no on the study hours, the pay dip or the unglamorous first job is the one that sinks career changes — not a lack of maths. If any of those three is a no, keep your current job and pursue an internal transfer into a tech-adjacent team instead, where your existing salary and reputation travel with you.
A no on the debugging question is worth taking seriously. Support and engineering work is long stretches of narrowing down a fault with incomplete information. If that sounds like a bad day rather than an interesting one, the tech-adjacent roles — coordination, technical writing, training, procurement — will suit you better than a technical one.
What transfers (table)
Most of what gets you hired at the junior end is not code. It is the behaviour employers already pay you for.
| Skill from your old role | How it applies in tech |
|---|---|
| Retail or hospitality customer service | Help desk triage: calming an angry user, extracting the actual problem from a vague complaint, and closing the loop before the shift ends |
| Teaching, training or coaching | Writing documentation and runbooks, onboarding new hires, and explaining a system to people who will not read a manual |
| Admin, scheduling or dispatch | Project and release coordination: chasing dependencies, keeping a ticket board honest, and spotting the task nobody has owned |
| Bookkeeping, payroll or audit | Reconciliation habits map directly onto QA and data work — checking one source against another and refusing to sign off on a mismatch |
| Trades, maintenance or vehicle technician | Structured fault-finding, hardware handling, cabling and site work — the core of computer network support |
| Nursing, care or emergency services | Incident response: triaging by severity, escalating early, and writing a clean handover under time pressure |
| Sales or account management | Pre-sales, customer success and solutions roles, where technical fluency plus objection handling is rarer than either alone |
| Warehouse, logistics or manufacturing | Process mapping and automation: you already know which steps are wasteful, which is half of any internal tooling project |
The transfer only counts if you can evidence it. For each row you claim, write one sentence naming the situation, what you did and what changed — the volume of tickets you handled, the process you rewrote, the error rate you cut. Put those sentences at the top of your resume, above the training.
Roles to aim for (table)
Aim at roles where employers are used to hiring on certification and portfolio. Retraining times below assume roughly 10 hours a week of study; full-time study compresses them, shift work stretches them.
| Role | Entry requirement | Typical retraining time |
|---|---|---|
| Computer user support specialist (help desk) | BLS says workers typically complete some college courses, but candidates may qualify with a high school diploma plus relevant IT certifications (BLS, 2025) | 3–6 months to a first certification; the Google IT Support Professional Certificate is structured as 3 months at 10 hours a week, beginner level, no prior experience required (Google/Coursera) |
| Computer network support specialist | Typically an associate's degree (BLS, 2025) | 6–24 months, depending on whether you take an associate's programme or stack vendor certifications while working a help desk |
| Web developer | Education ranges from a high school diploma to a bachelor's degree, and specific credentials may be unnecessary if you can demonstrate ability through prior work or projects (BLS, 2025) | 9–18 months to a hireable portfolio of three to five real projects |
| Web and digital interface designer | Same range as above — high school diploma to bachelor's, with portfolio able to substitute (BLS, 2025) | 6–15 months, faster if you already have design, marketing or content experience |
| Software QA analyst and tester | Typically a bachelor's degree (BLS, 2025), so expect degree filters; manual testing and support-to-QA moves are the realistic routes in | 6–12 months, usually entered sideways from support rather than directly |
On pay and outlook, use the published data rather than anyone's promises. BLS reports median annual wages of $61,860 for computer user support specialists and $76,220 for computer network support specialists (May 2025); $92,650 for web developers and $104,000 for web and digital interface designers (May 2025); $104,300 for software QA analysts and testers and $135,980 for software developers (May 2025); and $100,390 for computer programmers (2025). Medians are the middle of the whole occupation, not a starting salary — your first job will sit below them.
Direction of travel matters too. BLS projects employment of web developers and digital designers to grow 5 percent from 2025 to 2035, with about 13,600 openings a year on average (BLS, 2025), and software developers, QA analysts and testers to grow 10 percent over the same period (BLS, 2025). Computer support specialist employment is projected to decline 3 percent from 2025 to 2035, with about 48,700 openings a year, all expected to come from replacing workers who transfer or leave the labour force (BLS, 2025). Support is still the widest door, but plan to move through it rather than settle in it. Check the BLS Occupational Outlook Handbook for the current figures, and your own national statistics agency if you are outside the United States.
The plan (timeline)
Months 0–3 — test whether you like the work, then pick one lane
- Complete one beginner course end to end before paying for anything large — for example the Google IT Support Professional Certificate, structured as 3 months at 10 hours a week with no prior experience required (Google/Coursera). Finishing something is the test, not enjoying week one.
- Choose a single lane — support, web development, design, or QA — and write it on paper. Switching lanes at month eight is the most common reason these transitions take two years.
- Message two people doing your target job and ask for 20 minutes: what they did last Tuesday, what they wish they had learned first, which certification their employer actually asks for.
- Collect 20 real job ads for that role in your area and list every tool and certification named. That list, not a curriculum, is your syllabus.
- Book study time in your calendar as fixed appointments — two weekday evenings and one weekend morning — and tell whoever you live with.
- Ask your current manager whether you can take on the team's tech-adjacent work: the ticketing system, the reporting spreadsheet, the new device rollout. Internal evidence is worth more than a course certificate.
Months 3–6 — build evidence someone can inspect
- Sit the certification your job-ad list named most often. The Google IT Support Professional Certificate also prepares learners for the CompTIA A+ exams, awarding a dual credential (Google/Coursera), which covers the common help desk requirement.
- Build a home lab from an old laptop: install a hypervisor, run two virtual machines, break and repair them, and document each fix in a short write-up.
- Ship two projects for real users — a site for a local club, an internal tool for your current team, a test plan for an open-source app. Real users create the bug reports and constraints that make a portfolio credible.
- Write a one-page case study for each project: the problem, what you built, what broke, what you would do differently. Hiring managers read these; they rarely read code.
- Rewrite your resume skills-first: tools and certifications at the top, then projects, then employment history described in tech terms.
- Attend one local user group or online community every month and answer beginner questions there. Answering is how you find out what you do not know.
Months 6–12 — apply, convert, and keep learning
- Set a weekly application target — eight to ten tailored applications, each one referencing a named tool from the ad — and track them in a spreadsheet with columns for date, role, source, contact and outcome.
- Ask your two contacts to refer you internally rather than applying cold, and tell them which requisition number you want.
- Practise troubleshooting out loud with a friend: say what you are checking, why, and what you would escalate. Support and QA interviews test narration as much as knowledge.
- Accept contract, temporary, night shift or internal-transfer work if it is offered. The first tech role is a qualification, not a destination.
- Review the tracker every 30 applications. No first-round interviews after roughly 40 means the artefact is wrong — resume, portfolio, or target role — and sending more of the same will not fix it.
- Book a monthly check-in with someone already in the role to review what you are learning next: a specialism, a second certification, or a move from support into QA or infrastructure.
What goes wrong. Three failures repeat. Collecting courses instead of finishing projects, because courses feel like progress and projects feel like failure. Applying only to the job title you want rather than the one adjacent to it, which leaves you unemployed while a support role would have put you inside the industry. And going quiet for six months of study, so that when you finally apply you have no contacts to refer you. Fix all three by shipping small things publicly the whole way through.
The money side (list)
Costs vary enormously by country, provider and how fast you finish, so price everything yourself before committing. The bands below describe what drives the spread rather than quoting prices that will be out of date.
- Free tier. Public library access, vendor documentation, official language tutorials and community forums. Cost is your time only. Most people can reach the point of knowing whether they like the work without paying anything.
- Subscription certificate platforms. Charged monthly, so your total cost depends on your pace: finishing a programme built for 3 months at 10 hours a week (Google/Coursera's stated structure for its IT Support Professional Certificate) costs a third of what it costs if you take nine months. Check the provider's current monthly price and whether financial aid is offered.
- Certification exam fees. Priced per exam, and the Google programme's dual credential route involves the CompTIA A+ exams (Google/Coursera), which are sat separately from the coursework. Budget for one retake per exam and check the awarding body's own site for current fees and voucher bundles.
- Community or technical college. Priced per credit hour, with residency and public funding driving most of the difference. Relevant if you are targeting computer network support, where BLS reports an associate's degree is the typical entry requirement (BLS, 2025). Ask the admissions office about credit for prior learning.
- Bootcamps. The widest range of all, from part-time evening courses to full-time immersive programmes, sometimes with deferred or income-share payment. Ask for the refund policy in writing, and ask how the provider defines and verifies an employment outcome before you believe any outcome claim.
- Hidden costs people forget. A machine capable of running virtual machines, a second monitor, exam retakes, travel to meetups and interviews, and lost overtime or shift premiums while you study.
The pay dip. Expect one. Your first tech role is priced as a junior role regardless of your previous seniority. Use the BLS medians as the ceiling you are working toward, not the offer you should expect: $61,860 for computer user support specialists and $76,220 for computer network support specialists (BLS, May 2025), $92,650 for web developers (BLS, May 2025). If you are coming from a supervisory job in another field, the dip can last until your second tech role, typically 18–30 months in. Check the BLS Occupational Outlook Handbook and live local job ads for the range where you actually live.
The buffer. Hold 3–6 months of essential spending in cash before you make any change, and 6–9 months if you are the only earner, if you plan to quit outright, or if your target role is one where BLS projects declining employment, such as computer support specialists, down 3 percent from 2025 to 2035 (BLS, 2025). Keep training costs outside that buffer — course fees should come from a separate pot, not from the money that pays your rent during a long job search. Write the three numbers down before you enrol: [$X] total course and exam cost, [$Y] monthly essential spend, [$Z] months of cover.
The honest downside. Retraining costs money and time with no guaranteed job at the end. Provider outcome claims are self-reported: Google/Coursera states that 75% of certificate graduates report a positive career outcome, such as a new job, promotion or raise, within six months of completing the IT Support Professional Certificate — that is the provider's own reported figure for its own learners, not an independent audit, and it counts raises in existing jobs alongside new hires. Some employers still filter on degrees, particularly for software developer and QA roles, where BLS reports a bachelor's degree is typically needed (BLS, 2025). The realistic route past that filter is a referral and a portfolio, which takes longer than a course does.
Frequently asked questions
I'm in my forties or fifties. Is age going to stop me?
Age changes your strategy, not your eligibility. Employers hiring juniors are buying reliability, communication and troubleshooting temperament, all of which you have more of than a graduate. What works against you is presenting as a career-long expert applying to a junior role, so lead with the technical evidence — certification, home lab, two shipped projects — and let the twenty years of employment history sit below it as proof you show up and finish things. Referrals matter more than applications at every age and matter most here, so spend your time on the two contacts rather than the job boards. Employment discrimination rules differ by country and this guide is not legal advice; if you think you have encountered discrimination, take advice locally.
Do I need to go back and get a computer science degree?
Not for every role. BLS reports that education for web developers and digital designers ranges from a high school diploma to a bachelor's degree, and that candidates may not need specific credentials if they can demonstrate ability through prior work or projects (BLS, 2025). For computer user support, BLS says candidates may qualify with a high school diploma plus relevant IT certifications (BLS, 2025), and network support typically calls for an associate's degree (BLS, 2025). Software developers, QA analysts and testers typically need a bachelor's degree (BLS, 2025), so those roles are usually reached sideways — from support or manual testing — rather than straight from a course. A degree in any subject already clears many HR filters; a second one is rarely the fastest route.
How do I explain the career change without sounding like I'm running away from something?
Give one sentence on what you did, one on what you built, and one on why this role specifically. Keep it under thirty seconds and make the bridge concrete. For example: "I spent [X years] in [old field], where I [specific achievement, e.g. ran the ticket queue for a 40-person site]. I finished [certification] in [month], and built [project] for [real user], which is where I learned [specific tool]. I'm applying here because your ad names [tool from the ad], which is what I've been working in." Never open with what was wrong with the old job. Interviewers hear the complaint, not the reason.
Will a certificate or bootcamp actually get me hired?
No training provider can promise a job, and you should distrust any that does. A certification gets you past keyword screening and proves you can finish something; the portfolio and the referral get you the interview. Treat outcome claims carefully — for instance, Google/Coursera reports that 75% of graduates report a positive career outcome, such as a new job, promotion or raise, within six months of completing its IT Support Professional Certificate, which is the provider's own reported figure and includes people who stayed with their existing employer. Ask any provider how they define an outcome, who they count, and who verifies it.
Is it faster to move internally at my current employer?
Usually, yes. An internal move keeps your salary, your reputation and your knowledge of the business, and hiring managers take a known colleague over an unknown junior. Start by asking your manager for the tech-adjacent work on your own team — the ticketing system, the reporting, the device rollout — then ask the IT or engineering lead for a shadowing day and what they would need to see before they would consider you. Internal transitions often run six to nine months rather than twelve to eighteen, because you are proving yourself on the job instead of in a portfolio. The trade-off is that you are limited to the roles your employer actually has.
Sources
- U.S. Bureau of Labor Statistics — Web Developers and Digital Designers : Occupational Outlook Handbook (2025-05)
- U.S. Bureau of Labor Statistics — Computer Support Specialists : Occupational Outlook Handbook (2025)
- U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers : Occupational Outlook Handbook (2025)
- Google / Coursera — Google IT Support Professional Certificate
