Tell Me About a Time You Showed Initiative: Complete Graduate Interview Guide 2026

"Tell me about a time you showed initiative" (or "took the lead without being asked", "went above and beyond", "spotted a problem nobody else had") is a staple of competency-based interviews for graduate schemes, internships and early-career hires. The reason is practical. A new starter who only does exactly what is written on the task list needs constant direction, which costs the team time. A new starter who notices gaps, asks smart questions and gets on with useful work quickly becomes someone the team relies on.

Interviewers also know that initiative is hard to fake. You cannot demonstrate it with a personality adjective such as "proactive" or "self-motivated"; you can only show it with a specific story where you saw something, decided to act, and did. The table below shows 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 tuned to initiative stories, plus worked examples, employer angles and the mistakes to avoid.

Many candidates struggle here because they assume initiative means something grand: founding a society, launching a product, leading a campaign. In reality, interviewers for graduate roles are looking for evidence of a habit, not a headline. Initiative can be as modest as noticing that new members of a society never received a proper welcome and creating a one-page guide, or spotting a recurring error in a spreadsheet at a part-time job and building a check to catch it.

The defining feature is that nobody told you to do it. If your manager assigned the task, it was diligence, not initiative. Diligence is valuable too, and there are other questions for it, but this question needs a story where the impetus came from you.

Initiative versus overstepping

There is a balance. Interviewers at banks, law firms and consultancies work in regulated, hierarchical environments. A story in which you ignored a process, went around your manager or made an unauthorised decision can backfire, even if the outcome was good. Strong answers show that you checked before acting where appropriate: "I suggested the idea to my supervisor, got the go-ahead and then built it." That demonstrates initiative and judgement together, which is exactly the combination employers want.

For a wider view of how initiative sits alongside other skills, see our initiative interview questions bank.

Standard STAR works well, but initiative stories have a particular shape: a trigger, a decision, an effort and an outcome. The SPARK framework keeps STAR's discipline while making sure the part interviewers care about most, why you chose to act and what you did, gets the airtime it deserves.

Worked through in one paragraph

"In my part-time role at a café, I noticed that the closing checklist was kept on scraps of paper and jobs like cleaning the coffee machine were often missed (Spot). I talked to my shift manager, who agreed I could try a fix, and I decided a simple shared checklist would work better than asking people to remember (Pick). I designed a one-page laminated checklist, tested it for two weeks and adjusted it after colleagues pointed out two missing tasks (Act). The manager adopted it across all shifts, and the number of missed-task notes in the handover log dropped noticeably over the next month (Report). I learned that small process fixes often have more impact than large ones, and I now look for repeated small errors whenever I join a new team (Keep)."

Speak in the first person for the Act step. Even when you worked with others, the interviewer needs to hear what you personally did. If you are unsure how to weave in numbers, our guide to answering "tell me about yourself" includes tips for quantifying achievements concisely.

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

Example 1: The study group with no plan

"In my second year our econometrics study group was meeting but not making progress; everyone was revising different topics and nobody felt prepared (Spot). I realised nobody was going to organise it, so I offered to draft a plan. I checked with the group that they'd follow it, then mapped the syllabus to the six weeks before the exam (Pick). I assigned each person a topic to teach, created a shared question bank, and asked the lecturer to confirm our list of core topics was right (Act). The group said they felt far better prepared, and several of us improved on our previous mark (Report). It taught me that taking the first step on organisation often unlocks everyone else's effort (Keep)."

Example 2: The internship report

"During my internship, I noticed the weekly sales report took a colleague roughly half a day of manual copying between spreadsheets (Spot). I asked my manager whether I could try to automate it alongside my main tasks; she agreed as long as the existing report ran in parallel until mine was checked (Pick). I spent a few evenings learning spreadsheet formulas and macros, built a template, tested it against three weeks of past reports and fixed two errors I found (Act). The team adopted it, and the report now takes under an hour (Report). I learned to check with stakeholders first and to run old and new processes in parallel, which made my change easy to trust (Keep)."

Examples 3 and 4: Using the table as a prompt

The retail and society examples follow the same pattern. In the retail story, the differentiator is that you proposed a recurring process rather than a one-off fix; in the society story, it is that you tackled an unglamorous but important problem (funding) without being asked. Write each in full and time it. Wherever you find yourself wanting to add detail, your real experience probably has something worth including. Wherever you run dry, choose another story.

The wording of the question is broadly the same 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 published Leadership Principles are widely discussed by candidates, so if you are applying there, read them on Amazon's own careers site and choose a story that naturally maps to Ownership or Bias for Action. Our Amazon online assessment guide covers the wider process. For Microsoft, see the Microsoft online assessment guide.

At the professional-services firms, interviewers frequently follow up with "how did your manager react?" and "what would you do differently?" Be ready for both. The Big Four process often combines online tests, a video interview and a final-round interview; you can see how one firm structures this in our PwC assessment centre guide. For banks, the HSBC online assessment guide shows how competency questions fit into the wider selection process.

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

The "went above and beyond" variant needs special care, because it can tempt candidates to describe working unreasonably long hours. Employers generally want to see efficient, smart extra effort, not burnout. A better story shows that you found a valuable extra thing to do, not simply that you did more of the same thing for longer. If the only thing you did was stay late, the interviewer will likely ask "what was the impact?" and you will need a good answer.

Another variant is the situational version: "What would you do if you noticed a problem that was not your responsibility?" Here the interviewer wants to hear that you would raise it with the right person, offer to help, and avoid both ignoring it and acting unilaterally. The same balance between proactivity and judgement applies.

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

Mistake two is particularly common. Many candidates mistake having an idea for taking initiative. The idea is only the start; interviewers want to hear the harder middle: how you persuaded people, dealt with setbacks and finished the job. If you only have an idea story, see whether you can push it further in real life before your interview: even a small trial of your idea can turn a weak story into a strong one.

To rehearse, record yourself answering aloud and listen back for these patterns, or ask a friend what they remember afterwards. If your nerves run high before interviews, our guide to managing SHL test anxiety includes techniques that also help on the day of an interview.