Under the umbrella of HackDuke, we unite DKU students of all backgrounds to come together and create meaningful hacks in roughly 24 hours that change the intention and narrative behind how technology is used today. Come join us on September 9-10, 2023 to learn, collaborate, and code for good.
We believe hackathons are more than just about building cool projects. It’s also a place to discuss, share, and bring to life ideas that make a difference. Look forward to working with non-profits, coding alongside industry experts, and above all, collaborating with your peers to create something truly amazing!
Check out our website, notion.site, for Hackers Guide!
Requirements
Submissions are due on Devpost by Sunday, September 10 at 12:00 pm, though feel free to submit early. We recommend submitting by 11:00 am.
Only one submission is required per team (but make sure to add all team members to the submission). You must include videos, photos, or screenshots of the working product and a link to the source code (GitHub, etc.) of your project. You can submit the project in a team (of up to 4 people) or alone.
Your team must be present for in-person demos and judging unless specifically communicated with the organizing team (reach out to organizer sardor.akhmedjonov@duke.edu).
What should I build?
You can build a website, mobile application, API, or any other software product that aligns with one of our hackathon tracks (i.e., Education, Health, Finance, Environment).
Prizes
Main Prize
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
HackDKU Judges
Judging Criteria
-
Feasibility and Impact
How well does the hack fit the track theme? How well thought-out is the concept itself, with regard to both the problem it aims to solve and the solution that has been proposed? -
Innovation
How well does the hack approach the problem from a fresh perspective? Or, does the hack address a unique aspect of the problem that isn't already implemented or developed? -
Functionality
How well did the team translate their concept into a working prototype? Is the hack functional, and to what extent? Is it limited to a few examples or test cases, or were you able to operate the hack yourself and use it for its intended purpose? -
Overall Presentation
How was the overall presentation of the hack? Did the hackers have a prepared pitch, or was it more off-the-cuff? How convincing was the pitch? How well did the hackers understand the scope of their problem?
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.