Tell Me About a Time You Were Creative: Answer Framework and Examples

"Tell me about a time you were creative" is a behavioural question, which means the interviewer is not interested in your opinion of yourself. They want a real story they can examine. The reasoning behind it is straightforward: most graduate and early-career jobs involve problems that do not come with a manual, such as a client request that does not fit the usual process, a tight budget, or a team that keeps running into the same obstacle. An employer wants to know how you behave in those moments.

Many candidates freeze because they equate creativity with art, design or invention. In a recruitment context it almost always means something more practical: noticing that the usual approach is not working, coming up with an alternative, and making it happen. A change to a spreadsheet, a better way to run a society event or a new approach to a revision schedule can all qualify if you can describe the thinking behind it.

It also overlaps with other competencies. A creative solution to a hard problem is also a story about solving a difficult problem, and a self-started improvement often doubles as evidence of showing initiative. Knowing which angle the interviewer wants lets you emphasise the right part of one story.

The most common reason candidates give a weak answer is that they dismiss their best material as "too small". Interviewers at graduate level do not expect you to have launched a product or restructured a department. They expect an example proportionate to your experience, told with enough detail that the thinking is visible.

A good test is to ask three questions about a candidate story. Was there a constraint, such as limited time, money, people or information? Did you choose a different approach from the default one? Can you show what changed as a result? If the answer to all three is yes, you have a usable example, however modest the setting.

Avoid examples where the credit properly belongs to someone else, or where your contribution was only carrying out an instruction. If the idea came from a team brainstorm, that is fine, but be clear about what you personally proposed or built. Our guide to team-based answers shows how to describe a shared effort while keeping your own role clear.

STAR (Situation, Task, Action, Result) is the standard structure, but creativity questions have a specific weakness: candidates spend all their time on the situation and jump straight to the result, skipping the thinking. The interviewer is left knowing what happened but not how your mind worked. A tweak that fixes this is to organise your action section around Idea, Test, Result.

Idea: show where it came from

Briefly set the context and the problem in two or three sentences, then explain how you arrived at your idea. Did you notice a pattern, borrow an approach from another area, or ask users what they wanted? Mentioning one alternative you rejected, and why, shows that your idea was a considered choice. For example: "I considered rewriting the whole guide, but with two weeks left I decided a one-page visual summary would be more realistic."

Test: show you did not just hope it would work

Strong candidates test an idea on a small scale before committing. That might mean trying a new format at one event, asking two colleagues to review a draft, or running a spreadsheet macro on a copy of the data. Describing this step signals maturity, because it shows you balance imagination with risk management, something employers in finance, consulting and engineering particularly value.

Result: quantify where you can, describe where you cannot

Finish with what changed. Numbers are ideal, such as hours saved, attendance figures or marks achieved, but only use figures you can stand behind. If there is no number, describe the observable effect, such as a manager adopting your template for the whole team. End with a one-sentence lesson or a link to the target role.

Aim for roughly two minutes when spoken, or about 250 to 300 words. That gives enough room for the idea and the test without losing the interviewer's attention. Our guide to the competency-based interview explains how interviewers score this type of answer.

Treat the examples below as templates. Replace the details with your own experiences, and keep your delivery natural rather than memorised word for word. Each is condensed; in an interview you can add a sentence or two of detail.

Example 1: Recent graduate (dissertation research)

"For my dissertation I needed data on how students budget, but I had no funding for a formal study. Instead of relying only on published research, I designed a short anonymous survey and shared it through course group chats and two society mailing lists. Before sending it out I tested the questions on five friends, and three of them misread one question, so I rewrote it. I received over 150 responses, which gave me original data that most of my peers did not have, and my supervisor highlighted it in her feedback as a strength. It taught me that a small test can save a large amount of rework."

Example 2: Society event

"As events officer for a student society, I noticed our termly formal dinners were losing money and attendance had halved. I asked members why, and the main answer was cost and time. I proposed a monthly informal evening in the students' union with a shared-cost format. I trialled one in October with a small budget, and 45 people came compared with about 20 at the previous dinner. We made the format permanent, and the society finished the year with a surplus for the first time in several years."

Example 3: Part-time retail job

"In my weekend job at a clothing store, new starters took a long time to learn where stock was kept, which slowed us down on busy days. I suggested a colour-coded labelling system for the stockroom and drew a simple one-page map. I tried it on one section first and asked two colleagues to find items using only the map. They did it quickly, so the manager let me roll it out to the whole room. New starters said they felt confident within a day or two, and the manager asked me to help with the same approach at the next peak season."

Example 4: Internship (process improvement)

"During my finance internship, I was asked to produce a weekly report by copying figures between three spreadsheets, which took about three hours. I wondered if it could be automated, so I spent an evening learning how to link the files with formulas. I tested the new version against the manual one for two weeks to make sure the numbers matched exactly. It reduced the task to under half an hour, and my manager asked me to share it with the rest of the team. I learned that checking accuracy before announcing a shortcut is what makes people trust it."

Example 5: Career changer

"In my previous role in a small charity we had no marketing budget but needed volunteers for a fundraising day. Instead of paid advertising, I contacted local sports clubs and offered them a team-building slot at the event in return for helpers. I started with one club to see if the idea worked; they brought eight volunteers. Three more clubs followed, and we had more helpers than we needed. I am now looking to move into marketing because this was the part of my role I enjoyed most."

The same story can land differently depending on the employer. Large recruiters publish values and competency frameworks on their careers sites, and reading them before an interview helps you decide which part of your story to emphasise. Always check the current wording on the employer's own pages, as frameworks change.

Amazon is a well-known example because its Leadership Principles are public. One of them is "Invent and Simplify", which expects people to look for new ways to do things and to simplify where possible. Amazon interviews are widely reported to be built around behavioural questions linked to these principles, so a story about removing a step from a process or finding a simpler approach maps naturally. Microsoft publicly emphasises a growth mindset, so a story that includes learning from an idea that did not fully work can be especially effective there.

Remember that for many large graduate programmes the interview comes after online testing. Employers such as banks and professional services firms commonly use numerical, verbal and logical or inductive reasoning tests earlier in the process, so it is sensible to practise those alongside your interview stories. Our graduate scheme aptitude tests guide covers what to expect.

A good interviewer rarely stops at your first answer. They probe to confirm that the story is real and that you understand your own role. Preparing for the follow-ups is often what separates a competent answer from a convincing one, because it forces you to think about details you would otherwise gloss over.

If your idea met resistance, include that honestly. A story where everyone instantly agreed can sound too neat. Describing how you handled a sceptical teammate or a manager's concerns shows interpersonal skill, and it ties in to persuasion, another common competency.

Most weak answers to this question fall into a few predictable traps. Knowing them in advance makes them easy to avoid.

One more subtle mistake is using a story that is really about hard work rather than a new idea. Staying up all night to finish a task is dedication, not creativity. Check that your story contains a moment where you chose a different approach, not just a bigger effort.

Good creative answers are built from real material, and that takes a little time to gather. Start several days before the interview rather than the night before. The aim is not to memorise a script but to know your story well enough to tell it naturally and handle follow-up questions.

Brainstorm three candidate stories

Write down every time you improved something, solved a problem without an obvious answer, or worked around a limit. Include university, work, volunteering and personal projects. Then shortlist three that have a clear constraint, a choice between options and a visible result. Having more than one lets you avoid repeating a story you have already used earlier in the interview.

Write it out, then cut it down

Draft the full story with the Idea-Test-Result structure, then cut it to about 250 to 300 words. Underline the sentences that show your thinking and make sure they survive the cut. Finally, read it aloud and time it. If it runs over two and a half minutes, trim the context.

Finally, do not neglect the earlier stages of the process. If your application includes online reasoning tests, a strong interview cannot help you if you do not get through the screening stage. Balance your time between story preparation and timed practice tests so that you are ready for every stage.