Graduate Interview Questions: Build a 7-Story Evidence Bank and Answer With STAR

A graduate interview becomes much easier when you stop trying to predict every possible question.

You do not need 30 polished scripts. You need a small bank of honest examples that show how you think, work with other people, make decisions and learn. Then you need enough practice to choose the right example without sounding as if you are reading it from memory.

This guide helps you build seven useful stories, turn them into clear answers and work out where STAR helps - and where it does not. The examples are GradSharp editorial scenarios, not real employer questions or accounts of real candidates.

If you are unsure whether your part-time work, coursework or volunteering counts, start with what counts as work experience for graduate jobs. The short answer is usually: it counts when you can explain what you did and why it mattered.

What can a graduate interview assess?

There is no single graduate interview format. One employer may ask for evidence of past behaviour. Another may focus on strengths, motivation, hypothetical situations or technical knowledge. A final interview may mix all of them.

The invitation and job description are more reliable than a generic question list. Read them first.

Question family	What the interviewer may be exploring	Example prompt	Best preparation	Weak response pattern
Motivation	Why this role, employer and type of work make sense for you	”Why did you apply for this role?”	Connect employer research to your own evidence and direction	Repeating the employer’s homepage
Competency or behaviour	What you actually did in a relevant situation	”Tell me about a time you solved a difficult problem”	Prepare specific examples and use a structure such as STAR	Describing what “we” did without clarifying your part
Strengths	What kinds of work engage you and how that shows up in practice	”What type of task brings out your best work?”	Identify genuine patterns and have a brief example ready	Naming a fashionable strength with no evidence
Situational	How you would reason through an unfamiliar scenario	”What would you do if two deadlines conflicted?”	Explain priorities, questions, trade-offs and escalation	Jumping to an answer before clarifying the situation
Technical or role knowledge	Whether you can apply relevant knowledge	”How would you check this analysis?”	Review the role, core concepts and your own projects	Bluffing when you do not know

STAR is most useful for competency questions because those questions ask for evidence from something that has already happened. It is less useful for a simple factual question or a direct explanation of why you want the role.

Build a seven-story evidence bank

Seven is not an employer rule. It is a manageable preparation system: enough range to cover common themes without creating a script for every imaginable question.

Choose stories you can discuss comfortably and truthfully. A small event where your decisions are clear is often stronger than a prestigious example where your role was vague.

Story to prepare	Useful evidence sources	What to write down	Questions it may support
Team outcome	Group project, sport, society, busy shift, volunteering	Your role, disagreement or obstacle, contribution and group result	Teamwork, conflict, collaboration, inclusion
Difficult problem	Coursework, customer issue, technical project, event problem	Facts available, options considered, decision and outcome	Problem solving, judgement, initiative
Clear communication	Presentation, tutoring, customer support, explaining technical work	Audience, what they needed, how you adapted and what changed	Communication, influencing, stakeholder work
Responsibility	Shift, event, budget, deadline, caring duty, project ownership	What depended on you, how you organised it and how you checked delivery	Leadership, reliability, planning
Setback and learning	Rejected idea, missed target, poor first attempt, project error	What went wrong, your response, feedback and changed approach	Resilience, self-awareness, learning
Customer or stakeholder judgement	Retail, hospitality, volunteering, committee, client project	Competing needs, boundaries, decision and follow-up	Service, empathy, prioritisation, integrity
Achievement or motivation	Degree choice, project, competition, sustained personal goal	Why it mattered, effort, result and connection to the role	Motivation, achievement, strengths, career direction

For each story, keep a private note with these prompts:

1. What was happening?
2. What was I personally responsible for?
3. What made the situation difficult?
4. What did I decide or do?
5. Why did I choose that approach?
6. What happened next?
7. What did I learn or change?
8. Which requirements in the job description does this story support?

Do not force one story to prove everything. If your group-project example shows analysis and teamwork but not leadership, that is fine. Give it the jobs it can honestly do.

No internship? Your evidence can still be credible

Many graduates dismiss their best examples because they did not happen in a corporate office.

A difficult Saturday shift can show prioritisation, customer judgement and calm communication. A dissertation can show planning, analysis and recovery when the original method does not work. A society event can show coordination and responsibility. Caring responsibilities can show organisation and reliability, although you never have to disclose personal detail you would rather keep private.

The important test is not whether the example sounds impressive. Ask:

• Can I explain my own decisions?
• Can I describe the context without exaggerating it?
• Is there a useful result, change or lesson?
• Does it help answer this particular question?

If your CV currently hides this evidence, use the graduate CV first-screen guide to make your contribution easier to see before the interview stage.

Use STAR without sounding like a script

The National Careers Service and UCD Careers Network both present STAR as a way to structure clear examples:

• Situation: enough context for the listener to understand the problem;
• Task: what you were responsible for;
• Action: what you did, how you did it and why;
• Result: what happened and what you learned.

The framework works best when it stays invisible. You do not need to announce, “The situation was…” and march through four labels. Tell a short, coherent story.

Most weak STAR answers spend too long setting the scene. The interviewer needs the course, workplace or project context, but the useful evidence is usually in your action: what you noticed, what you chose, how you involved people and how you checked the outcome.

Two details make an answer sound human rather than rehearsed:

1. Explain one reason behind your action.
2. Include one honest reflection, especially if the outcome was not perfect.

That reflection might be as simple as: “I would agree the decision criteria earlier next time, because we lost time debating options that solved different problems.”

Three worked interview examples

These are fictional GradSharp examples designed to show the difference between vague claims and usable evidence. They are not model answers to memorise.

Teamwork: move from “we” to your contribution

Question: Tell me about a time you worked with others under pressure.

Weak answer:

We had a group presentation with a tight deadline. We divided the work, worked really well as a team and received a good result.

The answer may be true, but the interviewer still cannot see what the candidate contributed.

Stronger answer:

In a four-person policy project, we reached the final week with two sections overlapping and no agreed recommendation. I suggested that we stop editing slides and list the three criteria in the brief. I then mapped each section to one criterion and asked the group to choose a single recommendation before we rewrote anything. That gave everyone a clear piece of work and removed the duplicate analysis. We submitted on time. The main thing I learned was to agree the decision first; otherwise a group can produce polished pieces that do not form one answer.

The stronger version does not pretend the candidate led everything. It makes one useful intervention visible.

Problem solving: show the decision, not just the rescue

Question: Give me an example of a problem you had to solve quickly.

Weak answer:

A customer was unhappy, so I stayed calm and solved the problem. They left satisfied.

Stronger answer:

During a cafe shift, a customer said an allergy request had not been reflected in the order. I paused the order rather than guessing, checked the written ticket and asked the kitchen lead to confirm which ingredients had been used. We replaced the item and explained the delay. After the shift, I suggested that allergy changes be repeated back when the order was entered. I could not diagnose the food risk myself, so the important decision was to stop and check with the person who could.

This answer shows judgement and boundaries. It does not turn an ordinary part-time role into something it was not.

Motivation: connect research to your own direction

Question: Why do you want this graduate role?

Weak answer:

You are a leading organisation with a great reputation and excellent training. I have always wanted to work for a company like this.

Stronger answer:

I am looking for a role where I can use analysis but still explain decisions to non-specialists. In my final-year project, the part I enjoyed most was turning the findings into a recommendation that another team could use. This role combines structured training with work across operations and client teams, which is a closer fit than a purely research-based position. Before the interview I also looked at the first-year responsibilities described on your careers page, particularly the mix of analysis and stakeholder work.

Motivation answers do not need a full STAR structure. They need a credible connection between the work, the employer and the candidate.

Check the quality of an answer

This is a self-review tool, not an employer scoring system.

Check	Clear evidence	Needs work
Relevance	The example answers the question asked	The story is impressive but answers a different question
Specificity	The listener can picture the task and constraint	The answer relies on adjectives such as “busy” or “difficult”
Personal action	Your decisions and contribution are visible	The answer is mostly “we” with no clear role
Reasoning	You explain why you chose the action	You list steps without showing judgement
Result or learning	Something changed, was delivered or was learned	The story stops immediately after the action
Credibility	You could answer a follow-up honestly	The example sounds inflated or over-rehearsed

Record yourself answering one question. Listen once for content, not voice or appearance. Can you identify the decision? Can you tell what you personally did? Is there a clean ending? Fix the missing evidence before worrying about polish.

Common graduate interview questions to prepare for

Do not write a complete script for each question. Use the list to test whether your evidence bank has enough range.

Motivation and fit

• Why this role?
• Why this organisation?
• Why this sector or type of work?
• What are you hoping to learn in your first year?
• What part of the job description interests you most?

Prepare these by connecting employer research to your own choices and evidence. “You are a market leader” is not a personal reason.

Competency and behaviour

• Tell me about a time you worked through disagreement.
• Give an example of a difficult decision.
• Describe a time you had to explain something clearly.
• Tell me about a setback and what you changed.
• Give an example of taking responsibility.

Your seven stories should cover most of these, but choose the story that best answers the wording. Do not use the same favourite example for every question.

Strengths and self-awareness

• What type of task gives you energy?
• What do people rely on you for?
• Which skill are you currently developing?
• What feedback have you acted on?

Avoid turning a strength into a slogan. A brief example makes it believable. For a development area, choose something real and explain what you are doing about it.

Situational questions

• What would you do if two deadlines conflicted?
• How would you handle unclear instructions?
• What would you do if you spotted an error after sending work?
• How would you respond if a teammate disagreed with your recommendation?

Start by identifying what you would need to know. Then explain priorities, communication, boundaries and escalation. The goal is not to guess a secret perfect answer.

Technical or role questions

These depend on the job. Review the skills, tools and responsibilities named in the advert, and revisit projects you have claimed on your CV. If you do not know something, say what you do know and how you would verify the rest. Bluffing is harder to recover from than an honest limit.

Questions worth asking the interviewer

Good questions help you understand the work and show where your interest is focused. They should not be facts you could have found on the first page of the employer’s website.

Consider asking:

• What would a strong first three months look like in this role?
• What kinds of work do graduates usually take ownership of first?
• How is feedback given during the programme?
• Which teams or stakeholders would this role work with most often?
• What tends to distinguish people who learn quickly in this team?

Choose two or three that genuinely matter to you. The interview may answer one of them before you get the chance to ask.

Reasonable adjustments and interview access

If a disability or health condition creates a barrier in the recruitment process, use the employer’s stated route to ask about reasonable adjustments as early as you can. Acas gives UK examples such as an accessible interview location or additional time for a written test, but the appropriate adjustment depends on the person and the process.

You do not need to diagnose your needs in the article or copy someone else’s request. A concise message can identify the interview stage, explain the barrier and ask what information the employer needs to consider the adjustment. Applicants in Ireland should follow the employer’s Irish recruitment and equality guidance or seek appropriate local advice.

Your final 48-hour plan

Forty-eight hours before

• Read the invitation and job description again.
• Confirm format, time, location or video link, names if provided, and any documents required.
• Write a one-page employer brief: role, team, two reasons for applying and two questions to ask.
• Match your seven stories to the most important requirements.

Twenty-four hours before

• Practise five questions out loud, including one motivation and three evidence questions.
• Check that you can explain every major claim on your CV.
• Shorten any answer that takes too long to reach your action.
• Prepare clothes, route or technology without making them the centre of your preparation.

On the day

• Review story labels, not scripts.
• Listen to the complete question.
• Pause briefly if you need to choose an example.
• Ask for clarification when the wording is unclear.
• Finish the answer when the evidence is complete.

If the interview is part of a longer selection day, the assessment-centre overview explains the wider process, while the assessment-centre exercises guide covers group tasks, case studies, presentations and written work.

FAQ

How many examples should I prepare for a graduate interview?

There is no official number that fits every interview. Seven is a practical evidence-bank size: enough variety for common themes while remaining easy to remember. Add or remove stories based on the job description and interview instructions.

Can I use university examples?

Yes. Coursework, group projects, research, societies and presentations can provide useful evidence, especially when your personal contribution and decisions are clear. Mix them with work, volunteering or wider responsibilities where you can.

Does every interview answer need STAR?

No. STAR is useful for questions asking what you did in a real situation. Motivation, strengths, factual and technical questions often need a more direct structure.

What if my example has no impressive result?

Do not invent one. Explain what was delivered, what changed, what feedback you received or what you learned. A credible modest result is stronger than a dramatic claim you cannot defend.

Can I take notes into an interview?

Check the invitation or ask the employer. Even where notes are allowed, use short prompts rather than full scripts so you can stay engaged with the conversation.

How should international graduates explain unfamiliar context?

Give one short sentence explaining the university, organisation or local context, then move to your responsibility and action. Do not spend most of the answer translating the setting. For broader application planning, see the UK and Ireland international graduate guide.

Sources checked

This guide was checked on 18 July 2026 against National Careers Service guidance on interviews and STAR, UCD Careers Network interview guidance, GOV.UK Civil Service Success Profiles and current Acas recruitment guidance.

The sources support structured, specific examples, preparation against role requirements and the availability of reasonable adjustments in UK recruitment. They do not establish one universal graduate-interview format or scoring system. Always prioritise the live job description, invitation and employer instructions.

Build your first seven-story evidence bank

Open a blank document and write the seven story labels: team, problem, communication, responsibility, setback, stakeholder and achievement. Give yourself 20 minutes to add one truthful example under each.

Then choose one live job description and mark which story supports each important requirement. That is the point where interview preparation stops being a question-prediction exercise and becomes evidence you can actually use.

If your interview is still months away, build this into the wider final-year graduate job-search timeline rather than waiting for an invitation.