Real cluster. Real fault. Real engineer. Find out.
The mechanics in detail: how the environments are built, what the evaluator watches, how an interview is graded, and what we deliberately refuse to build.
- 50+
- Kubernetes labs
- <1 min
- Environment boot
- 5
- Scored criteria
- 0
- Cameras, ever
01
A real cluster, not a simulation
- Firmware will not start after a config changeIntermediate· 25 min
- Auth is down and the on-call runbook did not helpIntermediate· 25 min
- The rollout stopped at 2 of 5 and the deadline has passedAdvanced· 35 min
- Five services are down and only one of them is brokenAdvanced· 45 min
- Restore the service and leave it costing 30% lessAdvanced· 45 min
02
Grader scripts decide. The model explains.
- 4 / 4Fix correctnessgrader scripts
- 3 / 4DiagnosisAI, capped by reads
- 2 / 4Blast radiuscode sets the ceiling
- 3 / 4VerificationAI, capped by reads
- 3 / 4Root-cause explanationAI vs the answer key
03
What the report tells you
- Commands in the right direction71%
- Hypotheses tried first2
- Dead ends in / out1 / 1
- Commands that changed state6
04
Blast-radius score
05
AI-allowed by design
- AI toolsallowed, any model, no disclosure needed
- Detectionnone, we do not run any
- Proctoringnone: no camera, no mic, no screen
- Tab switchingnot watched, not scored
- What is gradedthe cluster, and the commands that got there
06
The full command log, not screen video
Roadmap
What’s next
Not shipped yet, listed anyway, customer feedback decides the order. What is deliberately not here: screen recording, webcams, or proctoring of any kind. The command log is the terminal, full stop.
In-session AI (opt-in, candidate told up front)
An AI assistant inside the lab terminal. The full prompt trail is graded alongside the commands: what context they gave it, which suggestions they caught as wrong, whether they verified before applying. Bring-your-own-AI stays allowed either way.
Randomized fault variants
One lab compiled into many concrete faults, with the invite picking one. Today each lab injects a fixed fault, so a leaked walkthrough is blunted by the grader rather than by the fault itself. Variants are the structural fix and they are being built.
Lab suggestions from a job description
Upload the JD, get a shortlist of labs that test what it actually asks for, with your own constraints (how many labs, how long each) respected. Today you filter the library yourself, and every lab says in plain English what it puts under pressure, so it is a two-minute job rather than an impossible one.
Live shadow mode (opt-in, candidate told up front)
Watch the interview in real time, read-only. For panel interviews that want to talk through the incident afterward, not surveillance.
Team incident drills
Same format, aimed at the team you already have: scheduled game days, blast-radius scores per engineer, and a report you can bring to the postmortem. Practice the 3 AM page at 3 PM.
More stacks
Every lab today is Kubernetes, and the platform can only boot Kubernetes sandboxes. We would rather say that than imply a breadth we do not have. Linux, Docker, Terraform, and CI/CD come next, then databases and cloud-provider labs: Postgres on fire, a pipeline that ships the wrong artifact, a cloud bill exploding.
Candidate skill profile
A verified record of solved labs: what was broken, what they fixed, and what the fix cost. Signal that travels with the engineer, not the employer.
Environments, data, and what we refuse
The questions your security reviewer will ask, answered before they ask them.
Disposable every time
Every interview and practice run gets its own environment, built for that attempt and destroyed when it ends. Candidates are expected to break things, so nothing they touch is shared with anyone else.
Nothing to install
The candidate needs a desktop browser. No VPN, no cloud account, no agent on their machine, no admin rights. Nothing from their laptop is touched.
What is recorded
Terminal commands, their exit codes, and diffs of files changed inside the environment. That is the complete list, and it is what the command log is made of.
What is never recorded
No camera, no microphone, no screen capture, no biometrics, no keystroke dynamics. None of it exists in the product, and adding any would mean changing the privacy policy first.
Retention and deletion
Interview reports are kept 12 months. Practice reports stay until you delete them.
Your code stays yours
Labs run on our own environments, not your repositories. A custom lab is built to resemble your stack, not to contain it, so nothing proprietary leaves your side.
Full detail in the privacy policy →
How Faultybox compares
Categories, not names. You know who they are.
| Faultybox | Code-sandbox platforms | Quiz platforms | |
|---|---|---|---|
| Real infrastructure | live Kubernetes cluster, cluster-admin | sandboxed snippets | multiple choice |
| Solved or not decided by | grader scripts against the live cluster | test cases on output | an answer key |
| Durability checked | the fix must hold | ||
| Blast radius | scored | ||
| AI policy | allowed, no detection, no proctoring | detection arms race | banned / proctored |
| Command log | every interview | sometimes |
Check the fit before you start: who this is for →
The box is faulty. Want in?
Free to start, no card. Hiring teams get 3 interviews and 3 trial runs on every interview lab. Engineers get 3 free practice runs on the free labs.