AIQ
AIQ
Part of the AI Career Paths lesson guide. Teaching a different grade? 🌈 Explorer (5–7) · 🔧 Builder (8–10) · ⚡ Architect (15–18)
Read the app's hook line and let the comparison sit for a moment before moving on:
"AI skills are becoming essential — like knowing how to use a computer was for your parents. Let's explore careers that combine AI with your passions."
Open with a direct question: "Your parents' generation had to learn to use computers even if their job wasn't 'computers' — think typing, email, spreadsheets. What's one job you know of where that was true, where computer skills became mandatory even though the job itself wasn't tech?" Take a few answers (accounting, teaching, retail management, and journalism are all good real examples if students get stuck). Then pivot: "Today's lesson is arguing the same thing is about to happen with AI — not that everyone becomes an AI engineer, but that AI literacy becomes as basic as knowing how to use a computer, in almost every job." Ask students to hold that claim loosely and test it against the twelve careers you're about to cover.
Push a little further before opening the app: "If that comparison holds, what happened to the specific job title 'computer operator' — the person whose whole job was literally operating a computer for a company, back when that was a rare and specialized skill?" (It's now essentially obsolete as a distinct role, because the skill became so universal it stopped being a separate job.) Ask students to keep that in the back of their mind as a possible parallel for today's most technical AI job titles — not as a scary prediction, but as a genuine open question worth testing against the evidence in the lesson.
Go through the lesson's three scenes, but push one level deeper than the basic job descriptions — this age band should leave able to explain why each career exists and what specifically makes it valuable, not just its title.
Scene 1 — Technical Paths 💻: These are the roles that build AI systems directly. An ML engineer ($150K+ average, per the app's figures) needs Python, math, and curiosity to build and train models — this is the closest thing to "traditional programmer" on the list, but it's still a small slice of all AI-adjacent work. A data scientist ($130K+) needs statistics and storytelling as much as programming, because finding a pattern in data is worthless if you can't explain what it means to someone who has to act on it. AI safety is worth spending real time on: it's explicitly framed here as "a GROWING field" because deploying powerful AI systems without safety research poses existential and practical risks — practical risks meaning bias, errors, and unintended harmful behavior in systems already in use today, and existential risks referring to the more speculative, longer-term concern some researchers raise about very capable future systems behaving in ways their creators didn't intend or can't control. Be honest that these two categories of concern are not equally certain — practical risks are documented and happening now; existential risk is a genuine but actively debated area of research, not a settled prediction. A robotics engineer merges AI with physical hardware — navigation, manipulation, and learning in the real world, which is a harder problem than it looks because the physical world doesn't behave as cleanly as training data.
Scene 2 — Creative + Social 🎨: This scene is where the "T-shaped professional" idea becomes concrete. AI + design shapes how humans actually interact with AI products — a genuinely technical-adjacent skill, since a badly designed AI interface can make an accurate system feel untrustworthy, or a flawed one feel convincing. AI policy requires understanding both the technology well enough to know what's actually possible and the societal impact well enough to write rules that work in practice — a policy written by someone who doesn't understand the technology, or by someone who understands only the technology and nothing about how people are affected, tends to fail. AI journalism and AI education both require translating technical material accurately for a non-technical audience — a skill that is not lesser than the technical skill itself, since bad AI reporting or bad AI teaching (misinformation, hype, or fear) shapes public understanding at scale.
Scene 3 — Every Field + AI 🌍: Use this scene to introduce the T-shaped professional concept explicitly: broad AI literacy (the top of the T) combined with deep expertise in one specific domain (the vertical stroke). A doctor who understands AI-assisted diagnosis, a climate scientist who can apply AI modeling, a music producer fluent in AI-assisted composition, and a sports analyst who can build AI-driven performance models are all T-shaped professionals — none of them primarily "AI people," but all of them meaningfully better at their actual job because of AI literacy layered on top of deep domain expertise.
If time allows, run the app's sorting activity and use it to sharpen the isAI distinction: ML model training, data analysis AI, AI-assisted design, and AI safety research sort as "AI," while policy writing, teaching kids, journalism writing, and playing sports sort as "not AI" — even though AI tools increasingly touch every one of those "not AI" tasks. The distinction the app is drawing is between the underlying task and the tools used to do it, which is worth naming explicitly.
Have students challenge this classification: is it possible for a "not AI" task to become an "AI" task over time, as tools improve? Journalism is a good case study — automated systems already draft simple, formulaic stories (routine financial earnings reports, basic sports recaps) from structured data with little human involvement, while investigative journalism, interviewing, and building a source's trust remain firmly human tasks. This is a good moment to reinforce that "isAI: true/false" isn't a permanent property of a job title, it's closer to a snapshot of where the line currently sits — and that line moves.
Close with: "AI literacy is becoming table stakes, the way computer literacy did for your parents' generation — but the careers that will matter most for you personally are the ones where you combine that literacy with something you already care about. The T-shape isn't optional anymore; the only real choice left is which domain forms your vertical stroke."
Extension activity — Portfolio Brainstorm: Have students individually sketch a one-paragraph pitch for a small AI-adjacent project connected to a personal interest — a sports fan might propose an app idea that predicts game outcomes from public stats, a music student might propose experimenting with an AI music tool and writing up what worked and what didn't, an aspiring writer might propose fact-checking an AI-generated article against real sources. The pitch doesn't need to be built — the goal is practicing the "portfolio thinking" the quiz just covered: what would you build, why does it combine AI with something you care about, and what would it prove about your judgment, not just your technical skill? Have a few students share their pitch aloud. This extends the 5–15 minute core lesson into a full period and gives students a concrete, personal answer to "what's my T-shape" rather than an abstract one.
If you have a full class period rather than a single sitting, extend this into a two-day exercise: day one is the pitch (as above), and day two has each student spend 15–20 minutes doing the smallest possible real version of it — actually trying the AI music tool for ten minutes and jotting down three observations, or actually fact-checking one real AI-generated claim against two sources. The point isn't a polished output; it's the difference between describing a project idea and having done even a tiny piece of it, which is exactly the gap between a resume line and a portfolio entry.