Code Room
Vibe codingHardvc-g230
Subject Ai verificationLevel Senior–Staff~20 minCommon in Reliability & on-call interviewsIndustries Software development, Technology

Question

Production alert: p99 latency on your Go search service tripled at 02:14 UTC and error rate is creeping. No human deployed anything overnight, but several AI-agent PRs auto-merged after passing CI. You need to trace the incident to a root-cause change fast. Walk me through how you go from 'latency tripled at 02:14' to the specific AI commit responsible, and how you confirm causation rather than coincidence before you revert.

What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.

Describe your solution

Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.

Run or narrate your approach, then ask the coach.