Tell me about a time when you pushed back on a decision or request.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you can disagree constructively rather than either staying silent or becoming combative. They want to understand how you evaluate when pushback is warranted, how you understand the other side's constraints, and whether you can influence a better outcome while preserving trust. At higher levels, they also look for judgment about scope: what kinds of decisions you choose to challenge, and how you do so without creating unnecessary friction.
Key Insights
- Pushback is strongest when it is in service of a meaningful outcome, not personal preference. Pick an example where the decision mattered and explain the risk you were trying to prevent or the value you were trying to protect.
- Conflict doesn't need to be emotional. You will sound stronger if you show that you got curious about the other person's constraints, incentives, or risk tolerance instead of treating the situation as 'they were wrong and I was right.'
- You should show judgment both before and after the pushback: why you chose to speak up, how you calibrated your approach, and how you moved forward once a decision was made.
What interviewers probe atlevel
Top Priority
Even at junior level, interviewers want to see curiosity: learn why the request was made before deciding how to challenge it.
Good examples
🟢Before pushing back, I asked what deadline pressure they were under and learned they were trying to unblock a demo later that week.
🟢I set up a quick conversation to understand why they wanted the change, and it turned out they were reacting to a recent bug report from support.
Bad examples
🔴I knew the request didn't make sense, so I told them we shouldn't do it without really getting into their reasons.
🔴When my teammate pushed for a shortcut, I assumed they just wanted to avoid extra work and argued against it.
Weak answers assume bad judgment or bad intent; strong answers show the candidate investigated the underlying constraint.
Valuable
Example answers atlevel
Great answers
In my last internship, a teammate suggested we skip automated tests for a checkout change so we could make a demo deadline. I pushed back because I had worked through that code path already and knew a small bug there would be visible immediately to users. Before arguing for a delay, I asked what the real constraint was, and it turned out the demo only needed one happy path to work. I suggested we keep the tests for the risky parts and reduce the demo scope slightly instead of removing safeguards entirely. My teammate agreed, we finished on time, and the demo went smoothly. What I took from that was that pushback lands better when I understand the real need and bring an alternative, not just a warning.
During my campus IT job, a supervisor asked me to reset a whole row of student printer accounts after a few people complained they couldn’t log in. I pushed back because I had checked the error messages and noticed the problem only affected students who had changed their passwords that day, so resetting everyone would have caused unnecessary disruption. I explained that we could fix it faster by updating just the affected accounts and putting a short note at the front desk for anyone else with the same issue. My supervisor agreed, and we solved it in about 20 minutes instead of turning it into a much bigger problem. I learned that pushback is really about protecting people from avoidable work, and it goes over well when you bring a simpler option with it.
Poor answers
A senior engineer wanted me to build a feature a certain way, but I thought it was overcomplicated. I told him there was no point doing all that and that my version would be faster. We went back and forth for a while, and eventually he let me do it my way. It worked for the feature, so I think that was a good example of pushing back instead of just accepting things.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid August, 2026
Mid June, 2026
Mid June, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.