A coding task, then the why
Tracy can introduce a coding task and probe the trade-offs behind the answer.
The first round is where the time goes.
- A passing test case says nothing about how the code holds up at scale.
- Take-home tests are easy to outsource.
- Senior engineers lose afternoons to first-round screens.
Three steps. No calendar.
Pick the skills
Choose skills as tags and set the style from behavioural to technical.
Tracy runs the task and the questions
She asks about the code that was written, not a generic follow-up.
Review with the signals
Tab changes, an external screen and long pauses are marked on the recording.
Evidence behind every result.
Probing on trade-offsMemory, failure modes, what breaks at ten times the load.
Questions from the CV“Your CV mentions Kafka. What did you change in the consumer?”
Integrity signalsEvidence for a reviewer, with timestamps.
Engineer hours savedYour team joins at the round where it matters.
Index for the ledger table
Chose the index from measured read latency, and named the write cost without being asked.
A migration that went wrong
Owned the rollback. Gave the order of steps and what she changed in the runbook after.
Retries from a payment provider
Idempotency keys on write. Did not cover what happens when the key store is down.
Let Tracy take the next interview.
Run your first 3 interviews free, or book a demo and watch Tracy work through your own questions.
Your first 3 results are free. No card needed.