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.
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
The usual starting point. Language fundamentals to the level where a first real project becomes possible.
View course
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
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 an AI agent in Python
Agents that plan and use tools, which is where a project stops looking like a chatbot wrapper.
View courseIn 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.
Who can actually enter what
Eligibility is where most families waste a season. These are the published rules.
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 guidelinesCongressional 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 rulesThe 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 ChallengeTechnovation: 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 eligibilityWhat 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.
Buildable in 24 to 36 hours
Scope ruthlesslyA 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.
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.
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.
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.
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.
Continues into the evaluation and failure analysis you had no time for on the weekend.
Turning it into evidence
This is the part that countsFix 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.
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.
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.
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.
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.
An external gate produces a dated, verifiable result.
How to actually do well at one
Six things that separate teams who finish from teams who demo an error screen.
Decide the demo first
Write the ninety second demo script before writing code. Build only what the script needs.
Cut the scope in half, then again
Every experienced team underbuilds deliberately. Finished and small beats ambitious and broken.
Assign roles in the first hour
Who builds, who integrates, who presents. Ambiguity costs more hours than any bug.
Freeze six hours early
Stop building. Integrate, test on a fresh machine, and rehearse. This is where most teams lose.
Record the demo before you present
Live demos fail. A recorded fallback has saved more presentations than any amount of debugging.
Keep the repository public and honest
Commit throughout rather than in one dump. The history is the part that has value afterwards.
From first event to something that counts
Roughly how a productive year looks, built around events rather than around a vague intention.
Get to build-ready
Able to make something small work end to end. Without this a hackathon is a spectating experience.
First event, expect a mess
The first one is for learning the format. Finishing anything at all is a win.
Continue one build for four weeks
Pick the least broken thing you made and take it to genuinely finished.
Second and third events
Now with a working method: scope small, freeze early, record the demo.
Enter something with a real deadline
A district or national challenge with published rules and a submission date.
One project, properly finished
Repository, demo video, users, README. The hackathons were the training, this is the artefact.
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.
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 9Block coding and logic. Finishing small things, which is the habit everything later depends on.
- Ages 10 to 13Real code in Python. First projects that another person can actually run.
- Ages 14 to 16AI and machine learning, own datasets, work that goes in front of real users.
- Ages 17 to 18Portfolio, 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.
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 2Scope honestly against the time left. Most ideas get cut down here, and that is the useful part.
- Weeks 3 to 6Build the smallest version that genuinely works, with the repository open from day one.
- Weeks 7 to 8One real user, then fix what tripped them up.
- Final weekREADME, 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.
Preparation, and the follow-through afterwards
The weekend is easy to sign up for. The four weeks afterwards are where the value actually is.
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
The build ability an event assumes you already have.
Python and AI classes for kids and teens
Beginner
Vibe coding, used properly
All levels
Build machine learning models in Python
Intermediate
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,499 per monthMini batch
3–4 students. More airtime per student.
₹2,999 per monthOne to one
1:1. The usual choice for a project with a deadline.
₹7,500 per monthPrices are per month and shown per region. Hackathon entry is usually free and is arranged by you directly with the organiser. See full pricing for every subject and tier.
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.
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.
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.
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.