Why this works
Hackathons are the rare moment when engineers, designers, and PMs all stop and pitch their best ideas to each other. The energy is real, the demos are honest, and the work is finished in 48 hours. Recording the recap turns one weekend into a year of recruiting and engineering-brand content.
Who you'll feature
The winning team. Their demo is the headline.
Two runners-up. Different angles on the same theme show range.
The judges or sponsors. One reaction quote each.
How to capture it
Open MarketScale → Requests → New Request to every team an hour before demos. Three prompts:
What problem did you hack on?
What's the one trick that made it work?
What would you build next if you had another weekend?
Have each team self-record a 90-second pitch with screen recording for software demos.
For an in-person event, book an Onsite Video Booking for finals day. The crew gets the pitches, the judges, and the room.
Stitch the best pitches with a compilation video for a single recap reel.
Reuse it (the 1:10 framing)
One hackathon weekend becomes:
A 3-minute event recap.
A 60-second sizzle of the winning demo.
Three social cuts (one per top team).
A LinkedIn post from each team lead.
A blog post on "what we built in 48 hours."
A recruiting clip for engineering and design hires.
An internal demo-day session for the broader org.
A roadmap-input artifact ("these three ideas are going on the next planning offsite").
A conference-submission seed.
A pinned playlist on the engineering Channel.
Bundle the recap reel and team pitches into a Sales Team Materials Collection for engineering managers and recruiters.
Common mistake
Only featuring the winners. The runner-up demos are usually where the most original thinking lives. Give every team 90 seconds in the recap, and the engineering brand earns more credibility than picking one champion ever could.