DevFest is an annual week-long workshop series and hackathon held at Columbia University.

Hosted by Columbia's largest technical student group, ADI, DevFest has always served as an opportunity for students from across the Columbia community with all experience levels to come together and learn about technology.

No experience is necessary, and the only requirement for attendees is that they are affiliated with either Columbia or Barnard (students, faculty, etc.).

Visit adicu.com/devfest to register and join the DevFest '22 Discord server, where we will be continuously posting updates.

Requirements

Submitted hacks must include:

  • Product source code or design material, and

at least one of the following:

  • Live demo
  • Product graphics (i.e. screenshots of a prototype)
  • Video of the hack being used
  • Video of the team explaining the hack (possibly w/o a prototype)

If your team chooses to do a live demo, join the Zoom meeting adicu.com/df22-zoom at 4 pm on Sunday.

If you choose to submit a video hack, please upload your video to YouTube, unlisted, and email the link to [email protected] with the subject "DF22 Hackathon Submission: <Team Name>" before 4 pm ET on Sunday, March 27th.

Teams who have submitted a hack but do not demo their project will not be judged.

Hackathon Sponsors

Prizes

$2,000 in prizes
First Place Prize
1 winner

$750 Cash + $250 in DigitalOcean Credits

Runnner-Up Prize
1 winner

$500 Cash + $250 in DigitalOcean Credits

Beginner Prize
1 winner

$250 Cash + $250 in DigitalOcean Credits

Best Saas Prize
1 winner

$250 Cash + $250 in DigitalOcean credits

Best Design Prize
1 winner

$250 + $250 in DigitalOcean credits

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Anthony Krivonos

Anthony Krivonos
Software Engineer @ Lyft

R.A. Farrokhnia

R.A. Farrokhnia
Award-winning Columbia University Faculty with joint-appointments at the Schools of Business & Engineering.

Ryan Bubinski

Ryan Bubinski
Co-Founder @ Codecademy

Judging Criteria

  • Completeness
    The extent to which the hack has been tangibly created. Hacks with working webpages, GitHub repositories, and (if needed) prototypes are strongly favored.
  • Capability of solving a real-world problem
    How feasible is the hack in solving the problem it is targeting, and how well does it do so?
  • Creativity
    How original is the solution compared to other hacks and products available on the market?

Questions? Email the hackathon manager

Tell your friends

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.