Tauseef FayyazA to Z
Glossary
Every concept in this sheet, plus the smaller terms it uses. Select a concept to open its card.
A
- A project from your old field
- A 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.
- Asking for help well
- Asking after a short, time-boxed attempt, with what you tried, what you expected and what happened.
B
- Background to role map
- Common, sensible pairings: electrical engineer to embedded or data, teacher to technical writing or developer education, accountant to data analytics, designer to frontend or UX, customer support to QA or support engineering.
- Bootcamp
- An intensive, usually paid training programme lasting weeks or months, often with a cohort, instructors and career support.
- Brag document
- A running private list of what you did, learned and helped with, with dates and links.
- Bridge role
- A 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 for banking software.
C
- Career changer headline
- A LinkedIn headline naming the target role and the edge your background gives, rather than your old title or "aspiring".
- Career changer resume
- A resume that puts a short summary and relevant projects near the top, then your previous experience rewritten to highlight transferable results.
- Case study write-up
- A 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.
- Certificates used sensibly
- Treating certificates as structured learning and a small signal, not as proof.
D
- Decision checkpoints
- Dates 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.
- Degrees and online degrees
- Formal qualifications, from full-time degrees to part-time online options such as tuition-free bachelor degrees and online masters that admit graduates of other fields.
- Demand check
- Counting current junior or entry-level postings for your target role in your city, region or remote market, and noting what they ask for.
- Domain advantage
- The edge you get from understanding an industry: its problems, vocabulary, regulations and users.
E
- Entry points into tech
- The roles people commonly enter tech through: frontend, backend or full stack developer, data analyst, QA or test engineer, support or solutions engineer, IT support, UX designer, technical writer and product roles.
F
- First open source contribution
- A small, accepted change to a public project: a documentation fix, a test, a translation or a labelled beginner issue.
- Free versus paid learning
- The choice between free curricula, which cover most beginner material, and paid courses, bootcamps or degrees, which add structure, deadlines, feedback or a credential.
- Freelance first
- Taking 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 full-time role.
I
- Impostor feelings
- The sense that you do not belong and will be found out, common among career changers surrounded by people with CS degrees.
- Income-share agreement
- A 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.
- Informational chat
- A short, low-pressure conversation with someone already doing the role you are considering, to learn what the work is really like.
- Internal transfer
- Moving into a tech or tech-adjacent role at the employer you already work for, often after taking on technical tasks in your current role.
- Internships for career changers
- Internships and graduate or trainee programmes that accept people from other degrees or careers, including remote and part-time ones.
K
- Keeping the learning habit
- Continuing a smaller, steady learning routine after you are hired, focused on what your job actually needs.
- Keeping your job while switching
- Learning and building on evenings, weekends or reduced hours while keeping your current income until you have skills, proof and ideally an offer.
L
- Learning in public
- Sharing what you learn and build as you go: short posts, write-ups of problems you solved, or notes on a project's decisions.
- Learning log
- A short dated note after each session: what you did, what confused you and what you will do next.
N
- Not starting from zero
- The idea that a career changer brings professional habits a new graduate lacks: reliability, communication, dealing with clients and managers, and domain knowledge.
O
- One curriculum at a time
- Choosing 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 adding others.
P
- Pay reset
- The chance that your first tech salary is lower than what you earn now, especially if you are experienced in your current field.
- Proof over credentials
- Evidence 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 of courses taken.
Q
- Questions to ask a bootcamp
- The 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 hours, refund policy and total cost.
R
- Reframed experience
- Bullets from your previous role rewritten to show outcomes that tech roles care about: data you analysed, processes you improved, tools you introduced, people you trained.
- Returnship
- A paid, time-limited programme for experienced people returning after a career break, with training and a real project, usually run by larger employers.
- Role taster project
- A 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, a short how-to guide.
- Runway
- How many months you could cover essential costs with savings and any other income if you earned nothing from work.
S
- Scoped project
- A 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.
- Stepping-stone role
- A 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.
- Sustainable pace
- A weekly study load you can keep for a year alongside work, family and rest, rather than a sprint you abandon after three weeks.
- Switch timeline
- The realistic time from starting to learn to a first paid tech role.
T
- Tech apprenticeship
- A paid role that combines work with structured training, often open to people without a degree or relevant experience.
- The "why switch?" answer
- A 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.
- The entry-level market
- The supply and demand for junior tech roles in your city or remote market.
- The family conversation
- An honest talk with the people affected by your switch about the time it takes, the money involved, the risk and how they can help.
- The full cost of a switch
- Everything 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 first salary.
- Training fee scams
- Fake job offers or "placement promised" schemes that ask you to pay for training, equipment, visas or certificates before you can start.
- Transferable skills
- Skills from your previous degree or work that tech roles also need: analysis, writing, teaching, handling customers, managing projects, working with numbers, debugging physical systems.
- Tutorial hell
- The loop of finishing one course or video series after another while feeling unable to build anything alone.
U
- Using your background at work
- Volunteering for work where your previous field helps: talking to users in that industry, reviewing requirements, spotting unrealistic assumptions.
W
- Warm referral
- An introduction or referral from someone who knows you or your work, earned through genuine contact over time rather than cold requests.
- Weekly hours budget
- The number of hours a week you can truly give to learning after work, family, travel and sleep, found by tracking a normal week.
- When a degree matters
- The situations where a degree is still required or strongly preferred: some large employers and government or bank roles, graduate programmes, many work visas abroad, and research or specialist roles.
- Why switches stall
- The common reasons people give up: no clear target role, jumping between courses, never building anything original, never talking to anyone in the industry, and quitting a job before savings or skills were ready.
Y
- Your first job is not forever
- Treating the first tech role as the place to gain one to two years of real experience, not the perfect final destination.
- Your first weeks as a switcher
- The 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.
- Your switch in one sentence
- A single sentence that connects where you came from, what you can do now and where you are going.