A candidate told me about the day his manager wanted to push a feature straight to production.
Tight deadline. Skip the review. Skip the tests. Get it live.
He didn’t say no. He came back with a feature flag, a controlled rollout that would let them test with a limited group of users before the full release.
The manager agreed. The feature shipped. No incidents.
I’ve heard a lot of candidates talk about technical debt this week. Most frame it in the abstract. “we should have tested more,” “the team moved too fast,” “we accumulated a lot of shortcuts.”
Very few describe the specific moment they were in the room where the shortcut was being proposed, and what they actually did instead.
That’s a different thing entirely.
The first is pattern recognition. You’ve watched something go wrong and you understand why. The second is judgment under pressure. You’ve seen the shortcut, understood the cost, and found a path that didn’t require your manager to lose face.
The feature flag wasn’t just technically smart. It gave the manager what he actually wanted – the feature live – without the risk he hadn’t fully thought through.
That’s not pushback. That’s engineering.
When have you seen someone reframe a technical disagreement into a shared win — and what made the difference?
Leave a Reply