Describe a time when you took an unpopular stance in a meeting with peers and your leader.
Asked at:
Meta
Amazon
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
This question tests whether you can disagree constructively when there is social pressure to go along with the room. Interviewers want to see judgment about when to push back, how you do it, and whether you stay collaborative rather than oppositional. At senior levels, they are also testing whether your dissent improved the decision quality for the group, not just whether you were willing to be contrarian.
“Tell me about a time you disagreed with your manager and teammates in a meeting. How did you handle it?”
“Describe a situation where you were the dissenting voice in the room.”
“Have you ever pushed back on a decision that your lead and peers were leaning toward? What happened?”
“Walk me through a meeting where you challenged the group's direction even though it was unpopular.”
“What's an example of a time you spoke up against the consensus in front of leadership?”
Key Insights
- You do not get credit just for disagreeing. You need to show that your stance was grounded in reasoning, risk awareness, or evidence rather than personal preference.
- An 'unpopular stance' is not the same as being combative. Show that you understood why others disagreed and that you engaged their constraints respectfully.
- Do not end the story at 'I spoke up.' The strongest answers explain what happened after the meeting, how you helped move the group forward, and what the outcome says about your judgment.
What interviewers probe atlevel
Top Priority
Your story should not end at speaking up; show that your input helped the team make a better decision or reduce risk.
Good examples
🟢After the meeting, we ran a quick check on the issue I raised and found the edge case was real, so we adjusted the plan before release.
🟢Even though the team kept the original direction, we added a safeguard I proposed, which reduced the risk and let us ship on time.
Bad examples
🔴I said my piece in the meeting, and after that it was up to the lead to decide.
🔴They did not fully agree, but at least I made my opinion known and moved on.
Strong answers show follow-through and impact; weak ones treat dissent itself as the accomplishment.
Even when you disagree, show that you assumed your teammates and lead were reasonable people operating under real constraints.
Good examples
🟢I understood the team wanted to hit the date, so I framed my concern around a smaller change that would still protect the release.
🟢Before pushing harder, I asked a few questions and realized the others were optimizing for simplicity, which helped me tailor my suggestion.
Bad examples
🔴They were rushing and not thinking it through, so I had to be the one to point out the obvious problem.
🔴My lead just wanted to move fast, and the others followed along, so I kept repeating my point until they gave in.
Strong answers humanize the other side and engage their incentives; weak ones reduce disagreement to others being careless or wrong.
At junior level, interviewers mainly want to see that you chose a meaningful issue to raise and did not confuse preference with principle.
Good examples
🟢I was the newest engineer, but I raised that skipping basic testing before launch could create customer-facing issues, and I explained the specific failure mode I was worried about.
🟢I disagreed with compressing the timeline because a dependency had not been validated yet, and I tied my concern to delivery risk rather than my own comfort.
Bad examples
🔴I pushed back because I thought my coding style was cleaner, and I kept arguing for it even though the difference was mostly cosmetic.
🔴I took an unpopular stance that we should use a tool I had used before, but I could not explain a concrete risk with the team's original plan.
Strong answers show the candidate picked a disagreement that mattered to outcomes; weak answers reveal they treated personal preference like a principled stand.
Valuable
It is good to speak up despite pressure, but maturity shows in being willing to update your view if the discussion changes your understanding.
Good examples
🟢I raised the concern even though I was junior, and when I learned a constraint I had missed, I shifted to a smaller recommendation that still addressed the risk.
🟢I was willing to be the only dissenting voice, but I framed it as a concern to test rather than assuming I had the full answer.
Bad examples
🔴I held my ground because I did not want to back down in front of everyone once I had spoken up.
🔴Even after my lead explained the tradeoff, I stuck to my position because I felt it was important to be firm.
Strong answers show principled flexibility; weak ones treat stubbornness as courage.
Example answers atlevel
Great answers
In one sprint planning meeting, the team wanted to combine two user-facing changes into a single release because it looked faster. I was the newest engineer in the room, but while testing my part I had found an edge case where a failed update could leave the page in a broken state. I said I was worried we were taking on unnecessary release risk and suggested we ship the smaller change first and keep the second one behind a flag until we verified the behavior. My lead initially preferred the original plan because we were trying to hit a date, so I walked through the exact scenario I had reproduced and offered to do a quick check that afternoon. We confirmed the issue, split the release, and still hit the deadline for the first part. What I was proud of was not just speaking up, but framing it around a concrete risk and a workable adjustment rather than just saying no.
During a planning meeting for a demo to a potential customer, everyone — including our lead — agreed we should cut scope and skip accessibility checks to get visuals polished faster. I disagreed and argued we should at least ensure keyboard navigation and proper labels for form fields, because accessibility isn't just legal risk for some customers, it's how a lot of people actually use software; I also mentioned that the customer we were demoing to had accessibility experts on their team. My suggestion was unpopular at first, so I offered to take the work off the designers' plates and implement the minimal fixes within the day so it wouldn't delay the demo. After I added proper labels, focused outlines, and fixed tab order, the demo went smoothly and the customer commented positively on how usable the interface felt. I felt good that I stood up for underrepresented users and showed a small, practical way to balance speed with responsibility.
Poor answers
I had a meeting where everyone wanted to use one approach and I said we should do it differently. I felt pretty strongly because I had seen a cleaner way to build it in a class project, so I explained that my version would be better long term. My lead still wanted to move ahead with the original plan, but I kept making the point so they knew I disagreed. In the end they went with their approach, but I think it was good that I stood my ground and showed conviction.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early October, 2025
Meta
Senior
Mid December, 2024
Amazon
Mid-level
Describe a time when you disagreed with a group or took an unpopular stance
Late October, 2024
Amazon
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.