Deep service chain latency
A user-facing service is slow, and you trace it through service A -> B -> C, where C (deep in the chain) is the actual slow one. How do you handle it now and after?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
0:00 of about 20 min
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.