Switch into tech cheat sheet (A non-CS degree)

1. 1An honest reality checkWhat a switch really takes in time, money and effort, what the entry-level market looks like now, and why some switches stall.7 concepts

   1. 1Switch timelineThe realistic time from starting to learn to a first paid tech role.
   2. 2The entry-level marketThe supply and demand for junior tech roles in your city or remote market.
   3. 3The full cost of a switchEverything a switch costs: course fees, a laptop and internet, exam fees, and the biggest one, the income and time you give up while learning or taking a lower…
   4. 4Why switches stallThe common reasons people give up: no clear target role, jumping between courses, never building anything original, never talking to anyone in the industry, and…
   5. 5Tutorial hellThe loop of finishing one course or video series after another while feeling unable to build anything alone.
   6. 6When a degree mattersThe situations where a degree is still required or strongly preferred: some large employers and government or bank roles, graduate programmes, many work visas…
   7. 7Informational chatA short, low-pressure conversation with someone already doing the role you are considering, to learn what the work is really like.

   7 in this chapterOpen this chapter
2. 2A target role that fits your backgroundTech has many entry points beyond general software engineering. The best first target uses what you already know.7 concepts

   1. 1Entry points into techThe roles people commonly enter tech through: frontend, backend or full stack developer, data analyst, QA or test engineer, support or solutions engineer, IT…
   2. 2Transferable skillsSkills from your previous degree or work that tech roles also need: analysis, writing, teaching, handling customers, managing projects, working with numbers…
   3. 3Bridge roleA role that mixes your old domain with a tech skill, such as a finance data analyst, an edtech content engineer, a health informatics analyst or a QA engineer…
   4. 4Background to role mapCommon, sensible pairings: electrical engineer to embedded or data, teacher to technical writing or developer education, accountant to data analytics, designer…
   5. 5Domain advantageThe edge you get from understanding an industry: its problems, vocabulary, regulations and users.
   6. 6Role taster projectA small project, done in a weekend or two, that gives you a feel for a role before committing: a tiny web page, a spreadsheet analysis, a test plan for an app…
   7. 7Demand checkCounting current junior or entry-level postings for your target role in your city, region or remote market, and noting what they ask for.

   7 in this chapterOpen this chapter
3. 3Money, risk and the people around youHow to fund a switch without betting everything on it: runway, keeping income, a possible pay reset and honest conversations at home.6 concepts

   1. 1RunwayHow many months you could cover essential costs with savings and any other income if you earned nothing from work.
   2. 2Keeping your job while switchingLearning and building on evenings, weekends or reduced hours while keeping your current income until you have skills, proof and ideally an offer.
   3. 3Pay resetThe chance that your first tech salary is lower than what you earn now, especially if you are experienced in your current field.
   4. 4Decision checkpointsDates set in advance when you review progress honestly and decide whether to continue, adjust the target role or pause, based on evidence rather than mood.
   5. 5The family conversationAn honest talk with the people affected by your switch about the time it takes, the money involved, the risk and how they can help.
   6. 6Sustainable paceA weekly study load you can keep for a year alongside work, family and rest, rather than a sprint you abandon after three weeks.

   6 in this chapterOpen this chapter
4. 4A learning plan that fits your lifeHow to choose one path, what to pay for and what not to, and how to judge bootcamps and degrees before you spend money.8 concepts

   1. 1Weekly hours budgetThe number of hours a week you can truly give to learning after work, family, travel and sleep, found by tracking a normal week.
   2. 2One curriculum at a timeChoosing one structured, well-known path for your target role, such as The Odin Project, freeCodeCamp, CS50 or a data analytics course, and finishing it before…
   3. 3Free versus paid learningThe choice between free curricula, which cover most beginner material, and paid courses, bootcamps or degrees, which add structure, deadlines, feedback or a…
   4. 4BootcampAn intensive, usually paid training programme lasting weeks or months, often with a cohort, instructors and career support.
   5. 5Income-share agreementA deal where you pay nothing upfront but owe a share of your future income for a period once you earn above a threshold, up to a cap.
   6. 6Questions to ask a bootcampThe checks before you pay: full outcome report with starters and finishers, what counts as a job, recent graduates you find yourself, who teaches, live help…
   7. 7Degrees and online degreesFormal qualifications, from full-time degrees to part-time online options such as tuition-free bachelor degrees and online masters that admit graduates of other…
   8. 8Learning logA short dated note after each session: what you did, what confused you and what you will do next.

   8 in this chapterOpen this chapter
5. 5Proof without a CS degreeProjects, contributions and writing that a stranger can check, built to use what you already know.7 concepts

   1. 1Proof over credentialsEvidence of skill that anyone can open and check, such as a deployed project, a data report, a merged pull request or a written case study, rather than a list…
   2. 2A project from your old fieldA project that solves a real problem from your previous degree or job: a tool, an automation, an analysis or a test plan for software used in that field.
   3. 3Scoped projectA project small enough to finish in a few weeks at your weekly hours, with a clear list of what it will and will not do.
   4. 4First open source contributionA small, accepted change to a public project: a documentation fix, a test, a translation or a labelled beginner issue.
   5. 5Learning in publicSharing what you learn and build as you go: short posts, write-ups of problems you solved, or notes on a project's decisions.
   6. 6Certificates used sensiblyTreating certificates as structured learning and a small signal, not as proof.
   7. 7Case study write-upA one-page account of a project: the problem, who it was for, what you built, decisions and trade-offs, results and what you would change.

   7 in this chapterOpen this chapter
6. 6Telling your storyHow to explain your switch in a way that makes your past an asset: one sentence, a career changer resume and a profile that matches.6 concepts

   1. 1Your switch in one sentenceA single sentence that connects where you came from, what you can do now and where you are going.
   2. 2Career changer resumeA resume that puts a short summary and relevant projects near the top, then your previous experience rewritten to highlight transferable results.
   3. 3Reframed experienceBullets from your previous role rewritten to show outcomes that tech roles care about: data you analysed, processes you improved, tools you introduced, people…
   4. 4Career changer headlineA LinkedIn headline naming the target role and the edge your background gives, rather than your old title or "aspiring".
   5. 5The "why switch?" answerA short, honest answer to why you are moving into tech: a moment or problem that pulled you in, what you did about it, and why this role.
   6. 6Not starting from zeroThe idea that a career changer brings professional habits a new graduate lacks: reliability, communication, dealing with clients and managers, and domain…

   6 in this chapterOpen this chapter
7. 7Getting in the doorThe routes that work for career changers beyond cold applications: internal moves, apprenticeships, internships, returnships, freelance work and referrals.8 concepts

   1. 1Internal transferMoving into a tech or tech-adjacent role at the employer you already work for, often after taking on technical tasks in your current role.
   2. 2Tech apprenticeshipA paid role that combines work with structured training, often open to people without a degree or relevant experience.
   3. 3Internships for career changersInternships and graduate or trainee programmes that accept people from other degrees or careers, including remote and part-time ones.
   4. 4ReturnshipA paid, time-limited programme for experienced people returning after a career break, with training and a real project, usually run by larger employers.
   5. 5Freelance firstTaking small paid or volunteer projects for real clients, such as a local business website, a nonprofit dashboard or automation for a former colleague, before a…
   6. 6Warm referralAn introduction or referral from someone who knows you or your work, earned through genuine contact over time rather than cold requests.
   7. 7Stepping-stone roleA job that is not your final target but gets you inside tech, such as IT support, QA, technical support or a data entry role with analysis duties.
   8. 8Training fee scamsFake job offers or "placement promised" schemes that ask you to pay for training, equipment, visas or certificates before you can start.

   8 in this chapterOpen this chapter
8. 8Your first year after switchingHow to settle into a first tech role as someone who came from elsewhere, and turn your background into an advantage.7 concepts

   1. 1Your first weeks as a switcherThe early period when you learn the codebase or tools, the team's ways of working and who to ask, while colleagues learn what you bring.
   2. 2Impostor feelingsThe sense that you do not belong and will be found out, common among career changers surrounded by people with CS degrees.
   3. 3Asking for help wellAsking after a short, time-boxed attempt, with what you tried, what you expected and what happened.
   4. 4Brag documentA running private list of what you did, learned and helped with, with dates and links.
   5. 5Using your background at workVolunteering for work where your previous field helps: talking to users in that industry, reviewing requirements, spotting unrealistic assumptions.
   6. 6Your first job is not foreverTreating the first tech role as the place to gain one to two years of real experience, not the perfect final destination.
   7. 7Keeping the learning habitContinuing a smaller, steady learning routine after you are hired, focused on what your job actually needs.

   7 in this chapterOpen this chapter
9. 9Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.157 terms

From another field or no degree.