--- title: "Hackathons for High School Students | Which Ones Accept You and What To Do After" description: "Hackathons for high school students: which events accept school-age participants, the real Congressional App Challenge rules, and how to turn a weekend build into something that still counts twelve months later." canonical: https://learn.modernagecoders.com/hackathons-for-high-school-students keywords: ["hackathons for high school students", "coding competitions for students", "Congressional App Challenge help", "student hackathon preparation", "learn to code for hackathons", "AI classes for teens"] source: src/pages/hackathons-for-high-school-students.html --- > Hackathons for high school students: which events accept school-age participants, the real Congressional App Challenge rules, and how to turn a weekend build into something that still counts twelve months later. [Courses](/courses)/ Hackathons # Hackathons for high school students, and what to do the week after. A hackathon is the cheapest way to find out whether your child can build under pressure. It is also, on its own, one of the weakest lines on an application. The difference is entirely in what happens next. Talk to a mentor[WhatsApp us](https://wa.me/919123366161?text=Hi%2C%20I%20want%20help%20preparing%20for%20a%20hackathon)Since 2020Teaching students to build10,000+Students taught25+Countries![Hackathons for Students poster, Modern Age Coders live online coding classes](/images/adm-hackathons.webp) ## This page is for you if - Your child wants to enter their first hackathon - You want to know which events accept school students - You want the weekend build to actually lead somewhere - You are outside the US and wondering what applies Courses ## Get build-ready before the event A hackathon assumes you can already make something small work end to end. These classes get a student there. [![Python and AI classes for kids and teens thumbnail, Modern Age Coders](/images/python-teens.webp) Beginner Python and AI classes for kids and teens The usual starting point. Language fundamentals to the level where a first real project becomes possible. View course](/python-and-ai-classes-for-kids-teens)[![Vibe coding, used properly thumbnail, Modern Age Coders](/images/vibe-coding-teens.webp) All levels Vibe coding, used properly How to build with AI assistance and still be able to explain every line, which is what an interview will test. View course](/vibe-coding-classes)[![Build machine learning models in Python thumbnail, Modern Age Coders](/images/ai-ml-teens.webp) Intermediate Build machine learning models in Python For students who already code and want a model they trained themselves, not a tutorial they copied. View course](/build-machine-learning-models-in-python)[![Build an AI agent in Python thumbnail, Modern Age Coders](/images/python-automation-ai-college.webp) Intermediate Build an AI agent in Python Agents that plan and use tools, which is where a project stops looking like a chatbot wrapper. View course](/build-ai-agent-python) [See every course we teach](/course-atlas) In short A hackathon is a time-boxed event, usually a weekend, where teams build working software from scratch. School-age students are eligible for many of them: MLH events accept students at any level of study including middle and high school, and the Congressional App Challenge is specifically for middle and high school students, though it requires US residency. Modern Age Coders prepares students for these events and, more usefully, helps them develop the weekend build into something finished afterwards. To talk it through, use the form below or message us on WhatsApp at +91 91233 66161. ## The short version - Many hackathons do accept school students. MLH defines student attendees to include middle school, high school and non-traditional learners. - The Congressional App Challenge is the most accessible formal competition for US school students, but it is US residents only. - Technovation runs a global season for girls and gender-diverse students aged roughly 8 to 18, ending in a spring submission. - A hackathon result on its own is a participation line. Continuing the project afterwards is what converts it into evidence. - The demo video matters more than the code at most of these events. Congressional App Challenge submissions turn heavily on a short demonstration video. The evidence ## Who can actually enter what Eligibility is where most families waste a season. These are the published rules. School OK ### MLH: school students are included MLH defines student attendees as enrolled at any level of study, at traditional institutions including middle school and high school, at non-traditional ones such as bootcamps or home school, or graduated within the past year. [Source: MLH member event guidelines](https://github.com/MLH/mlh-policies/blob/main/member-event-guidelines.md)US only ### Congressional App Challenge: residency required Open to middle and high school students who are US residents at the time of submission, with no citizenship requirement. Students compete in the district where they live or attend school, in teams of up to four. [Source: Congressional App Challenge rules](https://www.congressionalappchallenge.us/students/rules/)1 to 3 min ### The demo video is the submission For the Congressional App Challenge the most critical component is a demonstration video of one to three minutes. The app may be in any language for any platform. [Source: Congressional App Challenge](https://www.congressionalappchallenge.us/)Global ### Technovation: worldwide, ages 8 to 18 Technovation Girls runs a global season for students aged 8 to 18 who identify as female, trans, nonbinary or gender nonconforming, with divisions by age and a submission that includes the code and any AI training work. [Source: Technovation eligibility](https://iridescentsupport.zendesk.com/hc/en-us/articles/115002714613-Eligibility-for-participation-students)The list ## What to build, and what to build it into Weekend-scoped ideas that have an obvious second life, so the project does not die on Sunday night. Weekend ### Buildable in 24 to 36 hours Scope ruthlessly #### A tool that solves a problem at your own school Lost property, room booking, revision scheduling. The judges understand the problem instantly and you can demo it with real data. WebReal problem Continues naturally: deploy it for actual use the following term. #### An accessibility overlay for a site everyone uses Larger text, better contrast, keyboard navigation, applied to a site that badly needs it. Extension Continues into a published extension with real installs. #### A single-purpose data visualisation Take one public dataset and answer one question with one clear chart, built well rather than broadly. Data viz Continues into a proper analysis with the method written up. #### A small game with one original mechanic Not a clone with a reskin. One mechanic nobody at the event has seen, executed completely. Game Continues into a published, playable release with feedback from players. #### A model wrapped in the simplest possible interface One model, one input box, one honest output including what it does when it is unsure. AIMinimal UI Continues into the evaluation and failure analysis you had no time for on the weekend. The week after ### Turning it into evidence This is the part that counts #### Fix everything you faked for the demo Every hackathon build has hardcoded values and dead buttons. Replace them one by one and note each in the commit history. Follow through The commit history after the event is proof of persistence, which is what a weekend cannot show. #### Get five people to use it who were not at the event Watch them. Write down where they stopped. Fix those five things. Users Turns "we built it in a weekend" into "people use it", which is a completely different claim. #### Write the README you skipped What it does, how to run it, what is not finished. Honest and specific. Docs Makes the repository legible to anyone who looks, including an admissions reader. #### Re-record the demo properly The rushed event video is not the one to keep. Record a clean one to three minute demonstration. Demo video This is literally the submission format the Congressional App Challenge asks for. #### Enter it somewhere that has a deadline A district challenge, a school competition, an app store review queue. External deadlines finish projects that self-discipline does not. Deadline An external gate produces a dated, verifiable result. The standard ## How to actually do well at one Six things that separate teams who finish from teams who demo an error screen. 01 ### Decide the demo first Write the ninety second demo script before writing code. Build only what the script needs. 02 ### Cut the scope in half, then again Every experienced team underbuilds deliberately. Finished and small beats ambitious and broken. 03 ### Assign roles in the first hour Who builds, who integrates, who presents. Ambiguity costs more hours than any bug. 04 ### Freeze six hours early Stop building. Integrate, test on a fresh machine, and rehearse. This is where most teams lose. 05 ### Record the demo before you present Live demos fail. A recorded fallback has saved more presentations than any amount of debugging. 06 ### Keep the repository public and honest Commit throughout rather than in one dump. The history is the part that has value afterwards. Timing ## From first event to something that counts Roughly how a productive year looks, built around events rather than around a vague intention. Month 0 ### Get to build-ready Able to make something small work end to end. Without this a hackathon is a spectating experience. Month 1 ### First event, expect a mess The first one is for learning the format. Finishing anything at all is a win. Month 2 ### Continue one build for four weeks Pick the least broken thing you made and take it to genuinely finished. Months 3 to 6 ### Second and third events Now with a working method: scope small, freeze early, record the demo. Months 6 to 10 ### Enter something with a real deadline A district or national challenge with published rules and a submission date. Month 12 ### One project, properly finished Repository, demo video, users, README. The hackathons were the training, this is the artefact. Two ways in ## A weekend is short. Getting good at weekends is not The event lasts two days. The ability to be useful in those two days takes considerably longer to build. The long journey ### Starting at 6 or 7, building for years A student who has been coding since seven walks into a first hackathon able to contribute instead of watch. That is entirely a function of the years before it. - **Ages 6 to 9**Block coding and logic. Finishing small things, which is the habit everything later depends on. - **Ages 10 to 13**Real code in Python. First projects that another person can actually run. - **Ages 14 to 16**AI and machine learning, own datasets, work that goes in front of real users. - **Ages 17 to 18**Portfolio, competitions and research-grade work, with years of history behind it. By the time it matters, the repository is years deep. That cannot be assembled in a hurry, and it is obvious to anyone who looks. The short route ### A deadline in weeks, not years If the event is next month, the goal is to be able to build one small thing end to end and to scope ruthlessly. That is trainable quickly, unlike fluency. - **Weeks 1 to 2**Scope honestly against the time left. Most ideas get cut down here, and that is the useful part. - **Weeks 3 to 6**Build the smallest version that genuinely works, with the repository open from day one. - **Weeks 7 to 8**One real user, then fix what tripped them up. - **Final week**README, recorded demo, and rehearsal for being questioned about it. Smaller and finished beats ambitious and broken. We will tell you before you start if the deadline does not allow honest work. Send us the event date. If there is not enough time to be useful at it, we will say so and point at the next one instead. How we do it ## Preparation, and the follow-through afterwards The weekend is easy to sign up for. The four weeks afterwards are where the value actually is. Portfolio Program ### The four weeks after the weekend We prepare students for the format, scoping, splitting work, freezing early, and then we work with them on the part almost everyone skips: taking the weekend prototype to something finished, documented and demonstrable. - Practice at scoping to a ninety second demo before writing code - Team habits: roles in the first hour, integration long before the deadline - A recorded fallback demo, because live demos fail at the worst moment - Then the follow-through, replacing everything that was faked to ship - A clean rebuild of the demo video to the one to three minute format Prepare for an event The build ability an event assumes you already have. [Python and AI classes for kids and teensBeginner](/python-and-ai-classes-for-kids-teens)[Vibe coding, used properlyAll levels](/vibe-coding-classes)[Build machine learning models in PythonIntermediate](/build-machine-learning-models-in-python)Fees ## What preparation costs Event preparation and the follow-up work happen in regular classes at the regular fee. ### Group class Batches of 5–8. Good for building the fundamentals. ₹1,499per month ### Mini batch 3–4 students. More airtime per student. ₹2,999per month ### One to one 1:1. The usual choice for a project with a deadline. ₹7,500per month Prices are per month and shown per region. Hackathon entry is usually free and is arranged by you directly with the organiser. See [full pricing](/pricing) for every subject and tier. Proof ## Projects our students finished Real builds from Modern Age Coders students, published on Student Labs. ### Doodle Dash, a 30 second drawing challenge A finished game loop with state, timing and scoring. Small scope, complete execution. ### Babu, a 90 second maths challenge Timing, scoring and question generation. Deceptively fiddly once the edge cases arrive. ### Baby, a typing speed challenge Input handling, accuracy measurement and live feedback. A clean, complete piece of work. ### Simon Game Sequence, state and timing. A rite of passage that either works completely or does not work at all. [See what students finished](/student-labs) ## Tell us about the event Tell us the event and the date. We reply within one business day with what is realistic to have working by then. ### Event this month? Message us with the date and we will tell you honestly whether preparation time is enough to be useful. [WhatsApp+91 91233 66161](https://wa.me/919123366161?text=Hi%2C%20I%20want%20help%20preparing%20for%20a%20hackathon)[Call+91 91233 66161](tel:+919123366161)[Emailcontact@modernagecoders.com](mailto:contact@modernagecoders.com?subject=Hackathon%20Preparation%20enquiry) Your details are used only to answer your enquiry and are never shared or sold. We coach students to build their own entries and never build them. Questions ## Frequently asked Can high school students join hackathons? Yes for many events. MLH defines student attendees to include middle school and high school students, as well as home school and other non-traditional learners, and students who graduated within the past year. What is the Congressional App Challenge? A competition run through US congressional districts for middle and high school students. Students may enter individually or in teams of up to four, apps can be in any language for any platform, and the critical submission component is a demonstration video of one to three minutes. Can students outside the US enter the Congressional App Challenge? No. All competing students must be US residents at the time of submission, although there is no citizenship requirement. Students compete in the district where they live or attend school. Are there global options for students outside the US? Yes. MLH runs events internationally and online, and Technovation runs a worldwide season for students aged 8 to 18 who identify as female, trans, nonbinary or gender nonconforming. Do hackathon wins help with admissions? A placement helps a little, participation alone helps very little. What converts a hackathon into real evidence is continuing the build afterwards until it has users, documentation and a proper demonstration. What should a first-time team build? Something small enough to finish, solving a problem the judges recognise immediately. Write the ninety second demo script first and build only what that script requires. How do we prepare? Be able to build something small end to end before the event, practise scoping aggressively, and rehearse the demo. We run this preparation with students and then work with them on the follow-through. Does my child need a team? Most events allow individual entries, but a team of two or three is usually more productive. The Congressional App Challenge allows teams of up to four. Keep reading ## Related guides [Passion project ideasIdeas that survive a sceptical reader, and the ones that do not.Read the guide](/passion-project-ideas-computer-science)[CS extracurriculars, rankedWhat carries weight, what is neutral, and what is filler.Read the guide](/computer-science-extracurriculars)[How to build a coding portfolioThe finished standard: repo, demo, build log, defence.Read the guide](/how-to-build-a-coding-portfolio)[AI projects for high schoolersA ladder from first model to research-grade work.Read the guide](/ai-projects-for-high-school-students)[Student LabsReal projects our students designed and shipped.See the work](/student-labs)[How we teachLive, small batches, project first. What a class actually looks like.See the method](/how-we-teach) --- *Canonical: https://learn.modernagecoders.com/hackathons-for-high-school-students*