Appearance

What candidates do in a Vibe coding round ​

Available onProEnterpriseand the Pro trial

This page walks through the round from the candidate's side, so you know what they see and how the deadline works. For the candidate's own guide, see Coding rounds.

Before the round starts ​

  1. Notice. The candidate reads what is recorded and how their work is evaluated, and agrees. Nothing is recorded and the time doesn't start until they continue. From here they can also ask for an accommodation.
  2. Intro. The candidate sees the task name, the time limit ("45 minutes once you press Start"), the language, with the standard library only, the assistant level and how many hidden checks run on their final code after they submit. The intro explains how it works and how they are evaluated: whether the final code passes the hidden checks, the quality of the code, how they solved the problem and, when there is an assistant, how they worked with it.
  3. The candidate clicks Start the round, or I can't do it now to ask for a different time. You see asked for a new time on the round.

Small screens ​

The round has a code editor, a test runner and an assistant side by side, so it needs a laptop or desktop. On a phone, a tablet or a window narrower than 900 pixels, the candidate sees Please use a laptop or desktop, with buttons to copy the link or email it to themselves. They can still click Continue on this device anyway.

During the round ​

  • The candidate reads the Brief, opens files and edits code in the editor.
  • They click Run tests (or Ctrl or Cmd + Enter) as often as they like.
  • With Full help, they ask the assistant and accept or reject each change it suggests as a diff. With Hints only, it explains errors and gives hints but doesn't write code. With Off, there is no assistant.
  • They click Submit when they are done.

How work saves ​

Each file saves 900 milliseconds after the last edit. Until the server confirms a save, the edit is also kept in the browser. If a save fails, the page keeps retrying: after 8 seconds at first, then less often, up to once a minute.

If the test runner can't start on Infyva's side, visible tests run in the candidate's browser instead. Hidden checks only ever run on Infyva's servers, later if needed.

The deadline ​

The timer counts down from the moment the candidate clicks Start the round.

  • Warnings show at 10, 5 and 1 minutes left: "Your work is submitted automatically when time runs out."
  • In the last 3 seconds, any edits not yet saved are sent.
  • At 0:00 the editor locks and the round is submitted automatically.
  • There is no grace period. Infyva takes no save or test run after the deadline. A save that arrives late is refused and never graded.
  • If edits didn't reach Infyva in time, the done screen names the files, says the hiring team sees the version Infyva has, and offers Download these edits so the candidate can send them to you.
  • If the page is closed, Infyva submits the round itself 3 minutes after the deadline.

The report marks a round that ended this way with time ran out.

What is monitored ​

Leaving the tab and pasting large blocks of code (400 characters or more) are noted for you. The camera and microphone are not used. These are signals to ask about, not proof of anything.

Limits ​

  • Up to 60 files, 100,000 characters per file and 600,000 characters in total.
  • A visible test run stops after 30 seconds. The final run stops after 60 seconds.

After submitting ​

The candidate sees Your Vibe coding round is submitted and gets a confirmation email. To ask for a person to look at the result again, they reply to that email.

Next steps ​