About the challenge

The Historically Black Colleges and Universities (HBCU) Hackathon at Lilly is a targeted event for HBCU students interested in exploring STEM opportunities at Lilly. From March 3-April 17, we invite students to join the virtual hackathon. This event provides students at HBCUs the opportunity to flex their coding skills by solving a problem statement provided by Lilly and developing a solution using tools currently being utilized at Lilly. Students will be able to submit their solutions anytime during the hackathon period. During the event, students will have the ability to connect with recruiters to learn more about Lilly and potential positions. This opportunity is open to all majors and no previous programming experience is required to participate.

HBCU Hackathon at Lilly Highlights:
  • $30,000 in awards
  • Introduction to Lilly
  • Networking opportunities with Lilly leadership
Check if you are eligible

This hackathon is only open to active students at a Historically Black College or University (HBCU) who are legal residents of the 50 United States (including the District of Columbia). All registrants are also required to register for the event on the Lilly HBCU Hackathon Landing page.

Rules and Eligibility:
  • This event is open to all students who are currently enrolled at an HBCU
  • Register in teams of up to five (5) individuals
  • Teams may register any time during the Hackathon event

Requirements

What to Build

Build or update a software application that helps solve one of the problem statements using at least one of the following tools that Lilly software engineers use.

Problem statements
  • Highlighting safety narrative through AI/ML
    The Global Patient Safety process for creating safety reviews involves manually reading case narratives to identify and classify data especially when multiple events exist in the case. This manual process is both time-consuming and resource-intensive. How may we improve this process? Here are sample patient narrative data.
  • Introducing a web-based medicine information sheet
    Here is the medical insert sheet for our Mounjaro drug. It is difficult to read and understand. How might we convey the same information in a more user-friendly way? 

What to Submit
  • Project. Share a link to your live project for the judges to test it out. 
  • Video. Include a demo video (about 3-5 minutes) that introduces your team and project to the world. The video must highlight your project’s features and show how to interact with Eli Lilly in your project.
  • Code. Provide a URL to your code repository for judging and testing. Give access by making it public or sharing access with LillyHBCUHack@Lilly.com and testing@devpost.com.

 

Hackathon Sponsors

Prizes

$30,000 in prizes
Grand Award
1 winner

$10,000

*Payable to the winning Entrant's HBCU. It will be the responsibility of the HBCU to allocate the Award among the participating members, as the HBCU deems appropriate.

Best Solution to a Problem Statement
2 winners

$5,000

*Payable to the winning Entrant's HBCU. It will be the responsibility of the HBCU to allocate the Award among the participating members, as the HBCU deems appropriate.

Honorable Mentions
10 winners

$1,000

*Payable to the winning Entrant's HBCU. It will be the responsibility of the HBCU to allocate the Award among the participating members, as the HBCU deems appropriate.

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

A panel of qualified judges

A panel of qualified judges
To be announced...

Judging Criteria

  • Business Value
    How well does the solution address the problem statement? 
  • Level of Innovation
    Is the solution “out-of-the-box” and hasn’t been pulled off before? Is the solution something new and unique?
  • Realistic Capability
    Does the solution present itself as “plug and play” for Lilly/ How difficult would it be for Lilly to implement this solution and gain value from?
  • Technology
    Does the project demonstrate quality software development and use of the required tools? What level of engineering/coding skills were shown? Were best practices followed?
  • Design
    How well is the user interface designed? What elements are introduced for user design? How well are they executed?
  • Presentation
    How was the presentation of the solution executed? Was it easy to follow?

Questions? Email the hackathon manager

Tell your friends

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