Running a program on algorithms.live

    A guide for schools, universities, and government partners: what the Programs feature does end-to-end, who does what, and exactly which emails go out and when.

    How it works

    1. Step 1

      We set up your program

      Our team creates the program with your organization's name, tracks, timeline, prizes, eligibility rules, and assessment challenges, then adds your staff as Admins or Judges.

    2. Step 2

      Applicants apply

      Anyone with an algorithms.live account can apply from your program's public page. Each application is confirmed by email immediately.

    3. Step 3

      Applicants learn and get assessed

      Applicants work through the assigned curriculum track, then take a timed DSA assessment. Passing or failing both trigger an email with the result.

    4. Step 4

      Admins form teams

      Your admins review applicants who passed the assessment and assign them into teams, each with a problem statement. Every team member is emailed when they're assigned.

    5. Step 5

      Teams build and submit

      Teams build their project and submit it from their dashboard. Every team member gets a confirmation email the moment a submission is saved.

    6. Step 6

      Judges score

      Your judges score each team's submission from the Judging tab. Scores are private to judges and admins until results are published.

    7. Step 7

      Admins publish results

      Admins review the assisted ranking (teams sorted by average judge score) and publish each team's final rank. Publishing a team's rank emails that team immediately, and the program's public Results page updates.

    Admin

    Reviews applicants, forms teams, defines problem statements, manages the Roster (adding more admins/judges by email), and publishes final results.

    Judge

    Scores team submissions from the Judging tab. Judges don't manage applicants, teams, or publish results — that stays with Admins.

    Transactional emails

    Every email below is sent automatically by the platform at the moment its trigger happens, except results — those go out only when an admin deliberately publishes them.

    TriggerRecipientsSubject
    Application submittedThe applicantApplication received — {program}
    Assessment completedThe applicantYou passed / Assessment result — {program}
    Admin assigns a teamEvery team memberYou've been assigned to a team — {program}
    Team submits a projectEvery team memberSubmission received — {program}
    Admin publishes a team's rankEvery team memberResults are in — {program}

    FAQ

    Getting started

    Programs are currently set up by our team for each partner organization, so tracks, timelines, and assessments are configured correctly from day one.