Putting Technology to Work to Benefit North Carolina Communities

Lincoln Financial Group’s third-annual hackathon-style event where students from
North Carolina universities will have 24 hours to code real, working technology solutions
to solve a set of issues for a community non-profit organization.

View full rules


In person hackathon - participants may use Devpost and will present their application on Sunday, 10/23


Dave Goodrich

Dave Goodrich
Lincoln Financial Group

Judging Criteria

  • 1. App Design & Usability: User Interface
    • Does the UI of the app look professional or is it sloppy? • Is the application easy to use? • Does the workflow of the app make sense & intuitive? • Can application be administered by organizations with JA personnel with moderate technical expertise?
  • 2. App Design & Usability: Functional Requirements
    ● Is the application technically viable? ● To what degree does the application actually solve (some of) Junior Achievement's stated challenges? ● Will they use this tool?
  • 3. App Design & Usability: Solution Design & Innovation
    ● Is the application technically viable? ● Does the application approach a new problem, or look at an old problem in a new way (did the team think "out of the box")? ● How clever or innovative was the approach the team used to build the project?
  • 4. App Design & Usability: Demonstration and Presentation
    ● Was the team able to explain their idea and what the app actually did? ● How was the quality and cohesiveness of the delivery presentation visuals and demonstration?
  • 5. App Design & Usability: Does it work?
    ● Does the app work completely from start to finish? ● How many and how severe were any bugs encountered? ● Was anything in the app that wasn’t fully implemented? ● Did the team scope their app’s features well given the time frame of the Hackathon?
  • 1. Technology & Architecture: Technology Platform(s) Employed:
    ● The project is open-source or industry-leading (Apple/Google/.net), the data-set is open, team provided a good API support/documentation for others to pick up?
  • 2. Technology & Architecture: Technology & Architecture
    ● App incorporates established strong security protocols ie: 2-factor auth ● App allows users to sign in with a federated login provider (Google, FB, Twitter) ● App accommodates items such as authenticate new account via email, automated password resets
  • 3. Technology & Architecture: Technical Creativity
    ● To what degree does the application technology actually solve the current problem?
  • 4. Technology & Architecture: Architecture
    ● Application has multi-platform support (web / responsive / iOS / Android) ● The app uses the capabilities of the device it’s running on, for example location data through the GPS, biometric authentication, and motion sensors when appropriate.
  • 5. Technology & Architecture: Complexity
    ● Is the app technically interesting or difficult? ● Were there real technical challenges to surmount?