Assessments on a running system

Assess engineers on a realistic incident, not a quiz.

Send a link. Each candidate gets a running system that is failing under load, a briefing, and a clock that starts when the briefing opens and does not pause. You follow every attempt and read what each candidate did.

How it works

What a candidate goes through

  1. The invitation

    The candidate opens the link you sent, in their browser. There is nothing to install.

  2. Details and rules

    They give the details you asked for and read what is recorded and what is blocked, before anything starts.

  3. Briefing and clock

    The briefing opens and the clock starts. It does not pause.

  4. The running system

    They work on a running system under load: its code, logs, metrics and configuration.

  5. Submit and receipt

    They submit when they are done, or the deadline closes the attempt. Either way they get a receipt.

Set the terms

What you control

  • Incidents and time

    Choose a sequence of Crucible incidents and a duration. Let candidates start freely or within a time window, in the time zone you set.

  • Who can enter

    Only the email addresses you list can register, so a forwarded link lets nobody else in.

  • During the attempt

    Choose whether copy and paste work, whether leaving the window is recorded and warned about, and whether fullscreen is off, requested or required. Turn hints on or off.

  • Details and consent

    Choose the details to collect and the acknowledgements to require. Add your own consent wording.

  • Submitting and results

    Allow one or several submissions, decide whether candidates see a result and whether results are emailed when finalised, and set how long data is kept.

  • Invitation links

    Publish a link per audience. Revoke or regenerate it when you need to.

Follow the work

What you see

  • Attempts by state

    Follow who has registered, who is working, and how each attempt ended.

  • A report for each candidate

    Read the result and the integrity timeline together. The recorded signals are evidence for you to review.

  • A record you can act on

    Reopen or invalidate an attempt, correct a result, export results as CSV, and read the audit log.

Rules in the open

Fair and transparent to the candidate

Candidates read the rules before they register. This example uses the same disclosure text as the candidate flow.

What a candidate reads before the clock startsExample rules
  • The clock starts when you press Go to your attempt.

  • You will be asked to work in fullscreen. You can carry on without it if you prefer.

  • Copying and pasting is disabled.

  • Right-click is disabled.

  • Leaving this page is recorded.

  • You will be warned if you leave this page.

  • This assessment does not use your camera or microphone.

Read the example in full

The clock

  • Setting up counts against your time: you have 60 minutes from that press until you submit, and everything in between is inside them. Reading this page before you press does not use your time.
  • The clock does not pause and does not restart. Reloading the page, opening it in a second tab or retrying does not give you more time — you are shown the same deadline.

What is recorded

  • Leaving this page and coming back to it is recorded, with how long you were away.
  • This page being hidden — a tab switch, a minimised window — and shown again is recorded the same way.
  • Copying and pasting are disabled while you work. Each attempt that is stopped, and any that gets through, is recorded.
  • The right-click menu is turned off while you work.
  • You will be asked to work in fullscreen. You can carry on without it if you prefer.
  • Leaving fullscreen is your choice and the attempt continues. It is recorded as a signal your invigilator can read.
  • The size of this window is recorded when it changes.
  • You will be warned when you leave this page.

How to read these signals

  • These are signals for your invigilator to read, not proof of anything by themselves, and none of them is treated as cheating on its own.
  • A page cannot stop you leaving it, and this one does not try: where you went is never recorded, only that you were away.
  • A browser can be worked around, so this restriction is not tamper-proof. Where this page cannot stop a copy it says so, and records that the copy got through.
  • Fullscreen can be asked for but cannot be enforced: a page cannot force you to stay in it.

Acknowledgements

  • I have read and accept the rules of this assessment.
  • I agree to my details being processed for this assessment.

Set up your first assessment

Choose the incidents, the time and the rules in the console, publish it, and send the link.