Interviews

Common Interview Questions and How to Approach Them

Interview questions look endless, but most of them are trying to find out one of five things. This guide groups common questions by purpose, shows a simple way to build an answer, and includes model answers from fictional candidates. They are there to show structure, not to be copied.

Key points

  • Work out what a question is trying to find out before you answer it; the same example can then serve several questions.
  • Answer the question in your first sentence, give one specific piece of evidence, and tie it back to the job.
  • Keep most answers to between one and two minutes and let the interviewer ask for more.
  • For a weakness, name a real one that is not central to the job and say what you do about it.
  • Prepare facts and examples, not word-for-word scripts, so that your answer survives a differently phrased question.

Most interview questions are versions of a few underlying ones. Can you do the work? Do you want this particular job? How do you behave with other people and under pressure? How well do you know yourself? Do the practical terms suit both sides? If you can tell which of these a question belongs to, you can answer one you have never heard before.

The model answers below show how an answer is put together. They belong to fictional people in different jobs; yours has to be built from your own facts.

Group questions by what they are trying to find out

What the interviewer wants to learnTypical questionsWhat a useful answer contains
Whether you can do the job"Tell me about yourself." "Talk me through your experience of payroll." "What are your strengths?"Recent, relevant experience and one specific result
Why you want this job"Why do you want to work here?" "Why are you leaving your current role?"A reason tied to the work itself and something true about the employer
How you act with others and under pressure"Tell me about a time you disagreed with a colleague." "Describe a mistake you made."One real event: what happened, what you did, how it ended
How well you know yourself"What is your biggest weakness?" "What would your manager say about you?"A real limitation and what you do about it
Whether the practical terms fit"What are your salary expectations?" "When could you start?"A clear, researched answer given without apology

Build an answer in three steps

  1. Answer the question in the first sentence. If you are asked whether you have managed a budget, begin with "Yes, for two years" or "Not formally, but".
  2. Give one piece of evidence: something that happened, with enough detail that the interviewer could ask about it.
  3. Connect it to the job you are applying for, in one sentence.

Between one and two minutes is long enough for most answers. If the interviewer wants more, they will ask.

"Tell me about yourself"

This is a request for a short professional account, not a life story. A dependable order is: what you do now, what came before that matters, one thing you have achieved, and why you are here.

Model answer: Thandiwe Mokoena, applying for a payroll administrator post

I'm a payroll administrator with four years' experience. I'm currently at Stonemere Care Group, where I run the monthly payroll for about 600 staff across nine care homes. Before that I spent two years in accounts payable, which taught me to reconcile carefully and to chase missing information without annoying people. Over the last year I've taken on the pension contribution checks, and I cut our month-end corrections from around thirty to fewer than ten by giving the home managers a cut-off checklist. I'm looking for a role with more complicated pay arrangements, and your advert mentions shift allowances and weekly as well as monthly pay runs. That's the work I'd like to do more of.

It takes under a minute, includes one checkable result and ends on the job being discussed. School, hobbies and unrelated jobs are left out.

"Why do you want this job?"

There are two halves to this: what attracts you to the work, and what attracts you to this employer. An answer about what you hope to get is weaker than one that shows you understand the job and have a reason for doing it here.

Weaker

I have always admired your company, and I think this would be a great opportunity for me to grow and develop my career.

Stronger

I have done first-line IT support for three years, and the part I enjoy most is working out why a fault keeps coming back. This post is second-line, so that would be most of the job. I also saw that your clients are schools and clinics, and I would like my work to keep those running.

Why: The strong answer names the actual work, gives a reason from the candidate's own experience and shows that they have read about the employer. The weak one could be said to any company about any job.

Strengths and weaknesses

For a strength, choose one the job needs and prove it with an example: "I am organised" means little until you describe the system you set up. For a weakness, choose something true that is not a core requirement of the role, and say what you do about it.

Model answer on a weakness: Kenji Watanabe, applying for a site engineer post

I tend to hold on to tasks I should hand over. On my last project I was checking every setting-out drawing myself, and by the third month I was the reason the concrete pours were waiting. My manager pointed it out. Since then I agree at the start of each week which checks the assistant engineer owns, and I spot-check one in five. It still doesn't come naturally, so I put the handover in the Monday meeting notes to make myself do it.

It is a real limitation with a real cost, and the remedy is concrete. Admitting that it still takes effort makes the answer more believable, not less.

Questions about things you have done

"Tell me about a time when..." asks for one real event. The risk is a vague, general answer ("I always try to stay calm"). Pick a single occasion and tell it in order: the situation, what you did, how it ended. The STAR method explains that order in detail, and the guide to behavioural interviews shows how to collect a set of stories in advance.

Model answer on a difficult conversation: Priya Raman, applying for a staff nurse post

On a night shift last winter, the daughter of a patient on my ward was angry that her father had waited two hours for pain relief. She was right that it was too long: the doctor had been called to an emergency. I took her to the quiet room, told her plainly what had happened, and said what I could do, which was to get the on-call registrar to review him within twenty minutes. She was still upset about the wait, but she thanked me for telling her the truth, and I raised the delay at handover so the day team could follow it up.

One event, her own actions, and an ending that does not pretend everything was put right.

Pay, notice and other practical questions

Practical questions deserve practical answers. For salary expectations, find out what similar roles pay in your area before the interview and give a range with your reasoning, for example: "From the roles I have seen advertised and my four years' experience, I am looking for something in the high thirties, depending on the whole package." The guide to salary negotiation covers what to do once an offer arrives.

For your notice period, check your contract and give the real figure. For a gap in your work history, give a short, true explanation and move on to what you can do now; the guide on employment gaps has wording you can adapt.

When a question surprises you

No list covers every question. When one catches you out, take a breath and, if you need to, say "Let me think about that for a moment". Ask yourself which of the five groups it belongs to, then answer that.

If you have no direct experience, say so and offer the nearest thing: "I have not managed a budget myself, but I prepared the monthly figures for the person who did." An honest near-match is more useful to the interviewer than a confident answer to a different question. Research, practice and logistics are covered in how to prepare for a job interview.

Common mistakes

  • Learning model answers by heart, which makes you sound rehearsed and leaves you stuck when the wording of the question changes.
  • Answering "Tell me about yourself" with a full career history from school onwards, when a one-minute account of your recent, relevant work is what was asked for.
  • Giving a strength with no example, so the interviewer has only your word for it; attach one specific event to every claim.
  • Offering a fake weakness such as perfectionism, when a real, manageable one with a remedy is more credible.
  • Criticising a current or former employer when explaining why you are leaving, which shifts attention from your reasons to your attitude.
  • Talking for four or five minutes without a pause; stop after your point and let the interviewer steer.

Questions and answers

How long should an interview answer be?

Between one and two minutes suits most questions, and under a minute is fine for factual ones such as your notice period. Questions about a past event can run a little longer. If you are unsure whether you have said enough, ask "Would you like more detail on any part of that?".

Should I memorise my answers?

No. Memorise the facts: the dates, the figures, what you did and what happened. Then practise telling them aloud in slightly different words each time, so the answer holds up however the question is put.

What should I say if I do not know the answer?

Say so, then give what you can: the closest experience you have, or how you would go about finding out. Guessing at a technical fact is risky, because a follow-up question will usually expose it.

How should I answer a question about where I see myself in five years?

The question is usually about whether the job fits your direction and whether you are likely to stay. Describe the kind of work and responsibility you want to grow into, and connect it to what this role would teach you. You do not need a job title or a date.