Timing: 30 seconds. Open by acknowledging that "getting into tech" can feel mysterious in high school. Promise a practical map you can start on now, not a guaranteed shortcut. The three verbs on this slide are the through-line for the entire talk.

Timing: 20 seconds. A quick "scan to follow along" moment. Tell students they can grab the slides now and revisit every link and resource afterward - no need to write anything down.

Timing: 60 seconds. This is a section transition and a decision point. Stress that "software engineering" is only one path. Ask students to notice which work sounds fun to try this month, not which title sounds impressive. A backup keeps you flexible without meaning "anything in tech."

Timing: 75 seconds. Students often think they have "no experience." Reframe: the things they already do build real strengths. A game speedrun is persistence and system learning; a group project is collaboration and deadlines. Keep it specific and true, then connect it to tech work.

Timing: 45 seconds. This is the heart of the talk: you learn by making things. Stress that "project" can be tiny and still count - a Scratch game, a one-page site, a robot subsystem. The goal is small and finished, not big and unfinished, so you have something to show and talk about later.

Timing: 75 seconds. Discourage endless tutorials and giant "someday" projects. "Finished" can be tiny: a Scratch or MakeCode game, a one-page website, a small script, or a robot subsystem. The next loop should add one new challenge, not restart from zero.

Timing: 60 seconds. Courses teach a language but skip the workflow around it. A little comfort with the terminal, an editor, Git/GitHub, and reading errors makes projects easier to finish - and gives great stories about debugging and fixing mistakes. AI tools help here too, but they don't replace understanding.

Timing: 75 seconds. Credibility comes from making a project easy to understand and try - not from how big it is. A reviewer should get what it does, run or watch it, and see how you think. Not every project needs everything: pick a demo, a screenshot, or a link that fits what you built.

Timing: 75 seconds. There are excellent free, beginner-friendly places to learn - no paid course required. Scratch and MakeCode make the first project fun; Experience CS, freeCodeCamp, Microsoft Learn, and GitHub Skills go deeper. Point out that the languages they use (Python, C#, JavaScript) are built in the open on GitHub.

Timing: 75 seconds. Acknowledge AI is a huge, fast-moving deal that shows up everywhere students already are. The skill isn't just "using AI" - it's using it well: knowing what it's good at (explaining, drafting, brainstorming), where it breaks down (it makes things up, struggles with math, can't be trusted with private info), and treating it as a playground to try ideas quickly. Curiosity plus a healthy dose of "verify it" is the mindset.

Timing: 75 seconds. There are excellent free ways to learn AI - no expensive course needed. Elements of AI and Microsoft's Generative AI for Beginners are gentle on-ramps; Kaggle and Hugging Face are hands-on. Highlight local models: Ollama and LM Studio let students run real LLMs on their own machine - free, private, and offline, which is a great safe sandbox to experiment. Note age requirements on hosted chat tools and getting a parent's OK.

Timing: 60 seconds. Demystify open source: it's not just expert programmers. Projects need docs, tests, typo fixes, and translations. First Contributions is a repo built just for practicing your first pull request. Even a tiny merged change is real, public evidence and a great story.

Timing: 75 seconds. Learning in public means sharing work-in-progress: a short post, a README, a demo video, or a thread about a bug you fixed. You don't need to be an expert - you help the person one step behind you. Add a safety note: share only public, school-appropriate work, keep personal details private, and follow age rules on platforms (get a parent's OK).

Timing: 60 seconds. Most people forget their own wins within weeks. A simple running note - even in a phone app - captures what you did while it's fresh. It becomes the raw material for applications, resumes, and interview stories, and rereading it is a real antidote to feeling like you haven't done anything.

Timing: 75 seconds. Section transition from projects to people. A useful community is built through repeated, friendly participation - not one-off requests. Point out how many free options exist: school clubs, robotics teams, hackathons, and online communities. You can help by welcoming others, sharing a resource, or reporting a clear bug - not only by writing code. Mention basic online safety: keep personal info private and loop in a trusted adult.

Timing: 75 seconds. Encourage students to find one recurring thing - a school club, a robotics team, or a student hackathon - and return to it. Familiarity is what turns into mentors and opportunities. Include a safety note: attend in-person events with a friend or trusted adult and keep personal details private online.

Timing: 60 seconds. A specific, short message is easy to answer - much better than "can you mentor me?" Model good follow-up: thank them and share what you tried. Reinforce safety: use public/official channels, keep an adult in the loop, and never share private details with people online.

Timing: 60 seconds. This is a low-pressure, curious conversation - not a job request. Prepared questions show respect and surface what actually matters. Great first people: teachers, counselors, family friends in tech, or older students and alumni. Following up turns one chat into a relationship.

Timing: 75 seconds. Reframe the "hidden job market" for students: many opportunities (programs, contests, internships, first jobs) spread by word of mouth through teachers, clubs, and friends. The goal isn't to collect contacts - it's to be someone people think of because they've seen your work and know what you want.

Timing: 45 seconds. Each relationship does something different: peers for practice and momentum, mentors for perspective, teachers/counselors for access to programs, and slightly-older students for relatable, recent advice. Peers and one supportive adult are the most accessible starting point.

Timing: 45 seconds. Nobody owes anyone their time, and cold-asking "be my mentor" usually misses how trust works. Reliable follow-through, specific questions, and helping others give people a reason to invest in you. This is true for teachers, mentors, and teammates alike.

Timing: 75 seconds. Walk left to right. You do not need to finish everything before starting; each step feeds the next. A little learning lets you build; building gives you something to share; sharing helps you meet people; those people and projects are how internships, programs, and first jobs actually find you.

Timing: 75 seconds. Applies to internships, summer programs, and first jobs. Separate real rules (age, grade, eligibility) from wish-list items. Encourage a quick check: "Do I get the main thing, can I show something related, and can I learn the rest?" Applying is asking to be considered, not claiming a perfect fit.

Timing: 75 seconds. A student resume is not an autobiography. Its job is to make your real activities - projects, clubs, a class you loved - easy to see. "New" is normal; one finished project beats a long list of buzzwords.

Timing: 90 seconds. Being able to talk about your work is a learnable skill - for a club, program, scholarship, or first job. Practice out loud with a friend or by recording yourself. STAR keeps a story clear; have one ready about a hard thing, a mistake, and teamwork. Asking good questions makes it a two-way conversation, and a "no" is information about fit, not a verdict on your worth.

Timing: 60 seconds. Now that students have explored, built, and met people, they have a real story to tell: spark, explored, made, next. Keep it short and point to one real thing they built - that "made" piece is what makes the story land for a club, teacher, mentor, or program.

Timing: 90 seconds. Two common technical formats. For a coding challenge, the biggest mistake is going silent - narrate: restate, plan, start simple, test, improve. For a "how would you build it?" chat, students aren't expected to design something huge: ask questions, sketch a few parts, name one tradeoff, and it's fine to say "I'd look that up." Emphasize communication over memorizing tricky algorithms. Practice sites like LeetCode and Advent of Code are on the resources slide.

Timing: 75 seconds. Students will use AI - teach them to use it well: as a tutor and helper, not a copy-paste machine. They should understand what it produces and be able to explain it. Add an academic-honesty note: follow the teacher's and school's rules about AI on assignments. Skills like problem framing still matter most.

Timing: 75 seconds. Students face choices too: which class, club, camp, program, or internship. The skill is the same - look past the label at what you'll learn, who's involved, and whether it fits your life. Encourage them to ask questions and talk it over with a trusted adult before committing.

Timing: 90 seconds. Present this as an experiment, not a test - a few hours a week around school. The sequence matters more than the hours: choose, learn, build, then share and connect. Suggest a rough rhythm like two short learning sessions, one build session, and some community time. At the end of each week, keep, change, or drop parts based on how it went - homework and rest always come first.

Timing: 60 seconds. Reframe rejection as normal and useful - not a verdict. Didn't make the robotics team, the program, the internship? So has everyone. Reflect, adjust one thing, and try the next. Friends, mentors, and a supportive community keep momentum up when it feels discouraging.

Timing: 60 seconds. Don't read every link. Show how to choose: one place to explore (Code.org, Scratch), one deeper curriculum (freeCodeCamp, Microsoft Learn, Odin), and one hands-on practice spot. Depth beats a giant bookmark list.

Timing: 60 seconds. Point students to youth-friendly clubs and safe online communities - robotics teams, Girls Who Code, CoderDojo, plus teen-focused spaces like Hack Club and beginner-friendly forums (freeCodeCamp, dev.to) - alongside fun challenge sites. Reinforce safety: keep sharing public and school-appropriate and loop in a trusted adult. Encourage asking a teacher what clubs already exist at school.

Timing: 60 seconds. Motivation lasts longer when learning is fun. Programming games teach real logic; building something personal (a game, a site, a gadget) keeps students engaged. Encourage one project they'd genuinely enjoy making.

Timing: 75 seconds. Push back on the idea that tech requires expensive courses. School clubs, hackathons, CoderDojo, and library programs are free and welcoming. Challenge sites and coding games build skills and are fun - remind students they're practice, not a leaderboard to stress over.

Timing: 60 seconds. The core tools are free: Python, C#, JavaScript, and VS Code. JetBrains IDEs are free for students, and a Raspberry Pi is an inexpensive way to get hands-on. Students should grab the GitHub Student Developer Pack and Azure for Students while eligible - free tools and cloud credits. Nothing expensive gates hands-on practice.

Timing: 30 seconds. Return to the three-part framing from the title. Ask students to write down the one area they'll explore and the small project they'll start. The goal is to turn excitement into one concrete, doable action.

Timing: 5 minutes. Invite questions about choosing an area, project ideas, clubs and competitions, or getting started. If no one starts, ask: "What sounds the most fun to try?" Leave the contact slide visible.

Timing: 20 seconds. A quick "scan to follow along" moment. Tell students they can grab the slides now and revisit every link and resource afterward - no need to write anything down.