Common Interview Questions and Answers
Employers write their own questions, but they write them from a short list of competencies. That is why the same fifteen or so questions keep appearing in different words.
There is no secret list of interview questions, and any site selling you one is selling you a list somebody wrote down after their own interview. What is predictable is the underlying competency. Graduate employers score against a small framework, usually four to six behaviours, and each question is just a way of asking for evidence of one of them.
That is genuinely good news, because it means preparation is finite. Eight to ten well-chosen stories from your own experience, each with a decision you made and an outcome you can state, will cover almost anything you are asked. The work is in choosing the stories and knowing which competency each one proves, not in memorising answers.
Below are the questions that come up most often in graduate and early-career interviews, grouped by what they are actually testing. For each one, the note says what a reviewer is crediting, which is usually narrower than candidates assume.
What every answer is marked on
Evidence, not opinion
Interviewers score what you say you did, not what you say you are like. "I am a strong communicator" is unscorable. "I rewrote the weekly report so the two teams stopped duplicating work" is evidence, and it earns the same point far more reliably.
Your contribution specifically
Frameworks score individuals, so "we" costs you marks even when the work genuinely was collective. Say what the team did once, then spend the rest of the answer on your own part in it.
A stated outcome
The result is where most answers are thinnest and where the easiest marks are. Numbers help, but so does any concrete change: the process stuck, the client renewed, the bug never recurred, your manager adopted it.
Reflection
Most frameworks include learning or self-awareness somewhere. One honest sentence about what you would do differently often picks up a mark that the rest of the story cannot, and it costs you nothing.
Relevance to this employer
Motivation questions are marked on specificity. A reason that would apply to any of their competitors reads as no research, which is a far more common failure than weak experience.
Length and pace
Two minutes is a good target for a story answer and thirty to sixty seconds for a motivation or preference question. Long answers do not score higher, they just bury the evidence deeper.
Sixteen questions to have an answer ready for
Tell me about yourself.
An opener testing relevance and self-editing. Three beats in ninety seconds: where you are now, the two most relevant things you have done, why this role follows. Not a biography.
Why do you want this role?
Scored on whether your reasons are specific to the work itself. Name the actual tasks the job involves and connect one of them to something you have already done and enjoyed.
Why do you want to work here?
Name something checkable: a project, a market position, how the graduate scheme is structured. Then say why it matters to you. Generic praise of "culture" scores as nothing.
What are your strengths?
Pick one that the role actually needs and prove it with a short example. Two strengths with evidence beat five adjectives every time.
What is your greatest weakness?
Marked on self-awareness and on whether you are doing something about it. Name a real limitation, say the specific step you have taken, and avoid the disguised-strength answer, which interviewers hear several times a day.
Tell me about a time you worked in a team.
Teamwork evidence is your role in making the team work, not the fact that you were in one. Describe what you did when the team was struggling.
Describe a time you led something.
Leadership without a title counts, and for graduates it is usually the better example. Show the decision you made and how you brought people with you.
Tell me about a time you disagreed with a colleague.
The mark is in handling, not winning. State their position fairly, say what you did, and say what was agreed in the end, even when it was their view.
Give an example of when you solved a difficult problem.
Reviewers look for the method: how you diagnosed it, what you ruled out, why you chose the option you did. A solution with no reasoning reads as luck.
Tell me about a time you failed or made a mistake.
Pick something with a real cost and own the decision that caused it. Then give the change you made. Candidates who choose a costless failure are marked down for not answering.
Describe a time you had to juggle competing priorities.
Prioritisation is scored on what you chose not to do and how you communicated that. Say who you told, and when.
Tell me about a time you persuaded someone.
Influence is marked on whether you adapted to your audience. Say what that person cared about and how you framed your case around it.
Give an example of learning something quickly.
For graduate schemes this is often the most important competency in the framework. Show your method for getting up to speed and what you delivered while still learning.
Tell me about a time you handled a difficult customer or stakeholder.
Composure and judgement. Acknowledge the other person, describe what you could and could not offer, and say how it ended.
Where do you see yourself in five years?
Testing whether your plan is compatible with the role, not whether you have a plan. Direction plus flexibility beats a rehearsed job title.
What questions do you have for us?
Have two ready that you could not answer from the website: how the team measures success, what the first six months look like, how the scheme handles rotations. "No questions" is a wasted mark.
How to prepare in five steps
- 1
Find the framework before writing anything
Most employers publish the behaviours or values they hire against, on the careers site or in the invitation email. UK public sector roles use the Civil Service Success Profiles, and large professional services firms publish their values. Prepare against that list rather than a generic one.
- 2
Write eight to ten stories, one paragraph each
Cover teamwork, leadership, conflict, failure, pressure, persuasion, initiative and fast learning. Part-time jobs, societies, coursework and volunteering all count. What matters is that you made a decision and something changed.
- 3
Map stories to competencies, not to questions
Write the competencies down the page and put each story against every one it can serve. Most good stories serve two or three. This is what lets you answer an unexpected wording without freezing.
- 4
Add the number to every story
Go back through and attach one measurable outcome to each. Where no figure exists, write the concrete change instead. Stories without an ending are the reason otherwise good candidates score mid-range.
- 5
Rehearse out loud against the clock
Speak each story to a phone camera and time it. You are checking that it lands in two minutes with the result intact. Answers that read well on paper routinely take three and a half minutes to say.
Mistakes that cost marks
One story used for everything
Reusing the same project for teamwork, leadership and pressure makes a thin body of experience look thinner. Interviewers notice immediately, and it reads as though nothing else has happened to you.
Describing the team instead of yourself
The most common single fault in graduate interviews. If an answer contains no sentence starting with "I decided" or "I did", it has not given the interviewer anything to score.
Motivation answers that fit any employer
Saying you admire their people, culture and reputation is interchangeable with every competitor and is scored accordingly. One specific, checkable fact is worth more than three paragraphs of praise.
Memorising word for word
Scripted answers collapse when the wording shifts, and they sound recited. Learn the beats and the evidence, then let the sentences come out differently each time.
No reflection anywhere
Answers that end at the good outcome leave the learning mark unclaimed. One sentence on what you would change is the cheapest point available in a competency interview.
Treating a strengths question as a competency question
Asked what you enjoy or what comes easily to you, a fully structured STAR answer is the wrong shape and often reads as evasive. Those questions are marked on authenticity and energy instead.
Practise this before the real one
Record five behavioural questions to camera, with a prep window and a sector focus, then get AI feedback on clarity, structure and confidence.
Frequently asked questions
How many stories do I actually need?
Eight to ten well-prepared ones cover a typical graduate process, including the video stage and the assessment centre interview. Beyond that you get diminishing returns and start forgetting the detail, which is what makes an answer sound thin.
Can I use examples from university or part-time work?
Yes, and for most graduate applicants that is where the best evidence lives. A society committee decision, a group project you unblocked or a shift you ran short-staffed all demonstrate the behaviours employers score. Relevance of the behaviour matters, not the prestige of the setting.
What if I am asked something I have no example for?
Say so briefly and offer the nearest real situation, explaining what transfers. Interviewers accept that; inventing an example rarely survives the follow-up questions, which is when the answer actually falls apart.
Should I bring notes to an interview?
A short list of your stories and your questions for them is normally fine in a live interview and shows preparation. Reading full answers is not. In a recorded video interview, keep anchors beside the lens rather than a script.
Are these the questions my employer will ask?
Nobody can tell you that, because employers write their own. These are the questions that recur across graduate and early-career hiring because they map onto the competencies most frameworks contain. Prepare the evidence and the wording stops mattering.
How do I practise answering rather than just writing?
Record yourself. CogniPrep mock interview sessions run five behavioural questions to camera, with sector-specific question pools and AI feedback on clarity, structure and confidence, plus a model answer for your weakest response.