For hiring teams

Run hiring challenges that show how developers work.

Give candidates realistic software work, review candidate-attributable evidence from the process, and inspect Technical Evaluations before your team decides.

Technical Evaluation for Alex Morgan showing a 3.60 out of 4 score and evidence coverage

Define the work

Set the evaluation contract before the run begins.

Define realistic technical work, expected deliverables, review criteria, and repository expectations before candidates begin.

  1. 01
    Technical requirement

    Anchor the challenge in a concrete software problem.

  2. 02
    Candidate plan

    Make the expected work and deliverables explicit.

  3. 03
    Review criteria

    Review exactly what the evaluation will consider.

Challenge setup showing the technical task contract, candidate plan, review criteria, and approval state
Alex Morgan activity timeline showing recorded development progression

Review the trail

See the work behind the submission.

Recorded development activity gives reviewers context beyond the final result. It shows progression through the run without turning activity into a proxy for productivity, personality, or seniority.

Review contextProgression, milestones, and recorded run events.

Inspect the evaluation

A technical evaluation should show its basis.

Inspect criterion judgments, confidence, evidence sufficiency, and source references before your team reaches a decision.

Technical Evaluation criterion showing judgment, confidence, evidence sufficiency, and source references

Technical decision support stays inspectable. Your reviewers retain authority.

Evidence first

Insufficient evidence is a valid outcome.

When candidate-attributable evidence is insufficient, DevMarathon can return no overall score instead of inventing certainty.

Jamie Chen Technical Evaluation showing insufficient evidence for an overall score

AI supports the review. Your team makes the decision.

Human review remains final.

Operate the loop

Move from candidate runs to reviewer action.

Review run status, open the development trail, and inspect the Technical Evaluation in one connected hiring workflow.

  1. 01Candidate runs
  2. 02Development evidence
  3. 03Technical Evaluation
  4. 04Reviewer action
Organizer workflow moving from candidate runs to activity evidence and Technical Evaluation

AI evaluation pricing

Run hiring free. Pay only for AI evaluation.

Every organization includes three AI Technical Evaluations. Additional evaluations are $15 each, purchased one at a time with no subscription.

  1. Hiring workflow
    $0no subscription
    Challenges and candidate participation are free3 AI Technical Evaluations included
  2. AI Technical Evaluation
    $15one-time
    1 AI Technical EvaluationOne-time purchase. No subscription

Questions

Before your first challenge.

Does AI make the hiring decision?

No. Technical Evaluation supports the review; your team makes the final decision.

What happens when there is insufficient evidence?

DevMarathon can return insufficient evidence instead of producing an unsupported overall score.

Does Technical Evaluation review the entire repository?

Technical Evaluation uses controlled evidence selected from the submitted work. It does not independently browse the candidate's repository.

Is the hiring workflow a subscription?

No. The hiring workflow is free. Additional AI Technical Evaluations are one-time purchases.

Do organizers need GitHub?

No. Organizers can create a challenge without connecting GitHub.

Can teams start free?

Yes. Challenges, candidate participation, evidence, and manual review are free. Each organization also includes three AI Technical Evaluations.

Start with real work

Review the work behind the submission.