Skip to main content

Alpha Hacks ft. Zakk Fleischmann - Design Document (Draft v0.1)

Event Name: Alpha Hacks: AI Builders Challenge Date: April 26, 2025 (Saturday) Location: Alpha School High School Campus, Austin, TX Lead Coordinator: Zakk Fleischmann (zkf.io) Core Concept: A one-day AI hackathon for local high school students, featuring funded challenges/prizes and mentorship from older students/professionals. Foundation: Built upon the Day One Academy ethos (learning by building, experimentation).

Authors: Zakk Fleischmann, Gary Sheng, [Placeholder: Add other key organizers, e.g., Jack Oremus, Alpha Staff Liaison?] Status: Initial Draft

1. Introduction & Vision​

Problem: Many high school and college students are eager to build with AI but lack accessible, hands-on opportunities. Alpha School seeks to connect its talent pool with the broader local community and identify potential future students or ecosystem contributors.

Vision: Alpha Hacks aims to be a recurring event series igniting passion for building with AI among Austin-area students. Led by Zakk Fleischmann and founded on the Day One Academy ethos (main--kaleidoscopic-pika-9eddb7.netlify.app), this inaugural event provides a fun, competitive space to tackle challenges, learn AI tools, and connect with mentors. Crucially, it serves as a key touchpoint for identifying high-potential individuals and growing the Alpha School movement.

Goal for April 26th: Successfully pilot the Alpha Hacks format, test the funded challenge model, engage local students, identify potential recruits for Alpha School/ecosystem, provide value through Zakk's leadership, and foster inter-cohort connections.

2. Goals & Objectives​

  • Engage Local Youth & Talent: Introduce ~50-100 local high school and college students to practical AI application development.
  • Promote Learning by Building: Facilitate rapid experimentation with current AI tools.
  • Showcase Talent & Identify Potential: Provide a platform for students to demonstrate skills; identify high-agency individuals aligned with the Alpha ethos.
  • Recruitment & Movement Growth: Serve as an engaging entry point to the Alpha School ecosystem, attracting potential future students and contributors.
  • Test Incentive Model: Pilot faculty/community-funded challenges and prizes.
  • Foster Community: Connect Alpha students, local peers, college students, and mentors.
  • Leverage Expertise: Utilize Zakk Fleischmann's leadership and experience (zkf.io).
  • Brand Building: Position Alpha School as a hub for youth innovation and AI.

3. Event Details​

  • Date: Saturday, April 26, 2025
  • Time: Approx. 9:00 AM - 7:00 PM (Full Day Event, TBC)
  • Venue: Alpha School High School Campus (Specific rooms/areas TBD - main space, breakout rooms).

3.1 Team Roles​

  • Lead Coordinator & Challenge Coordinator (Zakk Fleischmann): Overall lead for event design, execution, and vision. Responsible for keynote/workshop content, setting the tone, potentially head judge. Also responsible for soliciting, defining, and managing the funded challenges/prizes.
  • Support & Accountability (Gary Sheng): Assist Zakk as needed, potentially acting as a mentor, ensuring resources are available, and holding Zakk accountable for successful execution. Not the primary operational coordinator.
  • Mentor Coordinator (Gary Sheng): Recruit and manage college/Gauntlet mentors, ensuring they are briefed and effective in supporting HS participants.
  • Alpha Liaison / Logistics (Jack Oremus): Coordinate venue, internal Alpha School comms, budget tracking (with Zakk/Gary), volunteer coordination within Alpha.
  • Outreach Coordinator (Cruce Saunders): Manage promotion to local schools (liaising with counselors?), community groups, and potentially college groups.
  • [Placeholder - Needs Owner]: Assign responsibility for specific logistics like Food/Beverage, AV setup, Swag (if applicable).

4. Target Audience​

  • Primary Participants (Prize Eligible):
    • Current Alpha School High School students.
    • High school students from other local Austin schools.
    • College students (e.g., from UATX, UT Austin).
    • (Consideration: Potentially allow advanced Middle School students with appropriate support/supervision, TBD for pilot).
    • Focus: Encourage participation regardless of prior AI experience; enthusiasm and willingness to learn are key.
  • Secondary Participants (Mentors / Non-Competing Builders):
    • Gauntlet AI graduates / current participants.
    • Other interested community members/professionals (e.g., experienced engineers, designers, faculty).
    • Role: Provide guidance, technical support, and mentorship primarily to high school participants, but also available to college participants. They can work on their own projects alongside but are not eligible for the primary challenges/prizes.

5. Event Format & Schedule (Draft - Condensed)​

  • 10:00 AM: Check-in, Light Breakfast, Networking
  • 10:30 AM: Welcome & Introduction (Alpha School rep, Zakk Fleischmann)
  • 10:45 AM: Keynote/Workshop: "Building & Prototyping in the Age of AI" (Zakk Fleischmann)
  • 11:15 AM: Presentation of Challenges & Prizes (Challenge Sponsors/Coordinator)
  • 11:30 AM: Team Formation (Optional) / Ideation / Hacking Starts
  • 1:00 PM: Lunch Break & Mentor Mingling
  • 1:45 PM: Hacking Continues (Mentors circulate, Zakk available for consults)
  • 4:30 PM: Hacking Ends / Prep for Demos
  • 4:45 PM: Project Demos (Short pitches/demos from each team/individual)
  • 5:30 PM: Judging Deliberation / Networking Break
  • 5:45 PM: Awards Ceremony & Closing Remarks (Zakk Fleischmann / Alpha Rep)
  • 6:00 PM: Event Concludes

6. Challenges & Prizes Mechanism​

  • Source: Challenges/Prizes proposed and funded by Alpha School faculty, potentially extended to community members or sponsors (e.g., local tech companies, Gauntlet grads).
  • Format: Can be specific tasks ("Build an AI tool using X API to solve Y local problem") or open-ended prizes ("Most creative use of AI for community connection," "Best educational AI application").
  • Goal: Incentivize focused building aligned with specific needs or creative directions. Ensure diverse challenges cater to different skill levels.
  • Communication: Challenges/prizes must be clearly defined and communicated at the start of the event.
  • Judging: A panel including renowned startup tech leaders (CEOs/CTOs), faculty sponsors, Zakk Fleischmann, and potentially key mentors evaluates projects based on criteria relevant to each challenge/prize (e.g., functionality, creativity, impact, learning demonstrated).
  • Note: Zakk is the Lead Coordinator (See Section 3.1). His background in building, prototyping, community, and education makes him ideal to lead this event, aligning with his current sabbatical focus.

8. Mentorship Component​

  • Gauntlet grads, experienced professionals, and potentially upper-level college students act as guides.
  • Responsibilities: Help HS and College participants troubleshoot technical issues, brainstorm ideas, understand tools, refine demos, and generally navigate the hackathon process.
  • Goal: Ensure all primary participants have a positive, productive learning experience, regardless of their starting skill level.

9. Technology & Tools​

  • Core: Participants likely use personal laptops.
  • AI Platforms: Access to common platforms (OpenAI API keys?, Hugging Face, Replicate, etc.) - Need to confirm logistics/provisioning.
  • Development Tools: Cursor, VS Code, relevant web frameworks, etc.
  • Foundation: Leverage resources, templates, and methodologies from Day One Academy where applicable.
  • Infrastructure: Reliable Wi-Fi, power strips, potentially shared cloud credits.

10. Logistics & Needs​

  • Venue: Secure appropriate spaces at Alpha High (main area, breakout rooms).
  • Food & Beverage: Breakfast, lunch, snacks, drinks.
  • AV: Projector, screen, microphones for presentations.
  • Staffing/Volunteers: Registration check-in, setup/cleanup, mentor coordination, timekeeping.
  • Registration: Platform for participant sign-up (Lu.ma? Eventbrite?). Clearly differentiate HS vs. Mentor tracks.
  • Outreach: Promotion to local high schools, Alpha students, relevant college/community groups.
  • Challenge/Prize Coordination: System to collect, manage, and present challenges/prizes. Secure funding commitments.
  • Judging Process: Define criteria, scorecards, deliberation process. Recruit judges (CEOs, CTOs, etc.).
  • Swag (Optional): T-shirts, stickers.

11. Success Metrics (for Pilot Event)​

  • Attendance: Achieve target numbers for both HS participants and Mentors. Representation from multiple local schools.
  • Project Completion: Number of projects successfully demoed.
  • Challenge Engagement: Number of challenges attempted/prizes awarded.
  • Participant Feedback: Positive survey results regarding learning, enjoyment, mentorship quality, event organization.
  • Mentor Engagement: Feedback from mentors on the experience and student quality.
  • Qualitative: Anecdotes of learning breakthroughs, new connections formed, excitement generated.

12. Immediate Next Steps (Urgent due to April 26 Date)​

  1. Confirm Zakk Fleischmann's Lead Role & Availability: Solidify responsibilities.
  2. Assign Core Team Roles: Identify Alpha Liaison, Outreach, Mentor, Challenge Coordinators.
  3. Secure Venue Commitment: Confirm space availability and setup at Alpha High.
  4. Define & Secure Challenges/Prizes: Solicit proposals from faculty/community immediately. Finalize list ASAP.
  5. Recruit Judges: Begin outreach to target tech leaders (CEOs, CTOs).
  6. Create Registration Page: Launch sign-ups with clear audience tracks.
  7. Develop Outreach Plan: Target local HS (via counselors?), Alpha network, college groups. Create promotional materials.
  8. Recruit Mentors: Actively reach out to Gauntlet grads, college students, etc.
  9. Outline Budget: Estimate costs for food, potential swag, prize pool if not fully sponsored.

13. Collaboration Notes & Ideas​

  • (Gary's Thoughts): Focus on support, mentorship, ensuring Zakk has what he needs to succeed. Leverage network for judges/mentors.
  • (Jack's Thoughts / Others'): [Add specific points, concerns, or alternative ideas here]
  • Future Iterations: How can this evolve? Monthly? Quarterly? Different themes?