The Hackathon
Last month, I had the opportunity to sit on the judging panel of a global hackathon sponsored by KendoReact and the DEV Community — and let me tell you, it was an eye-opener from both sides of the table. Here are some tips I picked up that might help future judges and participants make the most of the hackathon experience.
For Judges: How to Be Fair, Fast, and Focused
Define What a 10 Looks Like
Before diving into evaluations, it's crucial to have a clear benchmark for a top score in each category. What does “excellent” mean for design, functionality, innovation, or use of tech? If it's vague in your head, it'll be vague in your judging.
Know the Bottom Line
Every hackathon has hard requirements—whether it's using a specific tool or including at least 10 components. Keep these in mind at all times. A project missing these baseline rules simply isn't eligible to win.
Don't Get Lost in the Details
If a submission clearly doesn't meet the theme or key requirements, move on. Don't spend valuable time dissecting a project that doesn't check the fundamental boxes.
Speed = Fairness
As a judge, your speed matters more than you think. Delays can mean missing standout submissions. Be decisive and keep moving—you can always come back to double-check your favorites later.
For Participants: Make It Easy to Love Your Project
Make Judging Easy
This can't be overstated: judges are scanning dozens of entries. Help them help you.
Include a demo link. No demo = no review. Seriously.- Simplify sign-ins. Include test credentials in the signup form so the judge isn't stuck in account purgatory. If we can't get in, we move on.
Keep Docs Short and Focused
Your technical document is not a novel. Be clear and concise.
- Start with key features of the app so judges know what to look out for.
- Highlight tech stacks used: framework, state management, testing, or CI/CD involved. This shows awareness of professional practices—huge points for that.
Add Visual Cues
Drop at least one image in your DEV blog. This gives judges a quick preview when hovering over your submission. If design is a judging criteria, a poor or missing image might get your project skipped.
Be Wise About Scope
No one expects a complete enterprise-grade platform in 48 hours. The best entries are those that choose their scope wisely, focus on core features, and polish them well. A strong, finished MVP is far more impressive than an unfinished ambition.
Final Thoughts
Being a judge gave me a whole new level of respect for both sides of a hackathon. Whether you're submitting or scoring, taking perspective for the other party and making their lives easier can make all the difference.
To all the future hackers and judges out there—good luck and hack smart! 💻🚀
P.S. Clears throat dramatically… and yes, I'm absolutely taking a moment to show off my shiny exclusive judge badge. 😎
Did you find it helpful?
