The 20 questions they'll actually ask
One hour, twenty questions, five stories. Short answers you can memorise — not a book.
0 of 4 modules done
The five stories
| Story | Answers | |
|---|---|---|
| 1 | The 12-second schedule screen | Q6, Q7, Q8 |
| 2 | The overnight queue backup | Q9, Q12, Q13 |
| 3 | SignalR vs Azure SignalR Service | Q14 |
| 4 | The proposal that was rejected | Q15 |
| 5 | The junior querying in a loop | Q16 |
These are drafts — adapt them to something you actually worked on, because they'll ask for details.
The three rules
| 1 | 90 seconds, then stop. Let them ask the follow-up — that's where you score. |
| 2 | Every story ends with a number. 12 seconds to 1. Six hours stale, no data lost. |
| 3 | Never claim you designed the Call Design platform. You joined it and owned two modules. |
Know your own words
You claim the adherence module. If they ask what it is and you hesitate, that hurts more than not mentioning it. The definition, the diagram and the 20-second answer are at the bottom of Module 01, with the other workforce management terms — conformance, shrinkage, occupancy, AHT, service level.
If you only have 20 minutes
Read the cheat sheet, then say these three out loud until they're smooth:
- Q1 — the 60-second project pitch
- Q6 — the 12-second screen, with its numbers
- Q11 — stabilise → communicate → diagnose → fix → prevent