Every candidate gets an isolated cloud environment with a real system in it: a service that will not start, a cluster that is wide open, a deployment that was never written. What comes back is what they actually did.
$ docker compose up -d
3 services started
$ systemctl status api
active (running)
$ curl -s localhost:8080/health
{"status":"ok"}
Live environment
Running2h 12m left of the 3h limit
Without Scalyz
With Scalyz
What is at stake
Nobody finds out a DevOps hire was wrong in a code review. They find out during an incident.
Where it shows
The first incident
The gap between describing a rollback and performing one is invisible in an interview and obvious at 3am.
Who pays for it
The on-call rota
A hire who cannot hold the pager makes the rota worse for everyone who can.
What an interview cannot ask
Show me
Access to a real system is the one thing an interview cannot give a candidate. It is the only thing this replaces.
Three steps from the job post to a shortlist you can defend, with no screening calls.
Backend hiring, July
Open
6 invited · 4 completed
Closes Friday, 18:00
You pick the test and the deadline, then send your whole applicant list at once, by email, CSV, or a shareable link.
Live environment
Running2h 12m left of the 3h limit
Each candidate gets their own machine, a real one, with a real task already loaded.
Camille Durand
DevOps assessment
No integrity flags
Scoring runs automatically against the task you set, so the ranking builds as candidates finish.
$ docker compose up -d
3 services started
$ systemctl status api
active (running)
$ curl -s localhost:8080/health
{"status":"ok"}
Mission
3h limitShip it behind a load balancer
Set up the web serverDeploy the API service2 of 4 complete
These are real systems rather than exercises: a Go service that has to come back up on its own under systemd, a Node and Postgres stack that will not talk to itself, a Kubernetes deployment that has to be hardened, a web server that has to be built with Ansible.
The published missions for this role
Straight answers on how the tests, the scoring and the credits actually work.
A real virtual machine with a real mission, not a quiz. The candidate works with the same tools they'd use on the job, and the session is recorded so you can review the evidence later.
Automatically. The checks run against what the candidate delivered, and you get a report broken down skill by skill, so no one on your team grades a thing by hand.
A chatbot can suggest commands, but it can't run a live system for the candidate. The mission has to be done on the machine itself, and any cheating signals come with context, so you can judge them yourself.
In credits: one per candidate. A credit is reserved when you send an invitation and released if it expires unused. You pay per candidate tested, never per user.
Yes. Upload your files as a .zip, rename the mission to match your role, and run it yourself for one credit first. What you tested is exactly what candidates get.
On their own time. They start when it suits them, work with real tools on a real machine, and finish in one sitting. It runs in English and French.
Book a demo and we will run one of these missions on your own open role.
One credit per candidate, reserved on send, released on expiry
