Your recruiter runs a real technical screen. Without an engineer.
We generate the questions from your role, in language a non-technical person can read aloud without stumbling. They run the call. We read the transcript back against a level rubric and tell you what the answers actually showed.
Your calendar · your recruiter · 30 to 45 minutes
UPDATE accounts SET balance = balance - 100
WHERE id = 7 AND balance >= 100;Junior: reaches for a transaction and stops there.
Red flag: “the database handles that”.
A recruiter can ask a technical question. They cannot judge the answer.
That is the whole reason engineers get dragged into screening. So we split the job: the human asks and listens, the rubric judges afterwards, from the recording, against the same level profiles our own interviewers use.
Nothing to pronounce
Every question your recruiter reads is prose. No operators, no syntax, no library names they have to guess at. Code appears on the candidate's screen instead.
One opener, then the probes
The session starts with a warm-up that establishes context once, rather than asking “do you use X” before every question. Then the questions that actually separate levels.
The answer key stays internal
Each question carries what junior, mid, senior and a red flag sound like. Your recruiter never sees it during the call, so they cannot leak the shape of a good answer.
Judged on reasoning, not recall
The transcript is read for trade-offs, consequences and failure boundaries. A right answer with no reasoning behind it scores lower than a wrong one that shows the work.
Want to see the shape of the questions first? Browse screening questions by stack →