Photo by Luis Villasmil on Unsplash

Killer interview questions: how to answer the ones that actually decide it

By the jobsRmine careers desk. Written by a former hiring manager who has interviewed candidates for roles across financial services, tech and the public sector, and edited by the jobsRmine editorial team.

Introduction

You can polish a CV for weeks. You can read every guide. You can reformat the bullet points until they sit perfectly on one page. You can still lose the job in the interview.

The CIPD’s annual Resourcing and Talent Planning research has tracked this for years: UK employers consistently report that the structured interview is the single most influential stage of selection for most roles. Your application gets you in the room. What you say once you’re in there decides the rest.

The questions that do most of that deciding are the ones designed to make you stumble. “Tell me about a mistake you made.” “Why should we choose you?” “What would you change about us?” Hiring managers ask them on purpose, because the answer reveals something a CV can’t.

This is a working guide to the questions that come up most often in UK interviews, why interviewers ask them, and how to answer them in your own voice.

What counts as a killer interview question

A killer question is one designed to pressure-test you.

There are three families. Behavioural questions ask you to describe something you’ve actually done (“Tell me about a time you missed a deadline”). Situational questions ask what you’d do in a hypothetical (“How would you handle a client refusing to pay?”). Competency-based questions probe a named skill on the job spec (“Give me an example of when you influenced someone more senior”).

The research backs structured questioning. Decades of industrial-psychology meta-analyses, regularly cited by the CIPD, place structured interviews among the more predictive selection methods, well ahead of unstructured chats. Which is why most British employers, from the Civil Service Fast Stream to the Big Four, lean heavily on them.

If a question makes you pause, it’s probably doing its job. The interviewer wants to see how you think under a small amount of stress.

Why performance is what gets scored in the room

By the time you’re on a video call with a hiring manager at a Manchester insurance firm or sitting in a meeting room off Old Street, your skills are already taken as read.

Your CV cleared the screen. The recruiter signed off. Maybe a take-home task or a HireVue clip got you here, too. The qualifications question has already been answered.

What happens next is performance. According to LinkedIn’s Global Talent Trends reporting in recent years, UK hiring managers say “soft” capabilities (communication, judgement, how someone handles ambiguity) are now what most often tips a hiring decision between two technically equal candidates. The interview is where those are read.

I’ve sat on hiring panels where two candidates with near-identical CVs gave wildly different interviews. The one who got the offer told a clear story, owned a mistake without flinching, and asked a question at the end that made the room think.

That is what’s being scored in the room.

The seven killer questions and how to answer each

These are the seven that tend to come up most across the UK market, in roughly the order interviewers like to use them. Each one is here for a reason. Knowing the reason is half the answer.

1. What sets you apart from the other candidates?

The trap is sounding either arrogant or generic. The fix is evidence.

Pick the three requirements at the top of the job spec. Tie each to a specific thing you’ve done. Numbers, names, outcomes.

Picture a finance analyst going for a role at a London-based fintech. The job asks for SQL, stakeholder management and forecasting accuracy. A weak answer is “I’m hard-working and a team player.” A strong one is: “Three things. I rebuilt our weekly revenue dashboard in SQL and cut the reporting cycle from 2 days to 4 hours. I’m the named finance contact for three of our product squads, so I’m used to translating numbers for non-finance teams. And on last year’s forecasts, I came in within 2% of actuals across four quarters.”

Specific beats superlative every time.

2. What can you bring to the company that will benefit us?

This is the same question rotated 90 degrees. The interviewer wants to hear that you’ve understood what they’re actually hiring for.

Read the job spec line by line and find the underlying problem. A “growth marketer” listing is usually a “we’re not acquiring users fast enough” problem in disguise. A “senior software engineer with platform experience” listing is often a “our infrastructure is fragile, and we can’t ship quickly” problem.

Name the problem in your answer, then connect it to something you’ve done.

A graduate going for a marketing executive role at a Bristol B2B firm might say: “From the job spec and your last two LinkedIn posts, it looks like you’re trying to turn organic content into a proper inbound channel. In my final-year placement, I helped a CRM vendor double their newsletter sign-ups in 4 months by rewriting their landing pages. That’s the muscle I’d want to bring.”

3. How would you describe our company to a journalist?

Sometimes asked as “What do you know about us?” The polite version of the same thing.

This one separates candidates who applied to 40 places this week from candidates who applied to 4. Spend 20 minutes before the interview reading the careers page, the last 6 months of company blog posts, recent press, and (if it’s listed) the most recent annual report. For private companies, read the Crunchbase or Companies House summary and any founder interview you can find.

Then summarise the company in your own words. What it does, who it sells to, what it cares about. End with something genuinely interesting you noticed.

If you’re interviewing at a UK climate-tech start-up, that might be: “You’re a heat-pump installer trying to industrialise what’s traditionally been a fragmented trade. The thing I found striking was your engineering blog post on cutting installation time from 2 days to one. That’s the kind of operational detail I find interesting, and it’s why I applied.”

You’re showing you’ve read the About page and thought about it.

4. What would you change about the company, and why?

A genuine trap. Be too critical, and you sound presumptuous. Be too flattering, and you sound hollow.

The way through is to anchor your answer in something real and constructive. Pick something small you’ve genuinely noticed (a product detail, a piece of content, a customer-facing process) and offer one thoughtful observation, framed as a question rather than a verdict.

A mid-career engineer interviewing at a UK retail-tech firm might say: “I had a play with your demo last week. The onboarding was smooth, but I noticed the documentation jumps from a ‘getting started’ tutorial straight to the API reference, with nothing in the middle for someone scaling up. If I joined, that’s the kind of gap I’d want to look at. Happy to be told I’ve misread it.”

Curiosity reads well in interviews. Verdicts don’t.

5. What’s your understanding of the job description? Where will you excel and where will you struggle?

Two answers folded into one. Take them in order.

For the first half, paraphrase the job spec back to the interviewer in plain language. Skip the bullet points. Describe the underlying job.

For the second half, name a real strength tied to a real example, and a real gap tied to a real plan.

A mid-career engineer switching from automotive into renewables might say: “Reading the spec, the job is essentially to own the thermal modelling for your next battery system, work closely with the cell suppliers, and prepare us for the relevant safety standards. Modelling and supplier work I’ve done for 8 years at Jaguar. Where I’d be learning is the regulatory side; I’ve started the IEC training, and I’d want to pair with whoever owns compliance today for the first 3 months.”

That answer is honest and competent. Which is the combination interviewers actually want?

6. What are your salary expectations?

Awkward and inescapable. Two things make it less so. The first is research. The second is a calm sentence.

Before the interview, triangulate. Look at the role on Indeed and Glassdoor. Check the Hays UK salary guide or the Robert Half guide for your sector and seniority. Ask anyone in your network in a similar role. You’re looking for the going rate, plus or minus 10%.

When the question comes, give a range that sits inside that band, then say what the range is based on. Something like: “Based on the Hays salary guide for senior product roles in London and the conversations I’ve had with peers, I’d expect £85,000 to £95,000 base. I’m flexible inside that range depending on the total package, and I care about the equity and progression side as much as the headline number.”

You sound informed. You leave room to negotiate. You haven’t priced yourself out.

7. Tell me about a significant mistake you’ve made

The interviewer is not waiting to hear that you have no flaws. They’re waiting to hear how you handle it when something goes wrong, because every job involves things going wrong.

A good answer has four parts. What happened. What did you do when you noticed? How you put it right. What changed in your approach afterwards?

A management consultant might say: “Two years ago, I sent a client deck to the wrong recipient. Different industry, but a similar firm. I rang my partner within an hour, then called the client. We were transparent, sent a recall, and reviewed our distribution process across the team. Since then, we’ve used a two-person sign-off on anything going to a top-20 client. I’d rather over-engineer that step than ever repeat it.”

Notice what that answer does. It owns the error, names the recovery steps, and ends with the system change. Ownership, action, learning.

How to answer ‘tell me about yourself’

Most candidates over-prepare for this question and still get it wrong. They tell the interviewer their life story from sixth form onwards.

You have 90 seconds. Use them in three parts. Where you are now (one sentence). The two or three steps that got you here and are relevant to this role (a short paragraph). Why this job, right now (one sentence).

You’re sketching a line through your career, with this job at the end of it.

If you’re a primary school teacher applying to move into edtech product roles, that might sound like: “I’ve spent the last 5 years teaching Year 4 and Year 5 in two state schools in Leeds, latterly leading our maths curriculum. Before that, I studied education at York. I’m sitting here because I’ve seen first-hand how thin the design of most school software is, and the role you’re hiring for is exactly the bridge between the classroom and product that I want to work on.”

That’s a tell-me-about-yourself answer that actually answers the question.

How to answer ‘what is your greatest weakness?’

The advice you’ve heard a hundred times (“say you’re a perfectionist”) doesn’t fool anyone. Hiring managers in the UK have heard it since the 1990s.

A better answer names a real, mid-sized weakness and shows you’ve done something concrete about it. Real, because hollow answers undermine you. Mid-sized, because admitting something disqualifying (you struggle to meet deadlines, you find feedback hard) is a different kind of mistake.

Pick something tactical. Public speaking. Delegating. Saying no to scope creep. Estimating your own workload. Then describe the tool, course or habit you’ve taken on to work on it.

A project manager might say: “Estimating. I’m consistently optimistic about timelines, especially on cross-team projects. After missing a delivery date 18 months ago, I started buffering all my plans by 20% and running a pre-mortem with the team before committing. The last 4 projects came in on time.”

You’ve shown self-awareness, ownership and a result. That’s the greatest weakness interview answer that lands.

Competency-based questions and the STAR method

UK employers love competency-based questions. The Civil Service, the NHS, most of the big consultancies, and almost every graduate scheme run them as their core format.

You’ll hear three or four classics:

• “Tell me about a time you had to negotiate change in your organisation.”
• “Tell me about a time you led a team that wasn’t motivated.”
• “Tell me about a time something went wrong on a project you were leading.”

The format that works is the one most UK careers services teach: STAR. Situation. Task. Action. Result.

Situation: the context, in one or two sentences. Task: what you were responsible for. Action: what you specifically did (use “I”, not “we”). Result: what happened, with numbers wherever possible.

Where most candidates fall is the Action step. They tell you what the team did. The interviewer is scoring you, not the team. Use “I” deliberately and often, even if it feels uncomfortable at first.

Prepare 4 to 6 STAR stories before any competency interview. Different stories, covering different competencies (leadership, conflict, failure, influencing up, delivering under pressure). You’ll be surprised how many questions you can answer by reshaping one of those stories. The Civil Service Success Profiles framework is openly published and worth practising against, even for private-sector roles.

What makes a good interview answer

Three things, mostly.

A clear shape. Beginning, middle, end. The interviewer can take notes on it.

Specifics. Numbers, names, dates, places. “I improved retention by 12% over 6 months by rewriting our onboarding emails” beats “I worked on retention”.

A point of view. The candidates who win offers don’t just describe what happened. They tell you what they took from it, or what they’d do differently now. That’s the bit that signals seniority.

Memorised speeches don’t land. UK interviewers, especially in structured settings, are listening for whether you can think on the spot. Over-rehearsing strips the life out of your answer. Prepare the bones. Improve the muscle.

What an interviewer’s silence is telling you

When you finish answering, and the interviewer says nothing, the temptation is to keep talking.

Don’t.

Silence in interviews is often a deliberate tool. The interviewer wants to see whether you’ll panic, ramble, or contradict yourself. Some panels use it on purpose to test composure, especially for client-facing roles in law, sales and consulting.

If the silence stretches past 4 or 5 seconds, take a small sip of water and wait. If the interviewer is genuinely thinking, they’ll come back to you. If they’re testing you, they’ll move on quickly once they see you’re not rattled.

You can use silence yourself too. Before answering a hard question, take a beat. A second of considered thought lands better than a panicked first sentence. The good candidates I’ve interviewed all do this without realising.

Conclusion

Killer interview questions feel killer because the stakes are high. The questions themselves rarely are. Most are variations on three things: prove your experience, show your self-awareness, and tell me how you think.

Prepare specific stories. Research the company seriously. Practise answering out loud, ideally with someone who’ll push back. And when you’re in the room, slow down. The candidates who get the offer are the ones who answered the question that was actually asked.

You’ve already done the hard part by being invited. The rest is rehearable.

Frequently asked questions

How long should my interview answers be?

Aim for 60 to 90 seconds for most questions, and up to 2 minutes for behavioural questions using the STAR method. If you can answer in 30 seconds, you probably haven’t given enough detail. If you’ve gone past 2 minutes, you’re rambling. A useful test: if you can’t summarise your answer in one sentence at the end, it was too long.

What’s the best way to prepare for a competency-based interview in the UK?

Build a library of 4 to 6 STAR stories before the interview, each focused on a different competency: leadership, conflict, failure, influencing without authority, delivery under pressure, and learning something new fast. Read the job spec and map each named competency to one of your stories. The Civil Service publishes its Success Profiles framework openly online, and it’s a useful structure to practise against, even for private-sector roles.

Should I send a thank-you email after an interview?

Yes, within 24 hours, and keep it short. Two or three sentences thanking the interviewer for their time, referencing one specific thing from the conversation, and reiterating your interest. UK culture is less aggressive about post-interview emails than the US, so the message should sound considered rather than promotional. Don’t repeat your pitch.

What questions should I ask at the end of an interview?

Prepare 3 to 5, and ask 2. Good ones are specific to the company and the role: how the team is structured, what the first 90 days would look like, how performance is measured, and what the interviewer finds genuinely difficult about working there. Avoid anything you could have found on the website.

How do I answer questions about a gap on my CV?

Honestly and briefly. Name the reason (caring responsibilities, redundancy, illness, study, parenting, a career break), say what you did during it that’s relevant (a course, freelance work, volunteering), and pivot back to why you’re a strong fit for the role. UK employers are markedly more comfortable with career gaps than they were 10 years ago, and trying to hide one tends to backfire. The CIPD’s recent work on returner programmes is a good signal of how mainstream this conversation has become.