Convincing Others of Your Approach

“Tell me about a time you convinced others to adopt your approach.”

This question evaluates your influence skills — how you get buy-in from stakeholders, peers, or leadership without relying on positional authority. In senior roles, your ability to persuade is as important as your technical judgement.

---

Why Interviewers Ask This

• Persuasion strategy: Did you understand your audience’s motivations or just push your agenda? Did you build coalitions or go solo?
• Stakeholder awareness: Did you identify who needed to be convinced and what would move them?
• Outcome quality: Was the adopted approach actually successful, or did you convince people of a bad idea?

---

The Common Traps

The Bulldozer

“I was confident my approach was right, so I went ahead and built it. Everyone saw it was better once it was done.” The Interviewer’s Perspective: You ignore stakeholder input and bypass collaboration. Teams don’t want someone who acts unilaterally.

The Data Dump

“I created a 40-slide deck with benchmarks, cost analysis, and projections. Surely the data speaks for itself.” The Interviewer’s Perspective: You think logic alone wins arguments. You didn’t address people’s concerns, emotions, or incentives.

---

The Blueprint for The Influence Model

Phase 1: Your Idea

What was your approach and why did you believe it was right? Describe the situation briefly — what problem you were solving and what alternatives existed.

Phase 2: Stakeholder Analysis

Identify who needed convincing and what their priorities were. A PM cares about timeline; an engineer cares about maintainability; a manager cares about risk. Show you understood these perspectives.

Phase 3: Persuasion Strategy

How did you tailor your messaging? Did you prototype something, share data in a digestible way, build allies first, or address concerns one-on-one before the group meeting?

Phase 4: Adoption Outcome

Was your approach adopted? Even more important: did it work? If parts were modified, show that you welcomed input — the best outcome is a better version of your original idea.

---

High-Impact Answer Example

[Idea] “I proposed migrating our CI from a self-hosted Jenkins setup to GitHub Actions. The team was comfortable with Jenkins and resistant to change. My reasoning was reduced maintenance overhead and faster pipeline times.” [Stakeholders] “The senior engineers cared about reliability and migration effort. The PM cared about delivery continuity — no downtime during the switch. I knew each needed different proof points.” [Persuasion] “I ran a pilot on one low-risk repo: documented the setup time, pipeline speed, and any issues. I shared a one-page comparison with the team showing Jenkins vs. Actions for our specific patterns. Then in the planning meeting, I referenced the pilot data and offered to handle the migration myself to minimize team disruption.” [Outcome] “The team agreed to a phased migration. We moved all repos over three sprints with zero downtime. Build times dropped 40%, and the senior engineer later told me the pilot data made the decision easy.”

---

Checklist for Your Response

• The Empathy: Did I show I understood others’ concerns and tailored my approach to address them?
• The Evidence: Did I provide proof-of-concept, data, or a pilot rather than just arguing?
• The Collaboration: Did I involve others and incorporate their feedback, or did I bulldoze?
• The Result: Did the adopted approach deliver measurable value?