Back to all updates

4 months ago

🚀 Level Up Your Build: How to Wow the Judges

Hey Builders!

As a veteran of more hackathons than we have fingers (and toes), we know the feeling. It’s 3:00 AM, the API is finally behaving, and you’re wondering: “How do I actually win this thing?” With a powerhouse model like Amazon Nova at your fingertips, the floor is high, but the ceiling is nonexistent. To move from "cool prototype" to "winner’s circle," you need to think like a judge. They aren’t just looking for code; they’re looking for a story, a solution, and a spark.

Here is your survival guide to standing out in the Amazon Nova Hackathon.

🧠 1. The Name: Give it a Soul

Please, for the love of all things binary, don’t let an LLM name your project. 

  • The Tip: Pick a name that sounds like a real startup. Use a verb, an inside joke, or a metaphor.

  • Example: Instead of "Nova UI Automator," try "GhostCursor" or "SwiftStep."

📝 2. The Text Description: Sell the "Why"

Judges might read your description before watching the video. If it’s just a list of libraries, you’ve lost them.

  • The Hook: Start with the problem. "Every day, 5,000 logistics managers struggle with X..."

  • The Nova Factor: Be specific about why Nova was the secret sauce. Don't forget to tell judges all the required tools you used.

  • Structure: Problem → Solution → Nova’s Role → Impact.

🎥 3. The Demo Video: The 3-Minute Masterpiece

This is your "Shark Tank" moment. Use your 180 seconds wisely.

  • Show, Don't Just Tell: Don't spend 2 minutes on slides. Get to the UI/CLI within the first 30 seconds.

  • The "Golden Path": Show one clear, successful use case from start to finish.

  • Pro Tip (The "Fail-Safe"): If your live demo is prone to "demo demons," record a screen capture and voiceover it. It’s much cleaner than fumbling with a live mic.

  • New Tip: If you're doing Voice AI, show the user's reaction! Seeing a person interact naturally with Nova 2 Sonic is way more impactful than just hearing a waveform on a screen.

  • Don't forget: Include that #AmazonNova hashtag!

💻 4. The Code Repo: Don't Be a Mystery

A messy repo says "I finished this 5 minutes ago." A clean repo says "I’m a pro."

  • The README is your resume: Include a clear Setup.md or a "Quick Start" section. If the judges can't get it running (or at least understand the architecture) quickly, they’ll move on.

  • (Optional if you have extra time) Architecture Diagram: Drop a simple diagram showing how Nova interacts with your agents or MCP tools. It proves you understand the "Agentic" part of the challenge.

🏆 5. The Bonus Prize: The "Builder" Advantage

Don't skip the builder.aws.com blog post. It’s not just "extra credit"—it’s your chance to show the judges that your project has legs in the real world.

  • Focus on Community: Who does this help? A small business? Students? Doctors?

  • The Roadmap: Judges love to see that you’ve thought about "Day 2." How would you scale this?

 

⚡ Quick Tips for Each Category

  • Agentic AI: Focus on reasoning. Show the agent making a decision or "pivoting" when it hits an obstacle.

  • Multimodal: Don't just "describe an image." Make Nova interpret something complex, like a handwritten note or a fast-paced video clip.

  • UI Automation (Nova Act): Choose a workflow that is notoriously annoying (like filling out 10-pages of forms) to maximize the "wow" factor.

  • Voice AI: Zero in on latency and tone. If it feels like a real conversation, you'll really stand out.

 

Final word of advice: Build something you actually want to exist. Your passion will show through in the demo.

Now, stop reading this and get back to building! We can’t wait to see what you create with Nova.