
Make a team
Sign in to start a team, or join a teammate with their join code.
Teams show up with a project they started months ago, post it on LinkedIn and go home with a Nintendo Switch. This one gives you a company problem, a live leaderboard and $20,000 in cash prizes.
Sign in$5,000 to the winner of each track, plus $100 for the best video
Evans Lab 1008
Submissions close. Closing ceremony at 12 PM ET in Hitchcock Hall 131
Your guide from kickoff to the final.
LeaderboardPlay Mech Royale yourself in the browserStatus page
$ git log --oneline | wc -l214 commits$ git log --reverse --format=%cr | head -15 months ago$ cat README.md | head -1Built in 36 hours at a hackathon
Half the room walks in with a project they built months ago.

Thrilled to announce our team took 2nd place this weekend! #hackathon #innovation #grateful

Give your code a real company problem.
252 commits in 42 hours
FriSatSun
Nothing here is a matter of opinion, and nobody can hide.
$20,000
in total cash prizes
Compete for actual money and put your work in front of companies looking for people who can build.
Each track pays $5,000 to the winner. Winner takes all. Second place gets nothing.
One side prize is our call, not the scoreboard's: $100 for the best video about your weekend. Upload it to YouTube as Unlisted and enter it from your team page by Nov 22 at 11 AM ET.
A winning result can come from anyone. Bring yours.
You can be virtual for the whole thing. Kickoff and the closing ceremony are in person if you want to come. Build from wherever you work best.
Anywhere
Work remotely or grab a table. The leaderboard and the team chat stay open the whole way through.
Nov 20
Not a minute before.
Every track opens online at the same moment, so you can start from anywhere.
Nov 22
The leaderboards freeze and the top team in each track gets paid.
Every track is a problem a real company has today, and that company decides how it is measured.
They bring the problem. You bring the fix.
Winner takes $5,000
Blast Radius
Winner takes $5,000
Anything not answered here, email hi@joinbuilders.org.
Any current student, at any school in any country. Register with your school email.
Up to two people, or enter on your own. Each person is on one team.
Anywhere. You can be virtual for the whole thing, from kickoff to the final. Kickoff and the closing ceremony are in person at Ohio State, but you don't have to attend either one to compete or to win.
Every track opens online at 6:00 PM Eastern on Nov 20, the moment kickoff starts. Sign in on this page and open a track for its brief and starter files. No team sees a problem before then.
Enter as many tracks as you like. One team can win more than one.
Use any tools you like, AI included, unless a track's page says otherwise.
Every submission is scored automatically, and the live leaderboard shows each team's best practice score. Each track's page gives its metric, its tie rule and how many practice runs you get an hour.
Submissions close at 11 AM Eastern on Nov 22. Your final entry for a track is the submission you pick, or your best-scoring one if you don't pick. See your track's page for how its final is scored. Organizers verify the top results before announcing them.
The best final score in each track wins $5,000, and second place gets nothing. Teams anywhere in the world can win. Winners are paid online, in the room or not.
Anything built in this hackathon must be released under the MIT License. Builders may show your team's name, demo, screenshots and project description to promote the Buildathon.
You can use open-source libraries and code you wrote before the weekend. If your track takes a repository, name them in its README.
Your entry should be your team's own work. Excessive reuse of code, another team's entry included, may result in disqualification, at the organizers' discretion.

Explore the four tracks and open the ones you want to build for. You can enter as many as you like.

Hand in your entry on the track page. Your team’s list shows your place in the queue as the scorer builds and scores it.

Open your submissions on the track page to read the score and feedback. If an entry is rejected, you’ll see why. Your best score stays.

Find your team on the leaderboard. Each track has its own board. Practice standings update every few seconds. Only the final decides the prize.
Expand a board to see every team’s rank and best score. The board names the metric and tells you which direction is better. An earlier submission wins a tie.
The Baseline row is a simple reference entry’s score. Teams above it have beaten it. At the cutoff each board is sealed until its final results are revealed at the ceremony; the practice standings then fold beneath them.

Sign in to ask a question in leaderboard chat, or email hi@joinbuilders.org if it is private. For a scoring delay, check your track’s queue on the status page.

Submissions close Nov 22 at 11 AM ET. Your final entry locks then.
Hand in a GitHub repository with a Dockerfile at its top. 6 submissions an hour.
Final: The top 32 teams on the practice board play a qualifying round, and the top 16 play a 64-match final series on new seeds (last 4 live). The series alone decides.
Hand in a GitHub repository with a Dockerfile at its top. 5 submissions an hour.
Final: Your chosen commit is rebuilt and timed 3 times on about 60 million new events, and at least the 30 fastest entries are retimed in interleaved rounds across 3 fresh final datasets on one idle machine. Aim for under about 60 seconds in practice: if any final run goes over 3 minutes, you get no final score.
Hand in the S3 folder of one attempt. 1 submission an hour, 20 scored attempts in all.
Final: The board at the cutoff is final: your best attempt keeps its score, and nothing new is graded at the cutoff.
Hand in a GitHub repository with a Dockerfile at its top. 4 submissions an hour.
Final: Your chosen commit is scored on unseen changes, and the top entries are rescored one at a time on one idle machine. Only the final counts.
The photo gets likes. Nobody ever uses what you built.
You don't start a company and you don't get a job. The grand prize is a Nintendo Switch.
First commit: Friday, 6:04 PMLessMore
94 of 100 unseen test cases passed
Each track is a real company problem with a published scoring rule. Find the cause of a failed build: accuracy on the same 100 test cases, higher wins.
Your code runs on test cases you have never seen. Nobody pitches and nobody grades a slide.
Every submission updates the leaderboard. Build from anywhere and talk with the other teams in live chat while it happens.
First place is the highest score, and the score is on the board for everyone to read.
Find what broke the build
Make something a company could put to work. Your solution could start a hiring conversation.
Mech Royale
Winner takes $5,000
CAD De-ID
Winner takes $5,000
Shopping Sessions
Have a problem worth racing on? Sponsor a track.
Builders