Design a One-Day AI Assistant Hackathon for High School Students
A one-day hackathon works best when high school students are asked to design and prototype an AI assistant for a real problem they care about, not to build software from scratch. That keeps the day practical, ambitious, and accessible to students with no coding experience while still feeling relevant to teenage life.
What the Event Should Feel Like
This should be positioned as a design-and-prototype hackathon, not a programming contest. Students are solving a real problem and showing how an AI assistant would help, including what it should say, what it should avoid, and how a user would experience it.
Who It Is For
This version is designed for high school students. It works especially well for grades 9 through 12, where students can handle more open-ended problem selection, sharper user research, and stronger pitch storytelling.
Core Challenge
Each team chooses one meaningful problem from academic life, extracurriculars, college and career planning, community life, mental wellbeing, or personal organization, then designs an AI assistant that helps with that problem.
Recommended Team Roles
- Problem finder: keeps the team focused on the user and the pain point.
- Conversation designer: maps the assistant's questions, replies, and flow.
- Prototype builder: turns the idea into a no-code demo.
- Presenter: leads the final pitch and demo story.
For solo participants, one student can cover all roles. For smaller teams, each student can take more than one role.
Event Success Measure
Success is not technical complexity. Success is a clear problem, a thoughtful assistant concept, a believable user journey, and a safe, useful prototype.
One-Day Hackathon Schedule
The day should move from problem discovery to assistant design, then to prototyping, testing, and short final presentations. The pacing below is realistic for a school setting.
Kickoff and Inspiration
Start with a short explanation of what AI assistants are and show two or three examples that feel real to teenagers, such as a study coach, club planning assistant, or internship prep helper. Set clear ground rules: solve a real problem, keep the experience safe, use no-code tools, and focus on usefulness over complexity.
Problem Discovery
Ask teams to brainstorm five real problems high school students experience. Good prompts include: What makes school harder than it should be? What wastes time or creates stress? What makes clubs, projects, applications, or planning more confusing? What would be easier if you had a smart helper?
Define the User and the Assistant
Teams choose one problem and define who the assistant serves, what the user needs, what the assistant can do well, and what it should not try to do. This is the moment to narrow scope.
Conversation Mapping
Students sketch the assistant's flow on paper or slides: opening message, common user questions, follow-up prompts, safety fallback, and what the assistant finally recommends or helps the user produce.
Lunch and Mentor Check-In
Use lunch as a review window. Mentors should challenge vague ideas, push students to simplify the user journey, and make sure teams avoid unsafe or unrealistic assistant behavior.
No-Code Prototyping
Teams build their assistant using a free no-code tool, or create a clickable conversation demo if they want a lighter-weight prototype. The goal is to make the interaction easy to understand.
Peer Testing
Each team tests another team's prototype. Reviewers should note whether the assistant is useful, easy to understand, and appropriately cautious when it does not know something.
Refine the Experience
Students improve their prompt instructions, wording, examples, and visual structure. Most teams do not need more features here. They need more clarity.
Pitch Preparation
Teams prepare a short final presentation covering the problem, the user, the assistant idea, a quick demo, and what they learned about designing with AI.
Demos and Awards
Keep the judging lightweight and celebratory. A three-minute team demo is enough. Choose awards that reward usefulness, creativity, thoughtful design, and responsible use of AI.
What Each Team Should Deliver
The deliverables should reflect design maturity, not technical difficulty. By the end of the day, every team should be able to explain what problem they chose and show how their assistant helps.
Assistant Concept
- A short assistant name.
- A one-sentence mission statement.
- A simple description of the intended user.
Conversation Design
- Three to five common user prompts.
- Likely follow-up questions.
- A fallback response for uncertainty or unsafe requests.
No-Code Prototype
- A working assistant prototype or a clickable mock conversation.
- A flow that is easy for judges to understand quickly.
- A demo that can be shown in under one minute.
Final Pitch
- Problem being solved.
- Why the assistant matters.
- Short live demo or narrated prototype walkthrough.
Good Problem Areas for High School Students
- Assignment planning, deadlines, and workload management.
- Study support, revision planning, and concept explanation.
- Club leadership, event coordination, and student council work.
- Internship, scholarship, and college application preparation.
- Stress management, routines, and healthy school-life balance.
Ideas to Avoid
- Medical diagnosis or emergency decision making.
- High-risk legal or financial advice.
- Anything that encourages unsafe secrecy from adults.
- Scopes so broad that students cannot prototype them in one day.
Simple Judging Rubric
A school-friendly rubric should reward relevance, clarity, and responsibility more than technical polish. Each category can be scored from 1 to 5.
Problem Relevance
Ask: Is this a real problem high school students actually face, and is the need clearly explained?
Usefulness
Ask: Does the assistant genuinely help the user move forward rather than just sounding impressive?
Experience Design
Ask: Is the interaction easy to follow, well-structured, and understandable for the intended user?
Safety and Boundaries
Ask: Does the team show good judgment about what the assistant should avoid, escalate, or answer carefully?
Good Award Categories
- Most Useful Assistant
- Best Problem Choice
- Best User Experience
- Most Thoughtful Safety Design
- Best Team Presentation
Judge Instruction
Ask judges to reward teams that made smart design choices with limited time. A simpler idea done clearly should beat a bigger idea that remains vague or unsafe.
Free Platforms Students Can Use
The platform choice should reduce friction, not increase it. For a one-day event, the best options are the ones that help students prototype quickly without requiring paid plans or coding.
Google AI Studio
This is the strongest default if teams want to test prompt-based assistants quickly. High school students can experiment with instructions, example prompts, and response quality without writing code.
- Best for text-first assistant behavior.
- Fast to start with mentor guidance.
- Useful when the goal is prompt design, not app building.
Voiceflow
A good option for teams that want a drag-and-drop conversation builder. It is well suited for mapping user journeys and showing a polished demo at the end of the day.
- Strong for conversational flows.
- Good visual interface for student teams.
- Free tier is usually enough for prototype work.
Botpress Cloud
Useful if you want slightly more structure and mentor-supported setup. It is better for teams that need branching logic and clearer conversation paths.
- Better for guided bot experiences.
- Good when mentors can help with setup.
- More involved than Google AI Studio for beginners.
Coze
Coze is practical when teams want to assemble a demoable assistant quickly with minimal overhead. It can work well for short hackathon-style experiments.
- Quick setup for lightweight assistant demos.
- Useful for teams focused on speed.
- Best when the mentor group is familiar with the tool already.
Canva
If the event emphasizes design thinking rather than live AI behavior, Canva works well for mock chat screens, pitch slides, and storyboards.
- Very accessible for student teams.
- Excellent for slides and interface mockups.
- Strong choice when internet or account setup needs to stay simple.
Figma
Figma is useful when you want teams to focus on interface design, clickable prototype flows, and user journey clarity rather than model behavior.
- Best for screen design and mock interactions.
- Useful for teams with strong visual thinkers.
- Pairs well with a separate prompt-testing tool.
Recommended Simple Stack
For the easiest one-day setup, use Google AI Studio for assistant behavior, Canva for pitch slides, and paper templates or whiteboards for conversation mapping.
Account and Safety Note
Use adult-managed accounts where needed, define clear acceptable-use rules, and remind teams that an AI assistant should not replace teachers, parents, or trusted adults in high-stakes situations.
Organizer Checklist
A well-run student hackathon depends less on fancy infrastructure and more on clear prompts, simple templates, and active facilitation.
Before the Event
- Pick one primary platform and test it with a student lens.
- Create a one-page worksheet for problem, user, assistant goal, and safety limits.
- Prepare two example projects so students see the right level of ambition.
- Arrange mentors who can coach scope, not just technology.
During the Event
- Push teams toward sharper problem definitions.
- Ask students what the assistant should refuse or escalate.
- Keep presentations short and transition times tight.
- Use peer testing to catch confusing flows early.