See how engineers actually work with AI tools
One round of your existing loop, run in a real editor and terminal with an AI tool alongside. You see exactly how the candidate directed it, scored against a shared rubric with the evidence attached.
Interview signal broke when AI became normal
Every stage in a standard loop now measures something other than the job. Candidates know it, and so do your engineers.
Take-homes measure free time
A great submission and a generated one look the same. You end up interviewing the code, not the engineer who sent it.
Whiteboards ban the daily tools
Banning the assistant tests memory, not judgment. The skill you are actually hiring for, directing a model well, never shows up.
Nobody scores the skill that matters
Engineers direct a model every day, then get hired on a loop that never looks at it. RecruIQ drops into your existing pipeline and scores that work.
One round, in place of the take-home
Three steps from setup to a decision you can explain
Create the opening
Pick a task, select the language, add interviewers. Set it up once and reuse it for every role on the team.
Candidate works for real
A real editor and terminal, plus an AI tool with a visible token meter. Keystrokes and prompts are recorded as they work.
Review the report
A rubric-based report: a score on each of the five axes, how the candidate used the AI tool, and the moment in the session behind every score, so you can check the reasoning rather than take it on trust.
Watch the process, not just the diff
Play back the whole session. Every prompt and rewrite is marked on the timeline, so your debrief runs on what actually happened rather than what anyone remembers.
Compare candidates on one rubric
Same task, same five axes, same weights, so two candidates are genuinely comparable. RecruIQ’s model reads the session and scores each axis; the weights are fixed server-side, not chosen by the model, so a composite cannot be talked upwards. Every score carries a link to the moment in the session behind it, and the hiring decision stays yours. RecruIQ never makes one.
An interview engineers do not resent
One scheduled session instead of a weekend of homework. Candidates see the rubric before they start, and work in a normal editor with the AI tool switched on.
Planned integrations On the roadmap
None of these are live yet. They are what we are building next so stage changes, reports and scheduling sync both ways instead of moving by CSV. Tell us which one you need first and it moves up the list.
Two plans, both approved before you start
We approve every workspace by hand while we are in early access. No per-candidate fees, and interviewers and observers are always free.
The questions we get first
Cheating assumes the tool is banned. Here it is part of the task. We record every prompt, and the rubric scores how well the candidate directed, verified and corrected the model. Someone who pastes an answer they cannot explain scores badly on prompt quality and verification behaviour, and because each score links to the transcript, you can see why rather than take the number on faith.
The rubric, the language, the time limit, and who is watching. They pick their own slot within the window you set.
Python, TypeScript and JavaScript today, each with a real toolchain. More are on the way, so tell us which one you need.
Not automatically yet. ATS integration with Greenhouse, Lever, Ashby and Workable is on the roadmap, not shipped. Today you invite candidates by link and share the report by URL. Tell us what you run and it helps us order the work.
You choose per stage: 30, 45, 60 or 90 minutes. A round can have up to eight stages, and each one has its own length.
Yes. Bring your own task, write the rubric, and we version it so results stay comparable across candidates.
Add this round to your loop
Request access and we will set up your first round with you. Or take a 30-minute walkthrough with an engineer first.