What 50+ QA Automation Interviews Taught Me About Flaky Tests

Last month I asked a senior candidate the same question I ask everyone. "Tell me about a flaky test you fixed and how you fixed it." She paused and said, "I just added a retry." The interview was essentially over after that. Not because retries are wrong. Because she had no curiosity about why the test was flaky in the first place. I have conducted 50+ automation engineer interviews over the past two years, and flaky tests are the single topic where I can predict pass or fail within 90 seconds. Here is what separates the candidates who get offers from the ones who do not. Great candidates reject the "flaky equals unlucky" mental model Most candidates treat flakiness like weather. Sometimes it rains. Sometimes the test passes. Move on. The best candidates I interview treat every flaky test like a bug with a specific root cause. They talk about races, missing waits, shared state across tests, timezone bugs, animation frames, stale locators, hydration timing, and network jitter. When I he