Code Room
Vibe codingMediumvc-g600
Subject Ai iterationLevel Mid–Senior~18 minCommon in Algorithms & data structures interviewsIndustries Software development

Question

You asked an agent to fix a flaky integration test. Its first attempt added a `sleep(2)`; you rejected that and asked for a real fix; its second attempt wrapped the assertion in a retry loop, which is the same smell. It's clearly pattern-matching 'flaky test' to 'add waiting.' How do you diagnose why it keeps missing and re-steer it — and at what point do you stop prompting and take over?

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.