Sefism Switch into Tech Cheat Sheet

What this cheat sheet is

The Switch into tech cheat sheet is a quick-revision book on the strategy of a career switch. It does not teach you to code. It holds the ideas you need to make good decisions while you do: how long a switch really takes, which first role fits your background, how to fund it, what counts as proof, how to tell your story and which doors are realistic. It has eight chapters and 56 concepts, each a short definition with why it matters and, for most, the mistake people make with it.

It is the companion to the Switch into tech roadmap and uses the same eight chapter titles as the roadmap's stages, so a concept you meet in a stage is one click away.

Who it is for

People moving into tech from another degree, another career or self-study. It comes in three editions that match the roadmap's starting points, each with its own summary and one extra rule of thumb:

• A non-CS degree: for graduates of engineering, science, business or arts, with the emphasis on choosing a role that uses your degree and getting in through internships, graduate programmes or projects.
• Another career: for working professionals who keep earning while they switch, with routes such as internal transfers. Its extra tip: ask your current employer about technical work before you look anywhere else.
• Self-taught, no degree: for learners without a degree, with roles that hire on proof and public work that stands in for a degree. Its extra tip: check whether your target employers or countries filter on degrees before you plan around proof alone.

All three editions have the same eight chapters and 56 concepts.

Chapter by chapter

1. An honest reality check

Seven concepts: the switch timeline (one to two years is common part time), the entry-level market, the full cost of a switch (including income and time given up), why switches stall, tutorial hell, when a degree still matters, and the informational chat. The pitfalls are the useful part here, such as trusting "job-ready in 12 weeks" adverts that assume full-time study and ignore the search.

2. A target role that fits your background

Seven concepts: the entry points into tech, transferable skills, the bridge role, a background-to-role map (accountant to data analytics, teacher to technical writing or developer education, designer to frontend or UX, customer support to QA), domain advantage, the role taster project and the demand check.

3. Money, risk and the people around you

Six concepts: runway, keeping your job while switching, the pay reset, decision checkpoints, the family conversation and a sustainable pace. A typical pitfall: planning 25 hours a week on top of a full-time job and caring duties, then feeling guilty when it collapses.

4. A learning plan that fits your life

Eight concepts: the weekly hours budget, one curriculum at a time, free versus paid learning, bootcamps, income-share agreements, the questions to ask a bootcamp before paying (full outcome report, what counts as a job, who teaches, refund policy, total cost), degrees and online degrees, and the learning log.

5. Proof without a CS degree

Seven concepts: proof over credentials, a project from your old field (with fake records, never real client data), the scoped project, a first open source contribution, learning in public, certificates used sensibly, and the one-page case study write-up.

6. Telling your story

Six concepts: your switch in one sentence, the career changer resume, reframed experience, a headline that names the target role rather than "aspiring", the "why switch?" answer and the idea that you are not starting from zero.

7. Getting in the door

Eight concepts: the internal transfer, tech apprenticeships, internships for career changers, returnships, freelance first, the warm referral, the stepping-stone role, and training fee scams that ask you to pay before you start.

8. Your first year after switching

Seven concepts: your first weeks as a switcher, impostor feelings, asking for help well, the brag document, using your background at work, why your first job is not forever, and keeping the learning habit without burning out.

Each chapter also links up to three resources from the Sefism library to go deeper, such as Course Report, Learn In Public, iRelaunch and Get Your Work Recognized: Write a Brag Document.

Rules of thumb inside

The sheet ends with tips worth keeping on a sticky note. A few of them:

• Try the work for free for a month before you pay for any course, bootcamp or degree.
• Pick one target role and one curriculum; change them only at a planned checkpoint.
• Your first projects should come from problems you know from your old field.
• Keep your income until you have skills and proof, not just motivation.
• Never pay an employer or recruiter to get a job.

A glossary collects the shorter terms alongside every concept.

How to use it with the roadmap

• After each stage, read the matching chapter and check you can explain each concept without notes.
• At every checkpoint you set in chapter three, reread chapters one to four before deciding to continue, adjust or pause.
• Before you pay for anything, reread chapter four.
• Before a conversation with a hiring manager or recruiter, revise chapter six so your one sentence and your "why switch" answer are fresh.
• When an offer looks too good, check it against the training fee scam concept in chapter seven.

How it works on Sefism

Everything on Sefism is free to learn from. The public page shows all eight chapter titles with the first chapters open. Keeping the full sheet in your member area uses credits, and if you follow the Switch into tech roadmap, the sheet comes with it. New members get starting credits and the first roadmap is free. If a concept does not fit your situation, ask Tauseef directly.

Related on Sefism

• Can I get into tech without a computer science degree?
• Should I do a CS degree, a bootcamp or teach myself to code?
• How do I get back into software engineering after a long career break?
• Job search cheat sheet and Your first tech job cheat sheet for the stages after you are in.

FAQ

Is this a coding cheat sheet? No. It covers the decisions around a switch. For the skills, use the cheat sheet that matches your target role, such as Frontend or Data analytics.

Which edition should I pick? The one that matches your starting point: a non-CS degree, another career, or self-taught with no degree. The chapters are the same; the framing and one tip change.

Can I use it without the roadmap? Yes. It works as a standalone checklist of the ideas that decide whether a switch succeeds, though the roadmap turns them into dated milestones.