Your first interview

  1. Sign in with Google or GitHub and name your company. You are on Free: 3 sessions a month, no card.
  2. Create a session. Start from a template, or pick formats yourself — each becomes a tab. Add a title the candidate may see.
  3. Add the call. Invite in the session takes a Zoom, Meet or Teams link and a time, and gives you an invitation to paste and a calendar file.
  4. Send the candidate’s link. It looks like /s/8f3a-2b19/…; the long part is a key. It works until you end the session.
  5. Open the session yourself from Sessions. Signed in and in the team, you are the interviewer.

The six formats

  • Live coding — a shared editor in 15 languages. JavaScript, TypeScript, Python run in the browser of whoever presses Run, and both sides see the output.
  • Code review — you paste a fragment; the candidate selects lines and comments.
  • Project review — a repository pushed into the session with git, shown as a file tree.
  • System design — an Excalidraw board with a library of services, databases, queues and caches.
  • Manual QA — a test-case table and one bug report, both exportable to Markdown.
  • AI workbench — the candidate works in their own Claude Code; you watch its steps on a timeline.

A session can hold several formats as tabs. Add one mid-interview; the candidate follows the tab you open.

During the interview

  • Notes are yours alone: the server never sends them to the candidate. + Time puts the time in front of a line.
  • The guide — a template’s questions and what a good answer looks like — sits beside your notes. The candidate does not see it.
  • Integrity signals: pastes with their first lines, time away from the tab, large instant edits. The candidate is told before joining. No camera, no screen recording.
  • A dropped line loses nothing: edits wait in the tab and go out when it is back. A reload keeps them too.

After the interview

End session closes it for the candidate at once; their link stops working. You keep the session: edit your notes and Save as PDF — notes, code, comments, the board, test cases and signals, through the browser’s print dialog. Save as template keeps the tabs for the next candidate (Team).

Sessions are deleted 7 days after their last use on Free and 30 on Team. The dashboard shows each date. Save the PDF if you need a record.

What the candidate needs

  • A current Chrome, Edge, Firefox or Safari. No account, no install.
  • Behind a corporate proxy that blocks WebSockets, the session switches to plain HTTP by itself. The status page shows which one a network gets.
  • The join screen tells them what you see. Your company’s hiring privacy notice is yours to give; ours is in the privacy policy.

Pushing a repository

In a Project review session, either side pushes with plain git. The session shows the command with its address; it carries the session’s key, so treat it like the candidate’s link:

git push https://chillcode.net/git/<id>.<key>/repo.git HEAD:main

Push again to update; force pushes work. Clone and fetch are refused. Only the files are kept, not the history.

The AI workbench

The session shows the candidate two things to paste into their Claude Code: hook settings that send its steps to your timeline, and a command that adds two mock MCP servers — a ticket tracker and an error monitor. One ticket carries a planted instruction; you see whether the agent follows it. From the timeline you change the task, drop a server and mark each step. Nothing from their machine runs on ours.

Teams, plans and templates

  • Invite colleagues from Team: a link for one person, valid 7 days. Paste it into Slack; they sign in and join. We send no email.
  • Free: 3 sessions a month, one interviewer. Team: €29 a month or €24 a month yearly — unlimited sessions and interviewers, templates. Owners change the plan under Plan; cancelling is one click.
  • Templates: starter interviews from the library, and your team’s own, saved from any session.

Limits

Code 500 KB, notes 100 KB, a pushed file 200 KB and a repository 6 MB, 5 000 shapes on the board, 200 test cases, a run 10 seconds and 64 000 characters of output.

Support

Email support@chillcode.net — we answer within one working day. Mention the session’s short id (8f3a-2b19), never the whole link. Something down? Check the status page. Security issues go to security@chillcode.net.