Code for Impact is a mission-driven hackathon hosted by Rutgers Muslim Tech Collaborative, bringing together builders, designers, and visionaries to create technology that addresses real-world challenges.
In just a few hours, teams of 4 will design and prototype solutions across three high-impact tracks:
- ๐ฑ Climate: sustainability, carbon tracking, and environmental action
- ๐ฅ Health: access to care, mental health, and healthcare equity
- ๐ Disaster Response: tools for displaced communities, crisis navigation, and resilience
This isnโt just about coding, itโs about building what actually matters.
We provide:
- Mentorship from experienced builders
- A collaborative, high-energy environment
- Real opportunities to turn ideas into something bigger
Come build something meaningful.
Requirements
Each team must submit the following on Devpost:
Required
- A clear problem statement and solution statement
- A detailed solution overview
- A working prototype built with code
(UI/UX tools like Figma are allowed, but your final submission must include functional code) - A 2โ3 minute demo video showcasing your project
- A short explanation covering:
- Who this helps
- Why it matters
- How it could scale
- How you built it (tech stack + team work distribution)
- A GitHub repository link
- A live demo link
- A future roadmap outlining next steps and potential growth
Prizes
Overall Winner
Sponsor Prize
Health Track
Sponsor Prize
Disaster Track
Sponsor Prize
Climate Track
Internship and Sponsor Prize
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Azra Bano
Katie Parrish
Matthew Drews
Alveera Munshi
Asad
Hannan Shah
akib mahdi
Walmart Global Tech
Michael Y
Google
Judging Criteria
-
Impact & Relevance (30%)
How clearly does the project address a real-world problem? Is the problem meaningful and important, especially within the chosen track (health, climate, disaster)? Does the solution have potential to create real impact? -
Creativity & Innovation (20%)
Is the idea original or uniquely approached? Does the team demonstrate creative thinking or novel use of technology? Does the solution stand out from typical or obvious ideas? -
Technical Execution (20%)
Is there a functional prototype built with code? How well does the technology support the idea? Is the implementation thoughtful and appropriate, even if simple? Complexity is not required โ clarity and functionality matter more. -
Feasibility & Scalability (15%)
Could this realistically be developed further beyond the hackathon? Is the solution practical and usable in real-world scenarios? Does the team show a clear path to growth or deployment? -
Presentation & Clarity (15%)
Is the idea communicated clearly and effectively? Does the demo pitch explain: the problem the solution the impact Is the pitch engaging and easy to understand?
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.