✅ Quiz 19 — Your Path Into Tech
Answer in your head or on paper, then open the fold to check. No grades, no timer — this is for you.
1. True or false: you need a computer science degree to work as a software engineer.
Show answer
**False.** Many working engineers have no CS degree — they're self-taught, bootcamp-trained, or degreed in something unrelated. Employers ultimately screen for whether you can do the work, and a portfolio of real projects is believable proof without a diploma.2. Also true or false: “you can go from zero to hired in 3 months.” What’s the honest timeline for most part-time learners?
Show answer
Also **false** — that's the other lie. For most people studying part-time (roughly 8–15 hours a week) around a job or family, zero to genuinely job-ready takes **12 to 24 months** of consistent effort. Long, but walkable — and free of expensive gates.3. A 45-year-old nurse asks if she’s “too old to start.” What does the lesson say — and what advantage does she have that a 22-year-old graduate doesn’t?
Show answer
Age is genuinely not the barrier people fear — career-changers in their 30s, 40s, and 50s enter tech constantly. Her advantage is **domain knowledge**: a nurse who codes understands hospital software better than any 22-year-old ever will. Companies build software *about* the world, so they need people who know the world. Her first career is an asset, not dead weight.4. Compare the four routes into tech in one honest line each.
Show answer
**CS degree:** deepest foundations, slowest and most expensive; opens research and some big-company doors most readily. **Bootcamp:** fast and structured, costs real money, and quality varies wildly — interrogate one before paying. **Self-taught:** free or cheap and fits around real life, but demands discipline and a community. **Apprenticeships / returnships:** rare but real — you learn while being *paid*, and people forget to search for them.5. Name three questions you should ask a bootcamp before handing over money.
Show answer
Any three of: What percentage of graduates work *in the field* within 6–12 months, and how do you define "employed"? Can I speak to three recent graduates you didn't hand-pick? Who actually teaches — working engineers or recent graduates of this same bootcamp? What happens if I fall behind, and what's the refund policy in writing? What are the exact conditions on the "job guarantee"?6. Your friend loves helping people, is endlessly patient, and hates the idea of coding all day. Name two tech roles that might suit her, and why “getting into tech” doesn’t require becoming a coder.
Show answer
**Support engineering** (helping stuck users — patience and people-reading are the job) and **technical writing** (making complicated things make sense — the teacher's superpower). Tech companies are full of vital roles that write little or no code: QA, project coordination, data analysis, product, design, developer marketing. For many career-changers these doors are closer *and* better-fitting — and the building is connected on the inside if she later wants to move.7. Why does the lesson say “a portfolio beats certificates”? Use the baker analogy.
Show answer
Certificates prove you *attended*; projects prove you can *build*. Hiring a junior baker, you'd rather taste three things they baked than read a pastry-school diploma. Three real, small, **finished** projects on your GitHub — with commit history and honest READMEs — beat ten certificates, because the hiring manager can taste them directly.8. List the five standard stages of a tech interview process, in order.
Show answer
**Recruiter screen** (does your story make sense?) → **technical screen** (first look at your technical thinking) → **take-home or live exercise** (how you actually work, including when stuck) → **onsite/panel** (depth, collaboration, behavioral stories) → **offer** (negotiable — check levels.fyi first).9. What are whiteboard/LeetCode interviews, and what’s the lesson’s honest take?
Show answer
Live algorithm-puzzle interviews used by some companies (especially large ones), commonly practiced on a site called LeetCode. Honestly: they resemble daily engineering work about as much as spelling bees resemble writing novels, many engineers dislike them, and many companies skip them — but they exist, and they're passable with unglamorous preparation: a few dozen practiced problems over a couple of months, after your fundamentals are solid, never instead of them.10. Recite the learning loop — and explain why “getting stuck” isn’t a sign of failure.
Show answer
**Build something slightly too hard → get stuck → search or ask → finish anyway → repeat.** Getting stuck isn't failure — it's the mechanism, like muscles that only grow when the weight is slightly too heavy. Each pass through the loop, "slightly too hard" moves up a notch. Every self-taught developer learned exactly this way.11. What’s the community etiquette, in three lines? And why does the lesson insist on finding a community at all?
Show answer
Etiquette: **search before asking** (your question is usually answered somewhere); **show what you tried** and the exact error when you do ask; **thank people and report back** what worked. Why a community matters: loneliness — not difficulty — is the main reason self-taught journeys stall.12. 🗣️ Explain it to a friend
A friend texts you: “I’m 38, I manage a restaurant, and I’m miserable. I saw an ad saying I could become a coder in 12 weeks for $15,000. Should I do it?”
In under a minute, jargon-free: give them the honest picture — the timeline, the bootcamp caution, the free alternatives, and one reason their restaurant experience actually helps.