codeLinc 11 with Lincoln Financial & AWS

Overview

For 11 years, Lincoln Financial has hosted codeLinc, a 24-hour coding challenge. This event provides high school and undergraduate students with an opportunity to solve technology challenges under the guidance of Lincoln's veteran developers. Participants will showcase their coding and programming capabilities and stretch their skill sets while working on mobile development projects. This hackathon encourages registrants to develop innovative technical solutions that address community challenges faced by non-profit recipients. The challenge emphasizes creating functional, intuitive, and secure mobile applications using provided project templates and open-source development tools. Participants will gain real-world experience, mentorship, and the chance to win significant cash prizes. The event fosters creativity and problem-solving skills in a competitive yet supportive environment, aiming to produce solutions that can make a tangible impact.

What to build

Participants must develop a mobile application in alignment with the project templates provided. The application should be a completed solution or working application at the time of submission, developed solely as part of this challenge, and the sole work of the registrant. It is permissible to use open-source development tools, but the application must not contain any third-party proprietary code and must not infringe any third-party rights or laws. Solutions employing components incurring future licensing costs must be prominently documented.

Prizes

Key dates

• Submissions OpenOctober 03, 2026 at 11:30 AM EDT
• Submissions CloseOctober 04, 2026 at 12:00 PM EDT
• Judging BeginsOctober 04, 2026 at 10:30 AM EST
• Winners AnnouncedOctober 04, 2026 at 12:00 PM EDT

Eligibility

Participants must be students aged 16 years or older. The competition is open to individuals from all countries/territories, excluding standard exceptions. Only one entry per team is permitted. This challenge is not open to non-US residents for prize acceptance.

How to enter

1. Read the requirements.
2. Accept the rules and register for the event via the Jotform link.
3. Develop a mobile application in alignment with the provided project templates.
4. By October 4, 2026, 10:30 AM EST, submit a project packet including the mobile application, a link to the working source code, application login credentials, a written description, and a brief demonstration.
5. Registrants will be provided with a URL to the third-party vendor website or an email address to submit their Entry. Before submitting, registrants may be required to register and/or create a profile on the third-party site and agree to its terms and conditions.
6. Be available on-site to demonstrate the application starting at 10:30 AM EST on October 4, 2026, for judging.

Submission requirements

• Mobile application or other programming project in alignment with the project templates provided.
• Developed solely as part of this Challenge.
• Sole work of the Registrant/team.
• Completed solution or working application at time of submission.
• Comply with the Official Rules.
• Presented and submitted in English.
• Content and supporting materials must be acceptable for all viewing audiences (no malicious, illegal, vulgar, offensive, or inappropriate content).
• Project packet submission by 10:30 AM EST October 4, 2026, including: mobile application, a link to the working source code, the application login credentials, a written description, and a brief demonstration.
• Prominent documentation of any components or plugins incurring future licensing costs.
• Demonstration and presentation by the entire team on-site, with a maximum of 5 minutes for presentation.

Judging criteria

• User Interface & Intuitiveness: Cohesive, logical UI/UX, ease of navigation/administration.
• Functional Requirements & Impact: Addresses challenge, solves a real problem.
• Solution Design & Innovation: Employs an innovative or creative approach.
• Demonstration and Presentation: Clear, effective, positive presentation; clear depiction of functionality.
• Does it Work?: Core functionality works, potential for organizational use.
• Technology Platform(s) Employed: Employs novel technology platforms, libraries, open-source, APIs.
• Security Accommodations: Description of how the application accommodates user security.
• Technical Creativity: Incorporates a novel approach or innovative solution.
• Architecture & Methodology: Touches upon application architecture; use of storyboarding or roadmapping.
• Complexity: Appropriate level of complexity, not overly simplistic nor unnecessarily complex.

Sponsors & partners

Resources

• Full Rules
• Register for the event
• Hackathon Manager Email