Interviews

Prepare these five stories before your next interview

Build a small bank of honest work examples so you can explain your contribution, decisions and results with confidence.

By Apliq · 2 Oct 2026

“Tell me about a time when...” is easier to answer when you have already chosen a few real examples. You do not need a script for every possible question. Prepare a small collection of experiences you understand well, then choose the one that fits the conversation.

Five stories are a useful starting point. They can come from paid work, an internship, a course project, volunteering or a personal project. Make the context clear so the interviewer understands the scope.

1. A problem you helped solve

Choose a situation where something was unclear, slow or not working. Explain how you understood the problem, what options you considered and what you personally did.

The example does not need to be dramatic. Finding a reporting error or simplifying a handover can reveal more about your thinking than a large project described vaguely.

2. A time you worked with others

Pick a situation that required coordination, feedback or a difference of opinion. Describe what the team needed and how you helped it move forward.

Use “we” when describing the team's result and “I” when explaining your own actions. Give colleagues credit without making your contribution disappear.

3. Something that did not go to plan

Choose an example you can discuss honestly. Explain what happened, what you were responsible for and what you changed afterwards.

Avoid turning every setback into a disguised strength. A thoughtful explanation of a mistake, including what you would now do differently, is more useful than pretending the work was flawless.

4. A skill you had to learn

Describe why you needed the skill, how you learned it and where you applied it. Include how you checked that your work was correct or asked for help.

Be precise about your current level. Completing one project with a tool is valuable evidence, but it is different from being an expert in it.

5. A result you are proud of

Choose an outcome relevant to the role. Use numbers if you know how they were measured and can explain your contribution. Otherwise, describe an observable result: a process was adopted, a deliverable was accepted or a recurring issue was resolved.

Do not disclose confidential customer details or internal information. You can explain your reasoning and contribution while keeping sensitive details general.

Give each story a simple structure

Use the STAR framework as a set of notes:

• Situation: What was happening?
• Task: What did you need to achieve?
• Action: What did you actually do, and why?
• Result: What changed, and what did you learn?

Keep the setup short and spend most of your answer on your actions. Practise a concise first version, then prepare the details an interviewer might ask about. Avoid memorising every sentence; leave room to answer the question you were actually asked.

Match your examples to the vacancy

Read the job description again and connect each main responsibility to one of your stories. If you lack direct experience, explain the closest relevant example and the gap honestly. Do not reshape the facts to force a match.

Check that your examples are consistent with the resume you submitted. Prepare a few questions of your own, such as how the team defines success in the first few months and which problems the new hire will work on.

After the interview, note what you were asked and which examples were clear. That record becomes useful preparation for your next conversation, whatever the outcome.