Run a real technical round without a technical team.

You do not have an interview loop or a bar to hold candidates to yet. Give each one the same real task in an isolated cloud environment, and read a scored result instead of trusting a gut feeling on your fifth hire.

Mission

3h limit

Ship it behind a load balancer

  • DoneSet up the web server
  • DoneDeploy the API service
  • Route traffic through the load balancer
  • Prove the health checks pass

2 of 4 complete

Live environment

Running
  • vmlab-vm-01Ready
  • svcapi-serverReady
  • lbgatewayProvisioning

2h 12m left of the 3h limit

Your first hires set the bar every later one is measured against

Without Scalyz

You interview on instinct, because there is no one in-house to check the work.
One wrong hire is a fifth of the company and months you do not have.
You are hiring people more senior than you and cannot tell who is bluffing.

With Scalyz

Every candidate does a real task, and you read what they actually built.
You see the work before the offer, not in the first sprint after it.
The task does the checking a senior engineer would, before you are in the room.

What is at stake

At five people, one wrong hire is the whole quarter

You do not have the slack a big team has. The first engineers set the standard, or the lack of one, for everyone who comes after.

What is at stake

A fifth of the team

A hire that does not work out is not a rounding error at your size. It is a real fraction of the company and a quarter you cannot rerun.

What you lack

An in-house bar

There is no senior on staff to sit the interview and tell you what good looks like. The task has to carry that.

What sets the tone

The first few

The people you hire first decide the standard the next ten are measured against, for better or worse.

Live in an afternoon

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

Invite the whole list at once

You pick the test and the deadline, then send your whole applicant list at once, by email, CSV, or a shareable link.

Live environment

Running
  • vmlab-vm-01Ready
  • svcapi-serverReady
  • lbgatewayProvisioning

2h 12m left of the 3h limit

Candidates work when it suits them

Each candidate gets their own machine, a real one, with a real task already loaded.

Camille Durand

DevOps assessment

84
Infrastructure as code86
Networking78
Incident recovery91

No integrity flags

The shortlist ranks itself

Scoring runs automatically against the task you set, so the ranking builds as candidates finish.

Mission

3h limit

Ship it behind a load balancer

  • DoneSet up the web server
  • DoneDeploy the API service
  • Route traffic through the load balancer
  • Prove the health checks pass

2 of 4 complete

Camille Durand completed the lab2m
Report ready for reviewjust now
Hugo accepted your invitation1h

Start from a real task, or bring your own

You can send candidates a published task built around real systems, or import your own files as a .zip so the test is the work your company actually does. Either way you run it yourself first, as a candidate, before anyone else sees it.

  • Scored automatically on the end state of a real system, not on an answer
  • Import your own scenario as a .zip, rename it, and run it yourself as a candidate first
  • One credit per candidate, reserved on send, released on expiry, no seats

The questions we get

Straight answers on how the tests, the scoring and the credits actually work.

What is a Scalyz lab, exactly?

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.

Who scores it?

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.

Can they cheat with AI?

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.

What do I pay?

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.

Can I bring my own exercise?

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.

What is it like for candidates?

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.

Hire your first engineers on the work

Book a demo and we will run it on a role you are hiring for now.

One credit per candidate, reserved on send, released on expiry, no seats