Skip to main content
The cookbook gives you ready-made setups for common situations. Each recipe shows exactly how to build one Role end to end โ€” what to put in the Role, which Rounds to add, and which Interviewer runs each Round. If the three words still feel new, read How the pieces fit first. The one-liner:
A Role has Rounds; each Round is run by an Interviewer.

โ€‹
How to read a recipe

Every recipe follows the same shape, so once youโ€™ve done one you can do any:
1

Build the Interviewers (once)

These are reusable. Build them once under Interviewers, then reuse them in this recipe and any future Role.
2

Create the Role

Name it after the job, paste the job description, and list the skills.
3

Add the Rounds

Add each Round in order, point it at an Interviewer, and set its pass mark.
4

Add people and go

Add participants (or share the apply link) and schedule. The AI runs the interviews and sends scorecards.
You can do all of this in the dashboard โ€” no code. API snippets are included only for teams automating their pipeline.

โ€‹
Recipes

ServiceNow Engineer

One job, many flavors โ€” ITOM, HRSD, or both โ€” by mixing reusable module Interviewers into the right Rounds.

Backend Engineer

Screen โ†’ System Design โ†’ Coding, with a rising pass bar and human sign-off before the final.

Frontend Engineer

Screen โ†’ UI/JavaScript โ†’ Take-home review, tuned for component and accessibility depth.

Non-technical Roles

Customer Support and Sales โ€” no coding, just a friendly screen and a realistic roleplay.

โ€‹
The pattern behind every recipe

The magic is reusable Interviewers. Build a small library of module experts once: Then each Role just composes the Rounds it needs from that library. Need a variant (ITOM-only vs ITOM + HRSD)? You add or drop a Round โ€” you never rebuild the interviewer brains. Thatโ€™s the whole idea, shown concretely in the ServiceNow recipe.
Last modified on June 30, 2026