Home / Tools / STAR answer checker / Tell me about a time you handled a difficult stakeholder

Behavioral question

Tell me about a time you handled a difficult stakeholder

Difficult should mean a real constraint: a customer who wants a date you cannot hit, a sales lead who promised a feature, a partner with a contract. It should not mean “they were annoying.” Show how you learned what they actually needed and what you changed.

Check this example, then replace it

The box starts with one STAR answer. Read the scores, then delete it and paste a story from your own work. Scoring stays in the browser.

Question (optional) Your answer In July 2023 a sales lead had promised a prospect a custom export we did not have. The prospect was the stakeholder, and the deal was stuck. I was responsible for a version we could support after the contract. I called the prospect, asked which two columns their analyst opened every morning, and wrote those into the existing export instead of a new product. I then sent a sample file the same day and asked sales to strike the custom-build line from the order form. The result was the prospect signing that week, zero new services to maintain, and the sample file becoming the default for the next 6 deals. Support questions about exports dropped from 15 a week to 4. I saved the sample in the sales folder with the two column names labeled, so the next call did not start from a blank document.

Check answer Tighten with AI

86/100

Strong

About 59 seconds spoken · 147 words. Spoken time uses 150 words per minute.

Situation70

Task74

Action94

Result92

Feedback

• This has a clear STAR shape. Only keep numbers you can defend out loud.

Which sentence is which

In July 2023 a sales lead had promised a prospect a custom export we did not have. Situation The prospect was the stakeholder, and the deal was stuck. Unclear I was responsible for a version we could support after the contract. Task I called the prospect, asked which two columns their analyst opened every morning, and wrote those into the existing export instead of a new product. Action I then sent a sample file the same day and asked sales to strike the custom-build line from the order form. Action The result was the prospect signing that week, zero new services to maintain, and the sample file becoming the default for the next 6 deals. Result Support questions about exports dropped from 15 a week to 4. Result I saved the sample in the sales folder with the two column names labeled, so the next call did not start from a blank document. Action

Tightened draft

Copy

In July 2023 a sales lead had promised a prospect a custom export we did not have. I was responsible for a version we could support after the contract. I called the prospect, asked which two columns their analyst opened every morning, and wrote those into the existing export instead of a new product. I then sent a sample file the same day and asked sales to strike the custom-build line from the order form. I saved the sample in the sales folder with the two column names labeled, so the next call did not start from a blank document. The result was the prospect signing that week, zero new services to maintain, and the sample file becoming the default for the next 6 deals. Support questions about exports dropped from 15 a week to 4. The prospect was the stakeholder, and the deal was stuck.

Why this example holds up

You treat the stakeholder as someone with a job to do. The action is a question plus a smaller promise. The result is a signed deal and less support load, which is the part engineering managers listen for.

How to answer “Tell me about a time you handled a difficult stakeholder” with STAR

1. Situation. Set the scene in one or two sentences: when it was and what was already wrong. For example: In July 2023 a sales lead had promised a prospect a custom export we did not have.
2. Task. Say what you personally owned. For example: I was responsible for a version we could support after the contract.
3. Action. Say what you did, in order, with I. For example: I called the prospect, asked which two columns their analyst opened every morning, and wrote those into the existing export instead of a new product.
4. Result. End on the change, with a number you can defend. For example: The result was the prospect signing that week, zero new services to maintain, and the sample file becoming the default for the next 6 deals.

Mistakes on this question

• Complaining about sales. The interviewer may have been in sales, or may have to work with them.
• Building the custom thing they asked for, with no push toward a smaller version.
• No evidence you talked to the stakeholder. Relaying through a project manager hides you.

How to practice it

Replace the word difficult with the person’s constraint. If the story gets clearer, you were describing a person, not a problem.

FAQ

Can the stakeholder be a customer?

Yes. Customers are the cleanest version of this question because their constraint is usually concrete.

What if I could not give them what they wanted?

Say the no, the alternative you offered, and whether they took it. A clean no with a sample is a complete story.

Related questions

• Tell me about a time a customer was unhappy
• Tell me about a time you persuaded someone
• Tell me about a time you influenced without authority

Back to the STAR answer checker