>>> Information on the Challenge is Available on the Resources Tab <<<
>>> Please note that per the codeLinc 7 Rules, this challenge is not open to non-US Citizens <<<
For the last 6 years, Lincoln Financial has hosted a 24-hour coding challenge where high-school and undergraduate students have an opportunity to solve technology-related problems currently affecting a Greensboro-based nonprofit organization. Under the guidance of Lincoln's own veteran developers, they have had the chance to showcase their coding and programming capabilities and stretch their skill sets for the good of their community.
In 2020, however, given the uncertainty around school scheduling and in order to observe social-distancing and other CDC guidelines, codeLinc will transition to an 2 month virtual competition. The intent is to retain the core promise of codeLinc: Lincoln technologists working closely with students to leverage technology and solve challenges encountered by a charitable organization.
- The event will be held from August 17, 2020-October 17, 2020.
- Opening Ceremony and Kick-off will be held at: August 17, 2020 12:00 p.m. EST. These remarks will be recorded live and available for the duration of the event on the codeLinc YouTube channel.
- All entries must be submitted no later than 11:30 p.m. on October 17, 2020.
- Judging of the entries is expected to last 4 weeks.
- Winners will be announced no later than November 17, 2020.
The prize money will be awarded to the winning Registrant(s) via check within two to four weeks of the close of the event. The prize will be divided equally among the team members, with each team member receiving a check for their portion of the prize money.
The technical innovation prize will be awarded to the Registrant that submits the most creative technically sound and creative solution. This award can be in addition to or exclusive of the 1st, 2nd and 3rd prizes. Detailed scoring criteria are available in the rules.
After reviewing the event rules, please register here
$15,000 in prizes
1st Place Entry
$8,000 (team prize)
2nd Place Entry
$4,000 (team prize)
3rd Place Entry
$2,000 (team prize)
Technical Innovation Award-Sponsored by MindTree
$1,000 (team prize) The technical innovation prize will be awarded to the Registrant that submits the most creative technically sound and creative solution. This award can be in addition to or exclusive of the 1st, 2nd and 3rd prizes.
Submitting to this hackathon could earn you:
You are eligible to enter if you meet the following requirements at the time of entry:
- You are at least 16 years of age;
- You are actively enrolled as a student at an accredited educational institution that grants high school or college/university (or equivalent) degrees
- If you are considered a minor in your place of residence, then you must have your parent’s or legal guardian’s permission prior to submitting an entry into this Contest
- You are not a current employee, intern, agent or otherwise affiliated with Lincoln National Corporation or any of its subsidiaries;
- You are not involved in the any part of the administration of this Challenge; and
- You are not an immediate family member of (parent, sibling, spouse or child) of household member of a person who is: (i) an employee, intern, agent or otherwise affiliated with Lincoln National Corporation or any of its subsidiaries, or (ii) involved in the any part of the administration of this Challenge.
If a Participant is an employee of a corporation, government or an academic institution, it is his or her sole responsibility to review, understand and abide by his or her employer’s policies regarding eligibility to participate in the Challenge. If a Participant is found to be in violation of his or her employer’s policies, then he or she will be disqualified from participating in the Challenge and being awarded or retaining any prize. We disclaim any and all liability or responsibility for disputes arising between and employee and his or her school, government or employer related to the Challenge.
Although Participants do not need to enter as part of a team, all teams will include 3-8 people. Additionally, Participants can only be a member of one team.
After reviewing the event rules, please register for the event
WHAT AND HOW DO I SUBMIT?
By 11:30 p.m. EDT October 17, 2020, Registrants must submit a project packet including the mobile application, a link to the working source code, the application login credential, a written description and a brief demonstration (the “Entry”).
Each Team may submit only one Entry.
Before initiating the submission process, Registrants are required to register and/or create a profile on Devpost.com and to agree to the terms and conditions of the site. Upon completion of the registration process, Registrants will be able to submit their Entries.
WHAT IS REQUIRED OF THE PROJECT?
Each Entry shall consist of a mobile development project as outlined in the Project Templates provided. It is permissible to use open-source development tools. The application should not contain any third- party proprietary code and it is Registrant's responsibility to ensure that the submission does not infringe or violate any third-party rights or laws. Additional development resources will be made available to Registrants throughout the competition. If the solution employs components or plugins incurring future licensing costs, these must be prominently documented.
The application each Registrant submits must:
- be an application or other programming project in alignment with the project templates provided;
- have been developed solely as part of this Challenge;
- be the sole work of the Registrant;
- be submitted in English;
- be a completed solution or working application at time of submission; and comply with these Official Rules.
- A full project submission should require all of the following:
- A 3-5 minute video including demonstration of the application, the process that the group used to create the application and any APIs or other integration point
- All source code via a link to GitHub or another repository. Your code repository can be public or private. If your repository is private, access must be given to codeLinc@lfg.com and indicated in the documentation.
- Any needed technical documentation including links to a description of 3rd-party frameworks employed
- Any presentation file(s) used during the video
- Photos of all team members, either individually or together
HOW WILL ENTRIES BE JUDGED?
The team’s full submission packet must be submitted and posted to the codeLinc devpost site no later than 11:30pm EDT on October 17, 2020. Scoring criteria are visible under the rules tab or on Dropbox.
The winning Entries will be announced on November 17, 2020.
Scott Roth (The Big Guy)
SVP, Lincoln IT Enterprise Solutions
VP, Application Development Manager
VP, Lincoln IT HR
VP, IT Ops Technology Management
Big Brothers Big Sisters
1. User Interface & Intuitiveness
Does the solution incorporate a cohesive, logical user interface or experience? Would it be easy for the target user to navigate and/or administer?
2. Functional Requirements & Impact
Does it functionally address some or all of the challenge presented? Does it solve a real problem?
3. Solution Design & Innovation
Does the solution presented employ an innovative or creative approach?
4. Demonstration and Presentation
Is the presentation delivered clearly, effectively, and positively? Does the demo / screenshots clearly depict and demonstrate the functionality developed?
5. Does it Work?
Does all or part of the application work? Would the organization use it? Note - significantly more weight is placed on the core functionality than on supporting / tangental items such as login/registration/password reset etc
6. Technology Platform(s) Employed
Does the application employ novel technology platforms / libraries / open-source / apis?
7. Security Accomodations
There is no need to or much value in developing a login / password authentication capabilities from scratch. However, please describe how your application accommodates user security, either via publicly-available security mechanisms or other means
8. Technical Creativity
Does the application presented incorporate a novel approach or innovative solution to the challenge presented?
9. Architecture & Methodology
Does the presentation touch upon the application architecture? Did the team employ storyboarding or other roadmapping?
The application should not be more complex than necessary to deliver the solution. However, it should not be overly-simplistic and "gloss over" or omit accommodations for the functionality presented