It's 9pm at the Pursuit office in Long Island City. Laptops snap shut. A team walks to the front of the room with two minutes to prove that the idea they started building at 7pm actually works. Not a slide about what it could do. A live link, opened in front of a panel of judges, that has to run.
Pursuit runs these hackathons about once a month because they do something a normal week of class can't. Give a Builder two hours, a hard deadline, and a team of people they've just met, and you find out what they can actually build. A Mini Hackathon isn't a break from the program. It's the program, sped up.
Here's the belief underneath all of it. Skill isn't proven by how much you know. It's proven by what you can build and put in front of other people. Mini Hackathons are where our Builders get to do exactly that.
Every Mini Hackathon runs on the same structure. Teams form at 6:30. They build relating to a theme from 7 to 9. Then everyone closes their laptops and demos in a two-minute lightning round. Somewhere in there is a hard rule: your build has to be deployed. A real, working link by the deadline, or it doesn't count.
Two hours is not enough time to feel ready. That's the point. There's no room to wait until you've watched one more tutorial or until the idea feels safe. You pick something, you scope it down until it's buildable, and you ship it. The building comes first and the confidence follows. That pressure isn't artificial, either. It mirrors the actual conditions of the work our Builders are moving toward: real deadlines, incomplete information, AI as a working collaborator, and a team you have to sync with fast. A Mini Hackathon rehearses those conditions in one night, so building under real constraints feels familiar long before a job depends on it.
The word "cross-cohort" is in the name for a reason. Teams aren't sorted by level or by who already knows who. They're mixed on purpose, so a Builder who started days ago ends up on the same team as one who's cohorts ahead, in L2 or L3+, with staff, alumni, and guests in the mix too.
This is the part people underestimate. At Pursuit, learning isn't one expert talking to a room of students. It runs in every direction at once. Builder to Builder, staff to Builder, and just as often Builder to staff. A newer Builder learns faster standing next to someone a few steps ahead than they would from any lecture. And the person a few steps ahead learns by explaining, deciding, and leading under pressure.
But what holds this together isn't the teaching. It's the community around it. On a cross-cohort team, a Builder meets everyone: other Builders, staff, alumni, guests. And over enough late nights and shared deadlines, people start to look out for each other, noticing when someone's off, celebrating when a project finally works, showing up for the weeks that have nothing to do with code. Nobody does this alone. That's not a byproduct of Pursuit. It is Pursuit.
A build that only its author ever sees isn't finished. So every Mini Hackathon ends with the work in public: demoed live, judged, and celebrated. Winners are displayed on the Pursuit Hack Wall of Fame.
The themes change, and so does what Builders make. For "Play," Builders turned out everything from games to interactive simulations. "Unlocked" produced tools like a benefit-flyer-to-video app aimed at helping more people claim what they're owed. "Capture the Flag" flipped the format into a cybersecurity challenge where Builders scored points by breaking AI chatbots, a live on-ramp to our cyber curriculum. And at "Summer in the City," the top prize went to a Choose Your Adventure app that builds you a custom NYC night out based on your vibe, your crew, and your budget. Around it: an NYC beach-day finder, a drone-flight game over city landmarks, and a summer concierge.
Who's watching is just as important. Our judges and partners come from real companies. That proximity is deliberate. When a Builder demos to someone who hires for a living, a skills exercise turns into something closer to a pathway. The work gets seen by the people who can open the next door.
None of this is separate from how Pursuit teaches. Learn by building. Everyone is a teacher and a learner. Real deliverables, in public, together. A Cross-cohort Mini Hackathon puts all of that in one room for one evening, so you can see the model work in a single night instead of over ten months.
We run them because they produce the thing that's hardest to teach and most valuable to have: proof, to a Builder and to everyone watching, that they can build something real before they ever felt ready to.
If you want to put your team in the room as judges, please contact amed.sylla@pursuit.org, and learn more about our program at pursuit.org/ai-native-program.
