Tell me about a time you championed an idea, initiative, or person that others were hesitant about
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 influence when there is uncertainty, skepticism, or perceived risk. They want to see whether you picked something worth advocating for, understood why others hesitated, and moved the situation forward through judgment rather than force. At higher levels, they are also looking for scope calibration: did you champion something appropriate to your level, and did you do it in a way that built trust instead of burning it?
Key Insights
- You do not need a dramatic battle story. The strongest answers often involve thoughtful advocacy around real concerns like risk, timing, competing priorities, or trust in an unproven person or idea.
- Do not frame hesitation as ignorance. Show that you understood why reasonable people were cautious, then explain how you reduced that risk or uncertainty.
- You should make clear what changed because of your effort. 'I raised it' is weaker than 'I gathered evidence, adapted the proposal, and helped others get comfortable enough to act.'
What interviewers probe atlevel
Top Priority
You do not need to solve politics at junior level, but you should show curiosity about why people were hesitant instead of treating pushback as an obstacle to push through.
Good examples
🟢I asked my mentor what worried them, and it turned out they were concerned about introducing bugs late in the sprint, so I suggested a smaller change first.
🟢When the team was hesitant about letting the newer engineer own the fix, I learned the concern was support load, so I proposed pairing on review and keeping the scope small.
Bad examples
🔴People seemed resistant, so I just kept repeating that my idea was simpler and would save time.
🔴My lead said they were unsure, but I assumed they hadn't looked closely enough and I tried to be more assertive.
Strong answers show the candidate uncovered the real concern and adapted; weak answers treat hesitation as something to overpower.
Valuable
Example answers atlevel
Great answers
In my first year, I noticed a signup form was accepting malformed input, and support was manually cleaning up a surprising number of cases. I suggested adding a small validation step, but the team was hesitant because we were close to release and didn't want to create new bugs. I asked my mentor what the main concern was, then put together a very small change with test cases using examples from recent support tickets. That made it easier to review, and we shipped it behind a simple check in the next patch release. Over the next couple of weeks, support saw fewer bad submissions, and it taught me that when people hesitate, it's usually because they're protecting something important, so a smaller, lower-risk version of the idea often works better.
At my last internship, I was helping on a small internal dashboard, and one of the support reps kept asking whether we could add a simple status note field for customers. A few people thought it would be extra work for very little benefit, since the dashboard already showed the main case details. I spoke with the support rep directly and learned they were copying and pasting the same update into three different tools all day, which was wasting time and sometimes causing inconsistent messages. I brought that back to my team and suggested we try a lightweight version first, just a basic note field with no extra workflow changes. My lead agreed, and once we added it, the support team said it saved them several minutes per case and made communication much clearer. That experience taught me to listen for the person closest to the problem and advocate for practical changes that make their work easier.
Poor answers
I once really pushed for reorganizing part of our code because it was getting messy and hard to read. Some people didn't seem excited about it, but I kept bringing it up and explained that cleaner structure would help us move faster later. Eventually I got permission to do it, and I spent a few days cleaning it up. I think it showed that I'm willing to stand by a good idea even if other people don't see it right away.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early July, 2026
Late March, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.