How to show off a hackathon project after the hackathon ends

4 min read

You spent thirty-six hours building something, maybe won a track, took the photo with your team. Then the event ends and the project lives on a Devpost page that nobody visits again. The work was real. The place you put it just went quiet.

Devpost is an archive, not a portfolio

Devpost is great during judging. After that it is one submission in a long list, styled exactly like everyone else's, and found by no one. It was built for the event, not for you. Your project deserves a home you actually control.

What to keep from each hack

• The demo video. Your single best asset. People watch a 60-second demo before they read anything.
• Two or three sentences. The problem you picked and what you built in the time you had.
• The repo and your role. Especially if it was a team, say what you owned.

Pull these out while you still remember the details. A month later the specifics are gone.

Put all your hacks on one page

Three hackathon projects on one clean page tells a better story than three separate Devpost links nobody opens. It shows range, and it shows you can ship under pressure, which is the exact thing people are trying to find out about you.

Then reuse it

Drop the link in your resume, your applications, your X bio. The project keeps working for you long after the prize table is packed up.