Interview Prep for Graduates

What interviews actually look like in 2026

Forget the image of sitting in a boardroom opposite five unsmiling people. That still happens occasionally, but for most graduate roles in the UK, the process looks quite different now.

Here's the typical flow for a graduate position:

1. Application screening -- your CV and cover letter get reviewed (often by software first, then a human)
2. Phone screen -- a 15 to 20 minute call with a recruiter or HR person, checking the basics
3. Video interview -- either live with a hiring manager or pre-recorded (more on this below)
4. In-person interview or assessment centre -- the final stage, usually at the company's office

Not every company follows this exact order. Smaller organisations might skip the phone screen entirely and invite you straight to a face-to-face chat. Larger graduate schemes -- think Civil Service Fast Stream, NHS Graduate Management Training Scheme, or schemes at companies like Unilever and PwC -- almost always include an assessment centre at the end.

The point is: you'll rarely walk into a formal interview cold. There are usually earlier, lower-stakes conversations first. Each stage is a chance to build confidence for the next one.

The questions you'll definitely get asked

Every interview is different. But certain questions come up so reliably that there's no excuse for being caught off guard. Here's how to handle each one.

"Tell me about yourself"

This feels impossibly broad, which is why so many people ramble through it. The trick is structure. You're not giving your life story. You're giving a 60 to 90 second answer that covers three things:

1. Where you're coming from -- your degree, what you studied, maybe one relevant thing you did at university
2. What's brought you here -- how you got interested in this field or role
3. Why you're excited about this opportunity -- one sentence connecting your background to their company

"I've just finished a Geography degree at Leeds, where I got really interested in data analysis through my dissertation on urban transport patterns. That led me to an internship at a local council where I was building dashboards for public consultation data. I loved the problem-solving side of that work, which is what drew me to this analyst role at your company -- I saw you're doing similar things with retail location data."

That's it. Clean, specific, connected. Around 30 seconds. The interviewer now has three or four threads they can pull on.

"Why this role?" or "Why do you want to work here?"

The generic answer -- "I'm passionate about your company's mission" -- tells them nothing. They've heard it 40 times this week.

What works is specificity. Mention something concrete: a project they've worked on, a product you've used, a news article about them, something an employee said on LinkedIn. Then connect it to something you genuinely care about.

"I read about your work with the Birmingham City Council transport review, and the way you approached the data modelling was exactly the kind of work I want to be doing. I also noticed from your team page that a lot of people here have moved between different departments, which appeals to me because I'm still working out exactly where my strengths are."

This answer works because it proves you've done actual research and you're being honest about where you are in your career.

"Tell me about a time when..." (competency questions)

These are the backbone of UK graduate interviews. We'll cover them in detail in the next section, but the short version: use the STAR method (Situation, Task, Action, Result) as a framework, not a straitjacket.

The biggest mistake people make is spending too long on the Situation and Task. The interviewer wants to hear what you did and what happened because of it. Aim for roughly:

• Situation and Task: 20% of your answer
• Action: 50% of your answer
• Result: 30% of your answer

"What are your weaknesses?"

The "I'm a perfectionist" answer needs to retire. Everyone sees through it.

The best approach is genuine honesty paired with evidence that you're working on it. Pick something real but not catastrophic.

"I sometimes take too long to ask for help when I'm stuck on something. During my dissertation, I spent three days trying to fix a coding error before I finally emailed my supervisor, and she solved it in ten minutes. Since then, I've made a rule for myself: if I've been stuck for more than an hour, I ask someone. It's something I'm still working on, but I'm much better at it than I was."

This works because it's specific, self-aware, and shows growth. That's all they're looking for.

"Do you have any questions for us?"

Always say yes. Always. Having no questions signals that you're not that interested.

Good questions show curiosity about the actual experience of working there:

• "What does a typical first six months look like for someone in this role?"
• "What's the biggest challenge the team is working on right now?"
• "What do you enjoy most about working here?" (people love talking about themselves)
• "How is performance reviewed for graduate hires? What does success look like after the first year?"

Avoid asking about salary, holidays, or working from home at a first interview. Those conversations happen later, usually after an offer.

Competency-based interviews: the format that dominates UK graduate hiring

If you're applying to any medium or large UK employer, you will almost certainly face competency-based questions. The Civil Service, NHS, major banks, law firms, consultancies, and most large graduate schemes all use them.

The logic is simple: instead of asking hypothetical questions ("What would you do if..."), they ask you to describe real situations from your past ("Tell me about a time when..."). The assumption is that past behaviour predicts future behaviour.

Common competency areas for graduate roles:

• Teamwork -- "Describe a time you worked effectively as part of a team"
• Problem-solving -- "Tell me about a difficult problem you solved"
• Leadership -- "Give an example of when you took the lead on something"
• Communication -- "Describe a situation where you had to explain something complex to someone"
• Resilience -- "Tell me about a time things didn't go to plan and how you handled it"
• Organisation -- "How have you managed competing priorities?"

Before the interview, prepare two or three solid examples that you can adapt across different questions. University projects, part-time jobs, volunteering, sports clubs, society committee roles -- all count. The example doesn't need to be impressive. What matters is how you tell it.

A part-time job at Tesco where you dealt with a difficult customer complaint is a perfectly good example for communication, resilience, and problem-solving. You don't need to have led a charity expedition to Borneo.

Video interviews: what you need to know

Video interviews are now standard for first or second-stage screening. Some are live (you're talking to a real person over Teams or Zoom), and some are pre-recorded (you see a question on screen, get 30 seconds to prepare, then record yourself answering).

Pre-recorded interviews feel strange. Talking to a screen with no human reaction is genuinely weird, and it's okay to acknowledge that to yourself. But companies use them because they're efficient -- and you can prepare for them.

Technical setup

• Test everything the day before. Camera, microphone, internet connection, the specific platform they're using. Don't discover that your laptop needs a 45-minute update at 9:55am.
• Lighting matters more than you think. Face a window if you can. Avoid sitting with a window behind you -- it turns you into a silhouette. A simple desk lamp pointing at your face from a 45-degree angle works well.
• Look at the camera, not the screen. This is the single hardest habit to build. When you look at the person's face on your screen, you appear to be looking slightly downward. Looking directly at the camera lens creates the impression of eye contact. Stick a small note next to your camera as a reminder.
• Background. A plain wall is fine. A tidy bookshelf is fine. Your unmade bed is not. If you can't control your environment, most platforms offer virtual backgrounds -- use a simple, neutral one.
• Wear proper clothes. Yes, the full outfit. Not just the top half. You will, at some point, need to stand up unexpectedly.

Delivery on camera

Speak slightly slower than feels natural. Video compression and slight audio delays mean that your normal speaking pace can sound rushed. Pause between points. It feels awkward in the moment but looks confident on playback.

If it's a pre-recorded interview, you usually get one or two practice questions first. Use them. Get comfortable hearing your own voice played back. Almost everyone hates it initially -- that's normal.

Assessment centres: what they're actually testing

Assessment centres can last half a day or a full day. They typically include a mix of group exercises, individual presentations, case studies, and one-to-one interviews. They're more common for structured graduate schemes than for individual job roles.

Here's what's actually being evaluated at each stage:

Group exercises

You'll be given a scenario with a small group of other candidates and asked to discuss it, reach a decision, or solve a problem together. The assessors are not looking for the loudest person. They're watching for:

• Do you listen to others before jumping in?
• Do you build on other people's ideas rather than just pushing your own?
• Can you disagree constructively?
• Do you involve quieter members of the group?

The person who says "That's a good point, and building on that..." tends to score better than the person who dominates the conversation. The candidate who notices someone hasn't spoken and asks for their view demonstrates exactly the kind of awareness employers value.

Presentations

You'll usually get a brief or a case study and 20 to 30 minutes to prepare a 5 to 10 minute presentation. Sometimes you'll present to a panel, sometimes to other candidates.

They're testing your ability to structure an argument under time pressure and communicate clearly. Don't try to cover everything. Pick two or three key points and make them well. If there's data involved, show you can interpret it rather than just reading numbers off a chart.

Case studies

Often used by consultancies and financial services firms. You'll get a business scenario -- maybe a company losing market share, or a charity deciding where to allocate funding -- and need to analyse it and recommend a course of action.

They're not expecting a perfect answer. They want to see your thinking process. Talk through your reasoning out loud. Ask clarifying questions. Structure your analysis rather than jumping to conclusions.

How to research the company properly

Reading the "About Us" page is the bare minimum. It's not research. Here's what thorough preparation actually looks like:

• Glassdoor reviews -- read what current and former employees say about the culture, the interview process, and the work itself. Take individual reviews with a pinch of salt, but patterns are revealing.
• Annual reports and financial statements -- for larger companies, these are publicly available. You don't need to analyse them in depth, but knowing whether the company is growing, shrinking, or expanding into new areas gives you context that most candidates won't have.
• Recent news -- Google the company name and look at the past three months. Have they launched something new? Won an award? Been in the news for any reason? This gives you natural conversation material.
• LinkedIn -- look at the profiles of people in the team you'd be joining. What's their background? Have they posted anything recently? This gives you a sense of the team culture and potential conversation starters.
• The job description itself -- sounds obvious, but read it three times. Highlight the key skills and responsibilities. Your examples and answers should map directly to what they've asked for.

Spending 45 minutes on proper research before an interview gives you a noticeable edge. You'll answer questions with more specificity, ask better questions, and come across as someone who genuinely wants this particular role -- not just any role.

Managing nerves: practical techniques that actually work

Telling a nervous person to "just be confident" is about as useful as telling a hungry person to "just eat." Here are things that actually help.

Before the interview

• Prepare, then stop preparing. Do your research and practice your key answers the day before. On the morning of the interview, do something unrelated. Over-preparing on the day makes most people more anxious, not less.
• The physiological sigh. This is backed by Stanford neuroscience research. Breathe in through your nose in two short inhales (the second one topping up your lungs), then one long exhale through your mouth. Do this two or three times. It activates your parasympathetic nervous system and genuinely calms you down within about 30 seconds.
• Eat something. Your brain needs glucose to function. Low blood sugar makes anxiety worse and thinking harder. A banana or a piece of toast an hour before the interview makes a genuine difference.
• Arrive with a buffer. Rushing to an interview floods your system with stress hormones that take 20 minutes to clear. Give yourself more travel time than you think you need.

During the interview

• It's a conversation, not a performance. The interviewer wants you to do well. They have a vacancy to fill. They're hoping you're the right person. You're on the same side.
• Slow down. When you're nervous, you speed up. Consciously speak at about 75% of your natural pace. Pausing before answering a question doesn't make you look slow -- it makes you look thoughtful.
• If your mind goes blank, say so. "Sorry, let me take a second to think about that" is a perfectly acceptable thing to say. Interviewers are human. They understand.
• Focus on the other person. Nerves are self-focused ("What do they think of me? Am I doing well?"). Redirecting your attention to the interviewer -- really listening to what they're saying, being curious about them -- takes you out of your own head.

What to wear

The dress code for graduate interviews is less formal than it was ten years ago, but it still matters. Here's a rough guide by sector:

• Finance, law, consulting -- formal business wear. A suit or equivalent. You won't be overdressed.
• Public sector (Civil Service, NHS, local government) -- smart but not necessarily a full suit. Smart trousers, a shirt or blouse, sensible shoes.
• Tech, creative, startups -- smart-casual. Clean jeans are often fine. A nice top. No trainers unless you're very confident about the culture.
• Retail, hospitality -- smart-casual, leaning slightly smart. Show you've made an effort.

The underlying principle is simple: dress as though you already work there, but on a day when something slightly important is happening. If you're genuinely unsure, ask the recruiter or HR contact. They'd rather you ask than show up feeling uncomfortable.

Following up after the interview

Send a short thank-you email within 24 hours. Not a long one. Three or four sentences:

1. Thank them for their time
2. Mention one specific thing from the conversation that you found interesting or that reinforced your interest in the role
3. Reiterate that you're keen

That's it. Don't overthink it. Most candidates don't bother, which means doing it puts you in the minority and keeps you fresh in their mind.

If they said they'd get back to you by a certain date and that date passes, wait one more working day, then send a polite follow-up. Something like: "Just checking in -- I'm still very interested in the role and wondered if there was any update on the timeline." Keep it short and pressure-free.

What to do if you don't get it

It stings. There's no way around that. But here's what to remember: graduate hiring is competitive. Some of the big schemes get 100 to 200 applications per place. Not getting the job doesn't mean you weren't good enough. It might mean someone else was a slightly better fit, or the internal candidate they already had in mind came through, or a dozen other things outside your control.

What you can control is what you do next:

• Ask for feedback. Not every employer gives it, but many do, especially for later-stage interviews. Send a brief, gracious email: "Thank you for letting me know. I'd really appreciate any feedback you could share -- it would help me with future applications." When you get feedback, write it down and actually use it.
• Reflect honestly. What went well? What felt shaky? Did you prepare enough? Were there questions that caught you off guard? Each interview teaches you something if you let it.
• Keep going. The average UK graduate applies to around 7 to 10 roles before getting an offer. Some apply to more. It's a numbers game, but it's also a skills game -- and you get better at interviewing with every one you do.

Your first interview will probably be your worst. That's fine. That's how it works for everyone.