What to expect

One visit. Forty-five minutes. No prep required.

You sit with eight to fifteen students who are learning to vibe code. You show them how you use AI in your actual work. They ask questions. That is it. Your example is the curriculum.

0–5 min

Introductions.

The teacher champion introduces you. Students know your name and field. You know theirs.

5–20 min

Your story, and how AI fits in.

How you got here. What your day actually looks like. How you use AI in your work: what it does well, where it fails, how it changed your process. Keep it real.

20–35 min

Questions and conversation.

Students ask whatever they want. The best questions will not be the ones you expect. Let them lead.

35–45 min

Connections.

Students working on projects related to your field can ask follow-up questions. You can offer to stay connected if you want. No obligation.

Who we are looking for

The best guides are not the most impressive on paper. They are the ones who can show a teenager what building with AI actually looks like in the real world.

Developers & engineers

You vibe code daily, using AI to write, debug, and ship. Show students what it looks like when a professional collaborates with AI to build real software.

Designers & creatives

You use AI for ideation, prototyping, and production. Show students how professional craft and AI tools work together on real projects.

Marketers & strategists

You use AI to write copy, analyze data, and build campaigns. Show students how AI turns an idea into a launch plan.

Entrepreneurs & founders

You used AI to build your landing page, model your pricing, or automate your operations. Show students what starting something looks like now.

Hardware & IoT builders

You use AI to write firmware, design circuits, or prototype devices. Show students that vibe coding goes beyond the screen.

Content creators & filmmakers

You use AI for scripting, storyboarding, editing, or scoring. Show students how AI amplifies creative vision across media.

Working with minors

What makes a good session.

VIBE sessions happen inside schools with a faculty champion present. These guidelines keep everyone comfortable and safe.

Do

  • Address the group, not individuals privately
  • Let the teacher lead classroom management
  • Share your real work experience, including how you use AI
  • Ask open-ended questions
  • Be honest about hard days and setbacks
  • Direct follow-up requests through the faculty champion

Don’t

  • Exchange personal contact info with students directly
  • Meet students outside the school setting
  • Promise outcomes you cannot deliver
  • Use jargon without explaining it
  • Photograph or record students without written consent
  • Connect with students on personal social media

Full safety policies: Student Safety & Compliance →

Common questions

Everything guides ask us.

Do I need to prepare anything?

We send you a short guide kit about 15 minutes of reading that explains what the students are working on, what to expect, and the safety guidelines. No slides or lesson plan needed. Your real experience is the content.

How much time does it take?

One visit, forty-five minutes. Some guides choose to come back for a second session during the build phase (weeks 8–11) to give feedback on student projects. That is optional.

Do I need a background check?

Most schools require one. The school or host organization will walk you through their process. It is usually a simple online form and takes a few days. We will help coordinate.

What ages are the students?

Typically grades seven through twelve, so ages thirteen to eighteen. Students must be at least 13 to use AI tools directly, which is why we start at grade seven.

What level of AI experience do I need?

You should be someone who uses AI tools in your work, even if just for drafting, brainstorming, or prototyping. The students are learning vibe coding, so seeing how a professional actually uses AI day to day is the whole point.

Can I bring a colleague?

Absolutely. Two perspectives from the same field are often richer than one. It also makes the conversation more natural.

What if a student wants to stay in touch?

All follow-up goes through the faculty champion. If a student wants to continue a conversation, the champion can facilitate an introduction through school channels. Guides should not exchange personal contact information directly with students.

Spread the word

Know someone who builds with AI?

Copy this message and send it. Most people say yes when asked directly and told exactly what it involves.

Sample guide invitation: copy, adapt, send

Hi [Name],

A small group of students at [School] is learning vibe coding, building real apps, tools, and projects by collaborating with AI. Would you spend 45 minutes showing them how you use AI in your actual work?

No prep required. No slides. Just your real experience and their questions. Your example is the curriculum.

If you are interested, reply and I will connect you with the teacher running it. Details at vibeafterschool.com/guides.

Beyond the first visit

Ways to stay involved.

One visit is enough. But if the experience resonates, there are deeper ways to contribute.

Return for the build phase

Come back during weeks 8–11 to give feedback on student projects in your field. Thirty minutes of expert input can transform a project.

Host a site visit

Invite the cohort to your workplace. Seeing a real office, shop, studio, or hospital is exposure no classroom can replicate.

Judge the showcase

Attend the week 12 showcase and give students real feedback on their presentations. Professional validation matters.

Recruit other guides

The hardest part of launching a pilot is finding AI-fluent professionals. If you know three people who build with AI, that is a semester’s worth.

Sign up

Ready to guide?

Tell us your name, how you use AI in your work, and your city. We will match you with a school in your area.

Last updated: April 2026