Multiple AI hackathons across Indian cities this weekend are doubling as hiring funnels. With finals and showcases on August 21–22, final‑year students and early‑career builders can still make strong impressions. Arrive with job‑ready demos, crisp documentation, and a plan to discuss trade‑offs, reliability, and measurable user impact during live evaluations.
If you are choosing where to go, prioritise events with juries, mentor office hours, and structured shortlisting. Carry a 90‑second demo video, a clean GitHub repository, and reproducible setup notes. Shortlist two problem statements per track, align teammates early, and secure essential application programming interface credits or temporary compute before reaching the venue.

Snapshot below is updated 11:00 IST, August 21, 2026. Always recheck event portals for last‑minute changes, server‑time rules, and identity requirements. Reach reporting desks within the first hour, and follow local device policies for external drives, Wi‑Fi dongles, and GPUs. All times are local unless otherwise noted.
| City | Event | Date/Time | Registration | Notes |
|---|---|---|---|---|
| New Delhi | ACTS–Brainwave 2026 (MLH) | Fri, Aug 21, 2:30–10:30 PM | MLH link | On‑site check‑in |
| Chennai | Rockathon’26 Grand Finale | Sat, Aug 22, full‑day | Closed | Finalists only |
| Hyderabad | SPEC Industry Hack 2026 | Aug 22–23 | Portal | Campus‑led slots |
| Hyderabad | StackFlow 2.0 @ EPAM | Sat, Aug 22 | Closed | Workshops + demos |
Event pages confirm today’s Delhi hack day and Saturday finals in Chennai, with Hyderabad hosting a 24‑hour college hack and an AI builders’ workshop. Some listings show closed registrations or shortlisted access only; verify cut‑offs directly on the portals before travelling.
Ship retrieval‑augmented generation or agentic builds with an evaluation harness. Log latency, accuracy, hallucination, and cost per task. Add an admin analytics dashboard and safe‑mode fallbacks. State privacy posture, model choices, and observability clearly. Recruiters value reproducible repos, real usage telemetry, and a roadmap that balances reliability with speed.
Open with the user pain, then your measurable outcome. Demo flows live, not slides. Keep a one‑command setup, seed data, and a postman collection. Tag issues for next steps. Include a risks section covering bias, safety, and failure modes. Practice two follow‑ups: a deep‑dive and a time‑boxed elevator pitch.
Carry government ID, campus ID, power strip, and offline backups. Respect venue restrictions on external media and recording. Protect secrets using environment variables, not code commits. Confirm server‑time on portals before deadlines. Avoid unofficial forms or fees, and read privacy terms; decline uploads requesting unnecessary personal or biometric data.
If a slot is available, register now; otherwise, attend as a guest where allowed and network. Bring a polished demo, printed resume QR, and a crisp README. With thoughtful evaluations and clear metrics, even a short build can unlock shortlist calls next week. Stay safe, prepared, and focused on outcomes.