Tell Me About a Time You Persuaded Someone: Complete Graduate Interview Guide 2026

"Tell me about a time you persuaded someone" (or "convinced a colleague", "influenced a decision", "got buy-in for an idea") appears in graduate and early-career interviews across consulting, finance, technology, retail and the public sector. The reason is simple: almost nobody in a junior role has the authority to simply tell people what to do. Analysts need senior colleagues to use their numbers. Consultants need clients to accept recommendations. Engineers need product managers to prioritise a fix. In all of these situations, your ability to get things done depends on your ability to change minds through argument, evidence and relationship rather than rank.

Interviewers also use this question as a window into several other qualities at once. A good persuasion story shows how well you understand other people's priorities, how you use data, how you handle resistance, and whether you can accept a "no" gracefully. The table below sets out what is being listened for as you speak.

Because this is a behavioural question, the standard approach is to structure your answer with the STAR method. This guide adds a framework designed specifically for influence stories, plus worked examples, employer angles and the mistakes to avoid. If you want a wider view of how interviewers score communication skills, see our communication interview questions bank.

The biggest decision you will make is which story to tell. Candidates often default to a dramatic example, such as talking a client out of cancelling a contract, when a smaller, more realistic story would be stronger. Interviewers for graduate roles do not expect you to have closed deals or swayed a board. They want evidence that you can bring someone round to a better idea in an everyday setting, and do so in a way that colleagues would be happy to be on the receiving end of.

The defining feature of a good persuasion story is that the other person started out disagreeing, hesitant or uninterested, and that they ended up genuinely agreeing, not merely complying. If someone simply did what you asked because you were the team leader, or because everyone already agreed, you have not shown persuasion.

Persuasion versus manipulation

Interviewers are alert to the difference between persuasion and pressure. Stories in which you won someone over by flattery, exaggeration, withholding information, or getting senior people to side with you behind someone's back can raise red flags, even if you got the outcome you wanted. In regulated industries such as banking, audit and law, the way you influence matters as much as the result.

Strong stories use legitimate levers: listening to concerns, presenting evidence, offering a low-risk trial, linking your idea to the other person's goals, and being open about the downsides. Weak stories rely on charm, persistence alone, or "wearing them down". If you recognise your own story in the second list, look for a different one. Our guide to conflict resolution answers covers how to describe disagreements constructively.

Standard STAR works for persuasion stories, but the middle of the story matters most and is easy to rush. The HEARD framework keeps STAR's discipline while making sure you show the steps that interviewers value: understanding the other person first, then building an argument that fits them. It is named for the central lesson of influence: people are far more willing to change their mind once they feel they have been heard.

Worked through in one paragraph

"In a group project on retail pricing, three of us wanted to use a regression approach but one teammate insisted on a simpler comparison of averages because it was faster (Hurdle). I asked him why, and learned he was worried about the deadline and about not understanding the regression output well enough to present it (Explore). I suggested we run both methods on a small subset of the data that evening and compare the results, and I offered to walk him through the output afterwards. The simple comparison missed a clear seasonal effect that the regression picked up (Argue). He then asked whether we could still finish on time, so I proposed splitting the work so he owned the data cleaning, which he was strong at (Respond). We used the regression, submitted a day early, and received positive feedback on the depth of analysis. I learned that people resist ideas more because of a specific worry than because they dislike the idea itself (Deliver)."

Speak in the first person for the Argue and Respond steps. Even when a team effort was involved, the interviewer needs to hear what you personally said and did. For help turning a good story into a crisp opening, see our guide to answering "tell me about yourself", which covers concise storytelling.

The examples below illustrate structure; they are not scripts. The details are invented for demonstration, and your own answer must be based on real experience, because interviewers will probe with follow-up questions and expect depth. Use these to see how HEARD adapts to different kinds of material.

Example 1: The rota that kept clashing

"At my part-time job, the rota was written a week at a time and staff kept having to swap shifts at the last minute, which caused stress and the occasional understaffed shift (Hurdle). My manager felt the current system was fine because it had always worked and changing it would take her time. I asked what worried her most and she said she did not want to spend extra hours on admin (Explore). For two weeks I noted every swap and gap, which came to nine, and I drafted a two-week rota template that could be filled in under ten minutes. I showed her the nine swaps, explained the time they cost her in messages, and offered to prepare the first one myself (Argue). She was concerned some people would dislike committing early, so I suggested a one-month trial with a feedback check-in rather than a permanent change (Respond). She agreed, last-minute swaps dropped noticeably during the trial, and she kept the new format. I learned that making the change small and reversible makes it much easier for people to say yes (Deliver)."

Example 2: The placement template

"During my placement, I noticed the team's monthly report used a layout that made the same numbers appear in three places, which led to occasional mismatches (Hurdle). A senior analyst who had built the original was reluctant to change it, partly because she thought a new layout might confuse the managers who read it (Explore). I did not argue with her; instead I rebuilt one live report in a cleaner layout, kept her original summary page unchanged, and asked her to compare the two. I also showed her that the new version took roughly half the time to update (Argue). She raised a fair point about one chart the managers liked, so I kept that chart and adjusted the rest (Respond). She agreed to use the template for the next report and later recommended it to another team. I learned that respecting what someone has built, and asking for their input, makes them part of the change rather than the target of it (Deliver)."

Examples 3 and 4: Using the table as a prompt

The economics and society examples follow the same pattern. In the group project story, the differentiator is that you tested both approaches rather than just asserting yours was better; in the society story, it is that you gathered member feedback so the committee was responding to data rather than your opinion. Write each in full and time it. Wherever you run out of detail, your real experience probably has more to offer, or you should choose a different story.

The wording of the question is broadly similar across employers, but each organisation emphasises slightly different qualities. Do not pretend to share a company's values in a cynical way. Instead, use what employers say publicly to decide which part of your story to lead with.

Amazon's Leadership Principles are published on its careers site and widely discussed by candidates. Read them there and choose a story that naturally maps to Have Backbone; Disagree and Commit or Earn Trust. Our Amazon online assessment guide covers the wider process, and the Microsoft online assessment guide does the same for Microsoft.

At professional-services firms, interviewers often follow up with "how did the other person react?" and "what would you do differently?" Be prepared for both. The Big Four process commonly combines online tests, a video interview and a final-round interview, and you can see how one firm structures this in our PwC assessment centre guide. At assessment centres, persuasion is also observed live in group exercises, which our group exercise guide explains.

Interviewers rarely use identical phrasing. If you understand what each variation is really probing, you can reuse the same prepared story and simply shift the emphasis.

The "sell an idea" variant needs care because it can pull you towards a sales-pitch tone. Interviewers do not want to hear a rehearsed speech; they want to hear how you read the room. A good answer includes a moment where you changed your pitch because of how the other person responded.

Another common form is the situational version: "How would you persuade a colleague who refused to follow a new process?" Here the interviewer wants to hear that you would first understand the reason for the resistance, then address it with evidence or a small trial, and escalate only if necessary. The same sequence as HEARD applies, just in the future tense.

These are the patterns that most often turn a promising example into a weak one.

Mistake two is particularly common. Persistence is a useful quality, but interviewers are assessing whether you can influence with substance. If your only tactic was repeating yourself, the story will sound like nagging. If your genuine story is mostly persistence, look for the moment you changed approach, such as finding a new fact, finding a better messenger, or addressing a concern you had missed, and build the answer around that.

To rehearse, record yourself answering aloud and listen back for these patterns, or ask a friend what they remember afterwards. If nerves are a problem on the day, the techniques in our guide to managing SHL test anxiety also work well in interviews.