Schedule Friday, Feb 19th
  • 6:00pm - 7:00pm

    Opening Ceremony

  • 7:00pm

    Hacking begins!

    Team formation will also occurs at this time

  • 8:00pm - 9:00pm

    Music Hour

    Come into the #music-hour channel and listen/suggest some jams!

Saturday, Feb 20th
  • TBD

    Additional Workshops and Activities

  • 12:00pm - 1:00pm

    Pitt CSC Workshop

    How to API with Justin Kramer and Dylan Feehan

  • 1:00pm - 2:00pm

    Cigna Workshop

  • 2:00pm - 3:00pm

    Women's Coffee Hour

  • 4:00pm - 5:00pm

    Show and Tell Hour

  • 5:00pm - 6:00pm

    Music Hour

    Come into the #music-hour channel and listen/suggest some jams!

Sunday, Feb 21th
  • 9:00am

    Submit to Devpost/End of Hacking

  • 10:00am - 11:30am


  • 12:00pm

    Award Ceremony

Hackathon Sponsors


Student Life

Video Game

Health and Fitness

Social Good




NSIN Challenge

IEX Cloud Challenge

Devpost Achievements

Submitting to this hackathon could earn you:




Judging Criteria

  • TRACK: Student Life
    A project attempting to improve students' day to day activities in and around campus.
  • TRACK: Video Game
    A project that has some gamification aspect or is a video game.
  • TRACK: Health and Fitness
    A project which has applications mental health, diet and nutrition, exercise regimens, etc.
  • TRACK: Social Good
    A project which aims to address some common or social issue relevant to most people. Examples include clean and renewable energy, literacy, access to basic needs such as food, water, and shelter, etc.
  • TRACK: Humor
    A project that makes you laugh. These can be comedic in nature or just outright weird.
  • TRACK: General
    A project that doesn't quite fit into any other category.
  • TRACK: Beginner
    A project whose team is composed of beginner programmers.
  • Focus and Usefulness
    How well does this team and their project practically approach their category or categories? For General, think solely on the practical applicability of their project. For Beginner, think about the skill level of each team member.
  • Originality
    Did the team develop something novel, or approach something in a fresh and new way?
  • Progress and Learning
    Did the team stretch themselves technically? The team could have used a new tool or language, gone beyond the comfort zone of their technical ability, or put in a significant amount of man-hours developing their project.
  • Execution and Presentation
    How well did the team present their project? How well designed is the project in terms of user experience and completion?
    What does the Weather Mean to the Warfighter? Build a data dashboard that can serve as an operational decision-making tool for operational commanders. Aggregate publicly-available oceanography and meteorology information sources.

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

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