›_ inctrl
Live technical interviews

Interview engineers in real environments, not on whiteboards.

Candidate and interviewer share one live terminal into a real, broken system you set up yourself — Kubernetes today, with Linux, networks and cloud accounts next. Every session records into a replay your hiring committee can actually watch.

A real environment

An actual running system in a microVM, pre-broken — not a quiz or a mock.

Committee-grade replay

The session plays back with a command timeline — share the signal, not your notes.

Private to your team

You record your own scenarios. There's no public bank for candidates to memorize.

Built for DevOps, SRE, platform & infrastructure hiring.

Sign in

inctrl is invite-only while in early access.

By continuing you agree that interview recordings are evaluation data handled under our retention policy.

›_ inctrl
Welcome

What's your name?

This is how you'll appear to candidates when you join an interview. You can change it later in Settings.

›_ inctrl
Interviews
Scenarios
Candidates
Replays
Roles soon
Team
·
Interviews

Run a candidate, live

Start an interview on one of your scenarios — the environment is live in about 30 seconds.

Live now
No interviews running.
Hit New interview to start one — live in about 30 seconds.
Scenarios

Your scenarios

Broken environments you interview candidates on. Write the break as code, or build it live in a playground.

Candidates

Candidate pipeline

Everyone your team has interviewed. Each person's interviews, scenarios, and replays in one place.

No candidates yet.
Start an interview and name the candidate — they show up here.

Candidate

Replays

Interview replays

Rewatch a finished interview exactly as the candidate saw it — terminal, browser, everything.

No replays yet.
Click Record during an interview — it shows up here once the interview ends.
Roles

Interview processes

Coming soon

Run more than one hiring process. A role bundles which scenarios to use, the rubric, and the stages — so "Senior SRE" and "New-grad" loops each get their own setup.

Team

Your organization

Pending invites

Your organization is invite-only — people join only when you invite them, with the role you choose. Owners manage the team; managers record scenarios and run interviews; interviewers can only run interviews.

Settings

Your profile

This is the name shown to candidates when you join an interview.

Interviews

Preparing interview…

provisioning…

Spinning up a live environment for this interview — the join link appears the moment it's ready (usually ~30 seconds). You can leave this page open.
1
Send the candidate this link — it's the only one to share
2
Join as the interviewer when they're ready
The candidate lands in a waiting room — they can't see or touch the terminal until you admit them. Everything they type is recorded for the committee replay.

Save as a scenario

Saves the code in /scenario/. It'll appear in your library to interview on.

Start an interview

Name the candidate, choose a scenario and a length. Two join links are minted the moment it's live.

Delete scenario?

This removes it from your library and storage. It can't be undone. Any interview already running on it keeps going.

Edit scenario

Update the name, brief, answer key, the base it runs on, or the code that builds the break.

Scenario code

Written to /scenario/ in the guest before the candidate joins. setup.sh is the one that runs.

Build a scenario live

Spin up a clean environment and write the break in /scenario/, applying it until it fails the way your real incidents do. Save stores that code as the scenario.

Invite to your organization

They’ll get a link to join with the role you choose.

Send this to . It expires in 14 days.