Code RoomSupport queue breach predictor
MediumPrep Room Coding #32

Support queue breach predictor

Vibe & agenticAI agents & automationReliability & on-callMid–Senior~14 min

Your support queue occasionally blows through its service-level targets before anyone notices, and the first you hear of it is an angry escalation. Design an agent that watches the queue and predicts breaches early enough to matter. What can it do on its own — reprioritize, reassign, page someone — and what must it never do? Describe the rollout that earns the team's trust step by step, and the evidence you'd show your VP that it's working.

Implement
decide_queue_action(phase: str, minutes_to_breach: int, minutes_since_alert: int, human_acked: bool) → str
Examples
in["shadow",10,30,false]out"log"
in["assist",40,5,false]out"reprioritize"
in["autonomous",10,30,false]out"page"
What a strong answer looks like

Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).

0:00 of about 14 min

Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.