Sefism Switch into Tech Roadmap

What this roadmap is

Switch into tech is Sefism's plan for people moving into a tech career from somewhere else: a non-CS degree, another job, or years of learning on your own without a degree. It is not a crash course in coding. It is the strategy around the skills: how long a switch really takes, which first role makes sense for your background, how to pay for it without putting your family under pressure, what proof to build, how to tell your story and which doors to knock on.

What you will be able to do

• Explain honestly how long your switch will take, what it will cost and what could make it stall.
• Choose a first target role that uses your degree or experience, backed by conversations with people in the role and by real job postings.
• Run a weekly learning plan around work, study or family, and judge any bootcamp, certificate or degree before you pay for it.
• Show two or three pieces of proof built from problems in your old field, and tell your switch in one clear sentence.
• Pursue the routes that suit career changers: internal moves, apprenticeships, internships, freelance work and referrals.

Three starting points

When you add the roadmap you choose where you are starting from, and some stage copy changes to match:

• A non-CS degree (engineering, science, business or arts). Your degree is treated as an asset: maths, science, engineering, business or writing skills make some tech roles a much shorter jump.
• Another career. Years of work in another field are your edge. The roadmap pushes you towards roles where that experience counts, ideally at a company that builds software for your old industry, and adds a topic on moving internally at your current employer.
• Self-taught, no degree. The roadmap points you first at roles where employers hire on visible proof: frontend and web development, QA, IT and technical support, and data analytics. It also reminds you to check whether your target employers or countries filter on degrees.

Who it suits, and who should start elsewhere

It suits anyone who wants to move into tech without a CS background and wants to avoid the expensive mistakes: paying for a course in week one, quitting a job too early, or a year of tutorials with nothing built.

It is deliberately the plan, not the skills. Stage four tells you to add the Sefism skill roadmap for your target role and learn the skills there. Depending on the role you pick, that might be Frontend development, Data analytics, QA and test automation or UI/UX design. If you are not sure you want to code at all, Tech roles beyond coding covers product management, business analysis, technical writing and developer relations. If you are a CS student or graduate, University to job-ready and Your first tech job fit you better. For the applications themselves (resume polish, GitHub, a portfolio page), the roadmap sends you to Job search.

Prerequisites and realistic time

No prerequisites beyond the decision to switch. The roadmap adds up to about 133 hours across eight stages. At 5 hours a week that is about 29 weeks, at 8 hours a week about 20 weeks, and at 12 hours a week about 14 weeks. The first stage is a foundation stage: if you have already done that thinking, the plan lets you skim or skip it.

Those hours cover the switch strategy and your proof projects, not the whole skill set. Stage one asks you to estimate your timeline for about 600 hours of learning and projects, which is why the roadmap calls a year normal.

A student or recent graduate with 10 to 12 hours a week might do stages one to four in the first month, start the skill roadmap for their target role alongside, then spend most of the following months on stage five (proof), with stages six and seven running in parallel once the first project is live.

Someone working full time with 5 hours a week might give one evening and a weekend morning each week: stages one to four over the first two months, then a steady 3 hours of skill learning and 2 hours of project work, keeping income until there is proof and ideally an offer. Stage three insists on at least one rest day a week.

Stage by stage

1. An honest reality check (8 hours, foundation)

Before you spend money or quit anything: how long a switch really takes, what the entry-level market is like now, what a switch costs, why some switches stall, where a degree still matters, your real reason for switching, and first conversations with people in tech. You track one normal week to find the hours you can really study, list the money, lost income and time the switch will cost, and have at least two 15-minute conversations with people doing the work.

Milestone: a one-page reality note with your weekly hours and timeline, the full cost, where a degree matters for you, your reason in two sentences, and notes from at least two conversations.

2. A target role that fits your background (12 hours)

Tech has many doors besides general software engineering. You audit your transferable skills, map your background to roles, do a weekend taster project before committing, and count junior postings for two to four weeks to check real demand. The topics change with your starting point: using your degree, using your work experience, or roles that hire on proof.

Milestone: a target role note with one first role and one backup, the skills that support it, notes from a taster project, a month of junior posting counts, and the Sefism skill roadmap you will follow for it.

3. Money, risk and the people around you (4 hours)

Your runway, keeping income while you switch, expecting a pay reset, checkpoints and a plan B, family expectations, and a pace you can keep for a year. You set checkpoint dates at three, six and twelve months with evidence to review.

Milestone: a one-page money and risk plan, including junior pay for your target role compared with today and notes from a conversation with your family.

4. A learning plan that fits your life (6 hours)

Hours per week, honestly; one curriculum, not ten; free versus paid learning; bootcamps judged honestly; red flags such as income-share deals and job promises; degrees and online degrees; and a routine that beats tutorial hell. The rule is to learn free for at least a month before paying for anything, and never to sign an income-share or deferred tuition agreement without calculating the maximum repayment.

Milestone: a written learning plan with fixed weekly study slots, one chosen curriculum and the matching Sefism skill roadmap, a reasoned decision on anything paid, and the first two weeks of a learning log.

5. Proof without a CS degree (60 hours)

The longest stage. Proof over credentials: a project from your old field, scoping so you finish, a first open source contribution, writing and learning in public, certificates used sensibly, and turning a project into a case study. Build proof while you learn, not after, and use fake data rather than real client or employer records.

Milestone: two finished projects, at least one solving a problem from your old field, each with a one-page case study and a live link or report, plus one open source contribution or two public write-ups.

6. Telling your story (10 hours)

Your switch in one sentence, a resume for a career changer, reframing your past experience, a LinkedIn headline and About section that name the role, answering "why did you switch?" in under 30 seconds, the idea that you are not starting from zero, and telling your existing network. Never apologise for your background.

Milestone: the sentence, a one-page resume ordered for a career changer, an updated LinkedIn profile, a practised answer and a message sent to your network.

7. Getting in the door (25 hours)

Cold applications alone are the hardest route for a career changer. This stage covers apprenticeships and trainee roles, internships and graduate programmes for switchers, returnships after a career break (optional), freelance or volunteer work first, referrals and networking without awkwardness, meetups and communities, stepping-stone roles and the scams aimed at career changers. Career changers also get a topic on moving internally at their current employer.

Milestone: a doors list with at least ten concrete routes in, one freelance or volunteer project, three people who know your work, one or two communities you attend, and a scam check you apply to every offer.

8. Your first year after switching (8 hours)

Your first weeks as a switcher, handling impostor feelings, asking for help well, recording your wins in a brag document, using your background at work, treating your first job as a step rather than a destination, and keeping a smaller learning habit. Your first tech job goes deeper on the job itself.

Milestone: a two-week onboarding plan, a brag document with at least five entries, one way you have used your background at work, and three goals for the year with a review date.

Projects that fit a switcher

The roadmap suggests four projects from the Sefism FYP library:

• Replace a Spreadsheet Workflow From Your Previous Field With a Small Web App, the most memorable proof a switcher can show.
• Data Story From Your Previous Field Using Public Data, ideal for data and bridge roles.
• Small Business Weekly Report Automation with Monitoring, automating the kind of manual report many people leave behind.
• Job Application Tracker with a Keyword Gap View, a tool you use in your own search.

Stages also link picks such as freeCodeCamp, Course Report and iRelaunch.

How it works on Sefism

Everything on Sefism is free to learn from, and this roadmap is currently free to add as well. The public page at Switch into tech shows every stage open for every starting point, with its topics, milestones and recommended material.

Adding it to your dashboard costs no credits and does not use up your free first roadmap, so that stays available for another one. Once you add it, it stays yours. On your dashboard you can:

• tick stages off and track your progress, at a pace set by the hours you have each week
• keep the companion Switch into tech cheat sheet, which comes with the roadmap
• ask Tauseef a question about any stage, or book a 1:1 session if you want to talk your plan through

If you are new, create a free account first.

The companion cheat sheet

The Switch into tech cheat sheet follows the same eight chapters, with 56 short concepts such as runway, pay reset, bridge role, income-share agreement and warm referral, each with its common pitfall. Use it to revise a stage before a checkpoint or before you pay for anything.

Related on Sefism

• Can I get into tech without a computer science degree?
• Can I switch to software engineering at 30 with no degree?
• How do I move from a non-CS engineering degree into software?
• Is a bootcamp worth it in 2026?
• Should I accept a low-paying first job or internship in tech?
• Moving Into Tech From a Commerce Degree: Which Paths Actually Pay

FAQ

How long does it take to switch into tech? For people studying part time around a job, one to two years is common, and the roadmap treats a year as normal. The strategy stages here take about 133 hours; the skills for your target role come on top.

Can I get into tech without a CS degree? Yes, for many roles, especially those that hire on visible proof. The roadmap also tells you to check where a degree still matters: some large employers, government and bank roles, graduate programmes and many work visas abroad. Is a bootcamp worth it? Only after a month of free learning, and only after asking it the questions in stage four in writing: a full outcome report, who teaches, refund policy and total cost.