Give me an example of how you have changed the direction or view of a specific function/department and helped them embrace a new way of thinking.
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 influence how another group thinks, not just win an argument or get approval for your preferred solution. Interviewers want to understand how you identified the old mental model, understood why it existed, and helped others adopt a better one in a durable way. For more senior candidates, they are also judging whether the scope of the change matches your level and whether you changed behavior beyond a one-time decision.
“Tell me about a time you helped another team rethink how they approached a problem.”
“Describe a situation where you influenced a department to adopt a different operating model or decision framework.”
“Have you ever changed how a cross-functional group thought about an issue? What did you do?”
“What's an example of shifting another function from an old mindset to a new one?”
“Walk me through a time when you had to persuade a department to see things differently in a lasting way.”
Key Insights
- You should make the old view sound reasonable before you explain why it needed to change. If the other function just sounds uninformed or stubborn, you often come across as low-empathy and less credible.
- This is usually not about persuasion alone; it is about diagnosis. Show that you understood the incentives, fears, constraints, or past experiences that made the existing way of thinking attractive.
- Don't stop at 'they agreed.' Explain what actually changed afterward: decision criteria, operating norms, metrics, process, or repeat behavior. Interviewers are looking for durable influence, not a single successful pitch.
What interviewers probe atlevel
Top Priority
At junior level, you do not need to overhaul a department, but you should show curiosity about why people saw the problem differently before you tried to change their mind.
Good examples
🟢At first I thought they were blocking the change, but after I asked more questions I learned they were measured on stability and had recently dealt with a bad rollout, so I reframed the proposal around reducing risk.
🟢They preferred the existing process because it made handoffs predictable for them, and understanding that helped me suggest a smaller change that kept the predictability they cared about.
Bad examples
🔴They didn't want to do it my way because they were very set in their process, so I just kept explaining why my approach was cleaner until they agreed.
🔴The other team was focused on the wrong thing, and once I showed them my idea was faster, it was obvious we should switch.
Weak answers treat disagreement as ignorance; strong answers uncover the logic behind the original view and respond to it.
For junior candidates, the scope can be modest, but the change should matter to the work and persist beyond a single conversation.
Good examples
🟢I helped the team move from making ad hoc handoff decisions to using a simple checklist, and they kept using it on later work because it reduced missed steps.
🟢After I proposed a small trial, the group adopted the new review pattern for that project and then repeated it on similar work because it clearly reduced rework.
Bad examples
🔴I suggested we rename a few statuses so another team understood them better, and they started using my labels after that.
🔴I convinced the designer to tweak the format of the document, which improved the discussion a lot.
Weak answers describe a minor preference change; strong answers show a meaningful shift in how work got done afterward.
Valuable
At staff level, interviewers want to see that you translate a mindset shift into mechanisms, adoption, and measurable business or operational impact.
Good examples
🟢I converted the new way of thinking into concrete artifacts like review criteria, rollout stages, and owner expectations, then monitored adoption across teams.
🟢I followed through until we had evidence that the changed view was improving outcomes, not just changing language in meetings.
Bad examples
🔴I set the direction and trusted the teams to operationalize it because they understood the goal.
🔴Once the department agreed with the proposal, my role was mostly complete.
Weak answers stop at strategic influence; strong answers operationalize the change and prove impact.
Example answers atlevel
Great answers
On a recent project, our design team wanted engineering to wait until every edge case was specified before we started implementation. I understood why they worked that way, because they had seen rushed builds create rework before, but in this case it was slowing feedback a lot. I suggested that we split the work into a small first version with the highest-confidence flows, and I put together a simple list showing what was safe to build now versus what still needed design decisions. After we tried that on one feature, the team saw that they could get earlier feedback without losing quality, and they used the same approach on the next couple of features too. What I think changed was not just that one decision, but their view that engineering had to wait for full completeness before meaningful work could begin.
On a small product team where I worked, the product managers always pushed to pack sprints with visible new features and ignored maintenance work, which left engineers firefighting. I sketched a simple three-point rubric (user impact, frequency, and maintenance cost) and volunteered to score a subset of the backlog with one of the PMs for two sprints as a trial. After we presented the scored backlog, the PMs moved a few medium-priority maintenance items up, and we noticed fewer repeat incidents and quicker fixes for small regressions. Because the rubric made the trade-offs concrete, the product team started reserving a fixed portion of each sprint for upkeep and used the same scoring when planning future roadmaps.
Poor answers
I changed the way another team thought about our tickets. They wanted a lot more detail up front, but I felt that was unnecessary, so I pushed back and said we should just start building and figure out the rest as we go. Eventually they agreed and we moved faster after that. It was a good example of getting people to stop overthinking and be more practical.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late November, 2025
Meta
Staff
Early July, 2025
Meta
Staff
Mid January, 2025
Amazon
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.