Interview · Role-specific
Covers planning and dependencies, technical judgement, risk, launches, communication with leaders and getting ownership settled. Suits mid-level and senior technical program managers. Follow-ups push for specific mechanisms, dates and what went wrong.
Suits: Technical program manager, Engineering program manager, Technical project manager, Delivery manager
Interviewer: Tell me about a time you changed someone's mind at work. How did you go about it?
Candidate: Our team wanted to rebuild the billing page from scratch, and I thought it was the wrong call, so we put together a plan to…
Interviewer: You said "we". What did you say yourself, and what finally changed their mind?
Scored on
Score, reasons and recording. Your team decides.
An example exchange. This interview's own questions open when you use it.
Every answer is scored against this guide, with the reasoning written beside the score. You get the recording or the written answers too, and your team makes the call.
Engineering · Technical
Four classic problems, solved in words, that show how a candidate reasons about correctness and cost.
Listens for
4 of 18 questions · 35 min · All levels
Engineering · System design
One notification service at burst scale, designed stage by stage to test estimates, scaling and failure.
Listens for
7 stages · 50 min · Senior to Staff
Engineering · Technical
Tests real frontend judgement: performance on weak devices, state, accessibility, rendering and debugging.
Listens for
5 of 16 questions · 25 min · Mid to Staff
