Skip to content

From a CV line to a result anyone can check

CodeXams links each skill a candidate claims to a timed coding exam, a decision by a person at the hiring organisation, and a signed result.

Every step says who or what produced it:

Checked by codeProposed by a modelDecided by a person

How it works

Five steps on one thread. The candidate supplies the claims; the organisation tests and decides; the signature lets anyone check the outcome later.

  1. A CV line becomes a skill

    The candidate uploads a CV. A model proposes skills, each quoting the line it came from; code checks the quote is really there. The candidate keeps or removes each one.

    Proposed by a modelthen checked by code

  2. The team sets the exam

    An owner publishes the assessment: the coding task, the skills it tests, the AI help allowed and what is recorded. Candidates read it all first.

    Decided by a personthe hiring team

  3. The candidate codes

    A timed exam in the browser, then short questions about their own code. Hidden tests run the code; runs and pastes are recorded, the screen only where the policy says so.

    Checked by codehidden tests, by tier

  4. A person decides

    Reviewers start from the model's proposed rubric scores, keep or change each one, and record a decision with their reasons. A model never rejects anyone.

    Decided by a personwith written reasons

  5. The result is signed

    A validated decision can be issued as a signed result. Anyone with the link can check it was not changed and has not been revoked.

    Checked by codethe signature

How evaluation works, and why there is no total score

For hiring teams

  • See the code as it was written, every run and paste, and the hidden tests by tier, side by side.
  • Score against the same rubric, starting from a labelled model proposal that cites its evidence; keep or change each score.
  • Record decisions that cannot be edited later, only added to, with every view of a candidate's work in your audit log.
  • Issue a signed result the candidate can share, and revoke it if you must.

For candidates

  • Each skill shows the line of your CV it came from. Remove anything that is not yours.
  • Read the AI policy and what is recorded before the clock starts.
  • Follow your exam from submitted to reviewed, and ask for a person to review an automated decision.
  • Share your result as a link anyone can check, without an account and without sending your exam.

What candidates can rely on

These hold for every organisation that uses CodeXams, and no organisation can switch them off.

  • No model decides your outcome.

    Models propose skills, questions and a suggested band. A reviewer at the organisation decides; where its own rules decide a routine case automatically, you can ask for a person to review it.

  • There is no single score.

    Hidden tests are reported by tier and questions about the code by type, next to each other. Nothing adds them up or ranks candidates.

  • You see the rules before you start.

    The AI policy and what is recorded are on the screen before the exam begins, and recording starts only after you consent.

  • Only the organisation that invited you sees your exam.

    The exam service never learns your name or email. Each view of your work by the organisation is logged.

  • You can leave.

    Withdraw before a decision and your exam data is deleted; after one, you can ask the organisation to delete it.

Questions

Run your next technical assessment on CodeXams

Set up your organisation and publish a first assessment. Invited as a candidate? The link in your invitation email takes you to it.