This is NOT a feature delivery sprint.

This is about:

• Trying bold ideas
• Learning new technologies
• Solving meaningful problems
• Working across functions
• Exploring AI
• Thinking differently

And most importantly… having fun while building

For 3 days, we pause “business as usual” and switch into builder mode — experimenting, learning, collaborating, debating, designing, coding, breaking things, fixing things, and hopefully creating something awesome together.

For these 3 days — exploration IS the work.

Team Formation

• Team size: 3–7 members
• Teams can include Developers, QAs, Designers, PMs, and Program Managers
• Maximum 4 developers per team
• Every individual should be part of one team only

Cross-functional Collaboration

You are strongly encouraged to involve members from other teams as the best solutions are rarely built in isolation. Lean on members from CE / J&I, Business, Growth, Finance, People Team for:

• Domain knowledge
• Business insights
• User understanding
• Demo storytelling
• Presentation structuring

These members will NOT count toward the 3–6 member limit.

Timeline

• Hackathon Starts: 10th June afternoon
• Hackathon Ends: 12th June afternoon
• Final Presentations: 12th June, 3 PM – 5 PM
• Results Announcement: 12th June, 5:30 PM

Every team gets:

• 7-8 minutes for demo/presentation
• 10 minutes for Q&A

The problem statement/topic will only be revealed on 10th June.

Deliverables

Each team must present:

1. A working prototype/solution
2. A short presentation (2–5 slides) covering:
• What problem you solved
• Who you solved it for
• What you built
• Key workflows/demo
• Technical & architectural decisions
• What you learned

Important:

 It is completely okay if your solution is incomplete, rough around the edges, or partially working — as long as the thinking, direction, and learning are strong.

We value ambitious attempts more than safe and tiny improvements.

AI Usage

Use of AI coding, design, research, testing, or prototyping tools is highly encouraged.

However, teams should clearly explain:

• What was AI-generated
• What decisions were made by the team
• What challenges were solved manually

The goal is not just using AI — but learning how to build effectively with it.

Get your teams ready.

Let’s build something exciting together. #BeUnstoppable