Why interviewers ask this

Almost every job above entry level involves managing someone you do not report to and cannot simply outrank, a client, an executive sponsor, a partner team lead with different priorities. Interviewers use this question to see whether you can influence without authority and keep a working relationship functional even when someone is being unreasonable. It also reveals whether you default to blaming the other person or take some ownership of how the friction developed.

How to structure a strong answer

Describe the stakeholder's role and what specifically made them difficult to work with, vague or shifting requirements, unresponsiveness, an aggressive communication style, so the interviewer understands the real challenge rather than a generic personality clash. Explain the approach you took to understand what they actually needed underneath the friction, and the concrete adjustment you made, more frequent check-ins, written summaries after calls, involving a third party. End with how the relationship or project outcome changed as a result.

Example answer

I once worked with a regional sales director who would frequently reject product mockups late in the cycle with feedback like 'this just isn't right' and no further detail, which was derailing our sprint timelines. Rather than pushing back on the vague feedback directly, I set up a 30-minute working session where I asked him to walk through three specific customer scenarios he was picturing when he rejected the designs. It turned out his real concern was that the new flow added an extra click for his highest-volume customers, something he had never articulated clearly. Once I understood that, I redesigned around preserving that shortcut, and his feedback became specific and constructive for the rest of the project because he trusted that I was actually listening to the business concern behind his pushback.

Common mistakes to avoid

Do not use this question to vent about a boss or coworker, interviewers specifically ask about stakeholders to keep the story external to your direct reporting line, so keep the tone professional either way. Avoid stories that end with you simply escalating the person to someone else without attempting resolution first. Also avoid painting yourself as flawless, a brief acknowledgment of your own early misstep in the relationship makes the story more believable.

Get real-time help in your next interview
Live Interview Help listens to your interview and surfaces personalised answers in real time. Free 20-minute trial on Google Meet, Teams, and Zoom.
Install Free on Chrome
Check your CV against the job description first
Free AI-powered CV Match Check scores your CV against any job description: missing keywords, weak impact metrics, and ATS parsing risk, before you even apply.
Check My CV Free

Frequently asked questions

What if the stakeholder never actually improved?
That is a valid story too, as long as you show you managed the relationship professionally and found a way to keep the project moving despite the friction, for example by getting agreements in writing or looping in a shared manager appropriately.
Can I name the stakeholder's job title or company?
Job title and general role are fine and add credibility. Avoid naming the company or the person if it is identifiable and the story is unflattering to them, since that can come across as indiscreet.

Before your next interview, it helps to have the fundamentals down. Our complete guide to preparing for a job interview covers the basics, and the STAR method is a reliable way to structure almost any answer under pressure.

Try an AI mock interview free
A real voice interviewer that questions you, drills into weak spots, and scores your answers, grounded in your actual CV and the job description.
Try a Mock Interview Free