Top 5 Tips to Win the FutureStack GenAI Hackathon

Your winning strategy for $15,000 in prizes and career opportunities

Ajeet Singh Raina

30 Sep 2025 — 7 min read

The FutureStack GenAI hackathon is offering over $15,000 in cash prizes, plus interview opportunities at Cerebras and Meta. With competition from developers worldwide, how do you give your project the winning edge? After diving deep into the judging criteria and hackathon rules, here are the top 5 strategies that will maximize your chances of taking home a prize.

Here's the deal-breaker: To qualify for any cash prizes or interview opportunities, you MUST use at least one sponsor technology. This isn't optional—it's mandatory.

You have three options:

Cerebras API – Build with the world's fastest AI chip for lightning-fast inference and training. Perfect if you're working on compute-intensive AI applications that need serious speed.

Meta's Llama – Leverage open-source large language models to create impactful generative AI applications. Ideal for chatbots, content generation, code assistants, and innovative AI-powered tools.

Docker MCP Gateway – Show creative use of Docker MCP Gateway. Great for projects that emphasize scalability, deployment, or novel architecture patterns.

Pro Strategy: Pick the technology that aligns with your team's strengths and your project idea. Don't force a technology just because you think it's "trendy." The judges are looking for meaningful integration, not superficial implementation. Study the Resources section documentation before the hackathon starts so you hit the ground running.

Bonus move: If you can naturally incorporate multiple sponsor technologies, you might catch the judges' attention across multiple tracks. Just ensure each integration adds real value.

Tip #2: Master the Triple Threat Submission

Your submission needs three critical components, and all three carry equal weight:

1. A Clean GitHub Repository with Visible Commit History

The judges will review your code and commits. This means:

Make regular commits throughout the hackathon to show progressive development
Use clear, descriptive commit messages
Organize your code professionally with proper folder structure
Include comments where necessary

Red flag to avoid: A single massive commit at the end looks suspicious and suggests the work wasn't done during the hackathon.

2. A Crystal-Clear README File

Your README is often the first thing judges see. Make it count:

Start with a compelling project description that explains the problem you're solving
Include setup instructions so judges can actually run your project
List the technologies used (especially sponsor tech!)
Add screenshots or GIFs showing your project in action
Explain your architecture and key technical decisions
Credit any open-source libraries, APIs, or resources used

Template tip: Look at winning hackathon projects from previous competitions to see what excellent READMEs look like.

3. A Compelling 2-Minute Demo Video (This is Mandatory!)

Many participants underestimate this, but your demo video is crucial:

Keep it to exactly 2 minutes—respect the judges' time
Start with the problem statement (15-20 seconds)
Show your solution in action (60-75 seconds)
End with impact and future potential (15-20 seconds)
Use screen recording software and ensure audio is clear
Show real functionality, not just slides

Extra credit opportunity: While deployment is optional, deployed projects score bonus points. If you can show a live URL in your video rather than just localhost, you'll stand out.

Tip #3: Build a Balanced Team of 2-4 Members

Solo projects are allowed, but teams of 2-4 members have distinct advantages:

Why team size matters:

Multiple skill sets mean stronger execution across technical implementation, design, and presentation
Parallel development speeds up progress during the intense 7-day timeline
Different perspectives lead to more creative solutions
Workload distribution prevents burnout

The ideal team composition:

At least one strong backend/AI developer (to handle the sponsor tech integration)
One frontend developer or UI/UX person (for aesthetics and user experience)
Someone who's great at communication (for the README and video)

Important eligibility note: All team members must be 16+ years old and officially registered. Make sure everyone completes the registration form before you start collaborating.

Team coordination tip: While the hackathon is fully online, you can coordinate with your teammates through any platform you prefer—Discord, Slack, Zoom, whatever works. Just ensure all members are registered and your collaborative work happens during the hackathon period.

Join Cerebras Discord

Tip #4: Excel Across Multiple Judging Criteria

Projects are evaluated on six dimensions. Winning teams don't just nail one area—they perform well across most of them:

Potential Impact (High Priority)

Address a meaningful real-world problem. Generic "another todo app" won't cut it. Think about:

Who benefits from your project?
What specific pain point does it solve?
How big is the potential user base?

Creativity & Originality (High Priority)

Novel ideas get noticed, but even familiar concepts can win if executed creatively:

Put a unique spin on the sponsor technology
Combine technologies in unexpected ways
Solve an old problem with a fresh approach

Technical Implementation (High Priority)

Your project must actually work:

Test thoroughly before submission
Handle edge cases and errors gracefully
Show clean, maintainable code
Integrate sponsor tech meaningfully (not as an afterthought)

Learning & Growth (Medium Priority)

First-time builders and teams learning new technologies get special recognition:

Document your learning journey in the README
Mention if you learned new tools during the hackathon
Show how you overcame technical challenges

Aesthetics & User Experience (Medium Priority)

Polish matters, especially for user-facing applications:

Create an intuitive interface
Pay attention to visual design
Make interactions smooth and logical
Test with real users if possible

Presentation & Communication (Medium Priority)

Clearly explain your project:

Write a professional README
Create an engaging demo video
Articulate your technical decisions

Winning formula: Excel in the high-priority areas, perform solidly in medium-priority areas. Projects that are technically impressive but poorly presented often lose to slightly less technical projects with excellent communication.

Tip #5: Play by the Rules (And Maximize Your Advantages)

Understanding what's allowed—and what isn't—can make or break your submission:

What You CAN Do:

✅ Pre-hackathon planning – Sketch ideas, plan architecture, create mockups before the event starts
✅ Use AI tools – ChatGPT, GitHub Copilot, Claude Desktop and other AI assistants are fair game
✅ Leverage open-source – Libraries, APIs, frameworks, Creative Commons media are all allowed
✅ Include hardware components – Optional but acceptable if it enhances your project
✅ Attend workshops and mentoring sessions – Take advantage of sponsor engineer access

What You CANNOT Do:

❌ Submit pre-existing work – All core development must happen during the hackathon (Sept 29 - Oct 5)
❌ Work without registering – Every team member must complete the official registration
❌ Plagiarize or misrepresent – Will lead to immediate disqualification
❌ Skip the demo video – It's mandatory, not optional

The Smart Strategy:

Before the hackathon (Sept 1-28):

Form your team and ensure everyone registers
Study sponsor technology documentation
Sketch out 2-3 project ideas
Set up your development environment
Plan your architecture and tech stack

During the hackathon (Sept 29 - Oct 5):

Start coding immediately—don't waste day 1 on endless planning
Make regular GitHub commits to show progress
Attend sponsor workshops to learn implementation tips
Test early and often
Reserve the last day for polish, README, and video creation

Golden rule: Treat the hackathon as a sprint, not a marathon. Scope your project to something achievable in 7 days. An excellent execution of a focused idea beats a half-finished ambitious project every time.

Don't forget: Post about your hackathon project on social media and tag the sponsors. Ten participants will win exclusive swag packs through a raffle. It's free marketing for your project and a chance at extra prizes!

Your Action Plan

Register now if you haven't already (must be 16+ years old)
Study the sponsor technologies using the Resources section
Form or join a team of 2-4 members (or go solo if you prefer)
Brainstorm project ideas that use at least one sponsor technology meaningfully
Plan your submission strategy around the judging criteria

Remember: The winning projects typically excel in technical implementation, solve real problems, and communicate their value clearly. Focus on building something that works well, looks polished, and makes judges say "I would actually use this."

The FutureStack GenAI hackathon runs from September 29 to October 5, 2025. Over $15,000 in prizes awaits, along with interview opportunities at Cerebras and Meta. Are you ready to build something amazing?

For Docker-specific resources, do check out the below links:

Docker Documentation: Get familiar with Docker basics and advanced features.
MCP Catalog and Toolkit documentation
MCP Gateway documentation
Download Docker Desktop
Video Tutorial

For full terms and conditions and to register, visit WeMakeDevs FutureStack Hackathon

Top 5 Tips to Win the FutureStack GenAI Hackathon

Ajeet Singh Raina

Tip #2: Master the Triple Threat Submission