A full technical interview, run at 2am if that suits them.
Competency questions, a live coding challenge that genuinely runs, and a system-design round. What comes back is a scorecard that quotes the candidate, not a bare number.
- 30/45/60
- minutes, your choice
- One sitting
- coding, design and competencies
- 24/7
- whenever suits them
Inside the hour
Enough time on each part that none of it feels rushed.
The time gets shared out sensibly
The warm-up doesn't eat the session. Each part gets its own stretch, and as the end approaches the candidate gets a nudge rather than being cut off mid-answer.
The code actually runs
They write it, it runs, and they see what happens. Much like a live pairing round, except nobody on your team has to sit in.
System design is about the thinking
The drawing and the conversation count together. A tidy diagram with no thinking behind it doesn't get very far.
The scorecard shows its working
Every point comes back with what the candidate actually said behind it, so you can read the reasoning instead of taking the number on trust.
Where we hold back, and why that is deliberate
It reports. It doesn't decide.
Strong hire, hire and no hire are recommendations with evidence attached, not verdicts.
A quiet candidate isn't a low-scoring one by default.
Where the evidence is thin, the confidence drops. We don't invent a score to fill the gap.
It's one hour, not the whole picture.
A single session shows you how someone works through a problem. It can't tell you what they'll be like to work alongside for a year.
See it run on one of your own roles.
Free to try. No credit card, and no credit spent until you ask for work.