Marcus Johnson
Technical user
Resolve the technical issue without losing trust
- Context
- Support escalation
- Tone
- Methodical, low patience for fluff
- Difficulty
- 3 / 5
Senior engineer. He's already tried the basics and wants real answers.
What a strong answer includes
- 01Match his technical register
- 02Reproduce the issue verbally
- 03Commit to a real timeline
- 04Confirm the next checkpoint
How this scenario works
- 1
Hit the mic. The persona speaks first — just like real life.
- 2
Answer live. The objectives above light up as you check them off.
- 3
End the session when ready. You get a score and three concrete fixes.
“I've already tried the obvious things. Let's skip the script — what do your logs show?”
Skip the apology script. Ask one precise diagnostic question.
Example of a good answer
I've already tried the obvious things. Let's skip the script — what do your logs show?
Skipping the script. I see 503s from your workspace between 14:02 and 14:07 UTC — that matches the deploy we rolled back. Can you confirm the trace ID on your end? I'll have a fix validated within two hours, and I'll ping you at the 30-minute mark regardless.
Frequently asked questions
Is this scenario based on real situations?▾
Yes. Every scenario is modeled on real conversations people face — interviews, explainers, pitches, difficult discussions.
Do I need to sign up to try it?▾
No. You can run your first round in under a minute, no account required.
Is this voice or text?▾
Both. You can hold to speak, or type. The feedback score works the same way for both.
How long does one round take?▾
Between 1 and 3 minutes per round, plus the score recap.
