Common Interview Questions and How to Answer Them
Interviews feel unpredictable, but they are not. Across industries, countries and seniority levels, the same eight or nine questions appear in some form, because interviewers are trying to answer the same four things: can you do the job, will you actually do it, will you fit the team, and why are you available.
That predictability is your advantage. Prepare properly and you walk into most interviews having already thought through 80% of what will be asked, which frees your attention for the parts you cannot predict.
This guide covers the questions that genuinely recur, the structures that make answers land, example answers you can adapt, the questions you should ask back, and the specific handling that international and remote candidates need.
Prepare Five Stories, Not Fifty Answers
The most efficient preparation method is not memorising answers. It is building a small library of real stories that can be adapted to many questions.
Pick five experiences from your working life that you can describe in detail:
- An achievement with a measurable result.
- A problem you solved, ideally one with constraints or pressure.
- A conflict or difficult working relationship you handled.
- A failure or mistake and what changed afterwards.
- Something you learned or taught, showing growth or leadership.
Write each in the STAR structure: the Situation briefly, the Task you were responsible for, the Action you personally took, and the Result with a number where one exists. Then practise telling each in 60 to 90 seconds out loud, because stories that read well often sound rambling when spoken.
Those five stories will answer most behavioural questions in any interview. The details come from the accomplishment log our CV guide recommends keeping, which is exactly why that habit matters.
"Tell me about yourself"
The most common opening question, and the one most often wasted on a life story. The interviewer is asking for a professional summary, not a biography.
Use present, past, future: what you do now, the most relevant thing you have done before, and what you are looking for next, in about 60 to 90 seconds.
"I'm a customer service team lead at a telecom provider, where I manage a team of eight and handle escalated complaints. Before that I spent three years in retail banking, which is where I learned to resolve disputes under pressure. I redesigned our escalation process last year and cut average resolution time from five days to two. I'm now looking for a role where I can take on broader operations responsibility, which is what drew me to this position."
Three rules: keep it professional rather than personal, end on why you are here rather than trailing off, and tailor the middle section to whatever the role most needs.
"Why are you leaving your current job?"
The honesty test. Interviewers are checking for bitterness, blame and instability.
The structure that always works: state what you are moving toward, not what you are escaping, in one or two sentences, then stop.
"I've been in the same scope for three years and I'm ready to own a full process end to end, which this role offers."
If you were laid off: say so plainly. It carries no stigma, especially now. "My role was eliminated in a restructuring that affected about forty people, and it wasn't performance related." Our laid off versus fired guide has the full scripts.
If you were fired: be brief, own it, and show what changed. "The role wasn't the right fit, and we agreed to part ways. What I took from it was X, and I've applied that since by doing Y."
If the real reason is a bad manager or a toxic environment: translate it. "I'm looking for a team with clearer structure and more regular feedback" is true, professional and unanswerable. Criticising a former employer, even accurately, costs you the room every time.
"What is your greatest weakness?"
The question everyone tries to dodge, which is precisely why dodging it is noticed. "I'm a perfectionist" and "I work too hard" are recognised as evasions.
What works: a real, moderate weakness that is not central to the job, plus the specific thing you do about it.
"I used to take on too much myself rather than delegating, because it felt faster. It became a bottleneck when my team grew. I now assign ownership at the start of each project and hold a weekly check-in instead of stepping in, which has worked considerably better."
What to avoid: anything that disqualifies you for the core function (poor attention to detail for an accounting role), anything you have not actually addressed, and false modesty.
"Why do you want to work here?"
A research question. Generic answers are obvious and expensive.
Give two reasons: one about the organisation or the role specifically, and one about fit with your own direction.
"Two reasons. You've just expanded into the SME segment, which is exactly the customer base I spent four years supporting, so I'd be useful quickly. And the role includes process design, which is where I want to grow rather than staying purely in day-to-day delivery."
Preparation required: read the company's own site, recent news, the job description twice, and the profiles of the people interviewing you if you know them. Fifteen minutes is usually enough to sound genuinely informed.
"Why should we hire you?" or "What makes you the right fit?"
The closing argument. Match yourself to their stated needs, briefly, with evidence.
The structure: pick the two or three requirements the posting emphasises most, and give one piece of proof for each.
"You need someone who can handle high volume without losing quality, and someone comfortable training others. I currently handle seventy-plus interactions a day at a ninety-five percent satisfaction rating, and I've trained eight new hires on our systems this year."
Behavioural Questions
These start with "tell me about a time when" and are answered from your five prepared stories.
Common versions: a time you handled conflict, missed a deadline, dealt with a difficult customer, worked under pressure, disagreed with a manager, led without authority, or made a mistake.
Three rules for all of them:
- Use STAR and spend most of the time on Action, since that is what they are assessing. A long Situation and a short Action is the most common error.
- Say "I" rather than "we" when describing what you personally did, while still crediting the team.
- Always finish with the Result, and quantify it if you can. A story without an outcome sounds unfinished.
For the failure question specifically, choose something real but recoverable, take responsibility without excessive self-criticism, and spend the second half on what changed afterwards.
"What are your salary expectations?"
The question that costs the most money when answered badly.
Preferred response, if you can use it: turn it around once, politely. "I'd like to understand the full scope first. Do you have a range budgeted for the role?" Many employers will answer, and in a growing number of places they are legally required to disclose a range, as our pay transparency guide explains.
If pressed: give a researched range rather than a single number, anchored slightly above your target, and say it is based on market data for the role and your experience.
Never volunteer your current salary unprompted, and note that in many jurisdictions employers are prohibited from asking, which our salary history guide covers.
Know your structure before answering, because a quoted figure means different things in different systems, which is the whole subject of our CTC versus in-hand guide. The full negotiation sequence, once an offer exists, is in our negotiation guide.
"Where do you see yourself in five years?"
The commitment question, badly phrased. They want to know whether your ambitions are compatible with this role rather than a precise prediction.
Answer with direction rather than a job title: the kind of responsibility you want to grow into, and how this role contributes.
"I want to be leading a function rather than a team, with real ownership of process and outcomes. The next step for me is broadening from one area into managing across several, which is what this role would start."
Avoid: "running my own business" when applying for a long-term staff role, naming the interviewer's job, or saying you have no idea.
"Do you have any questions for us?"
Never say no. This is assessed, and it is also your last chance to gather information.
Strong questions:
- "What does success look like in the first six months?"
- "What is the biggest challenge facing the team right now?"
- "Why is this role open?" which is genuinely informative.
- "How is performance reviewed, and how often?"
- "How does the team handle disagreement?"
- "What would you want me to prioritise in week one?"
Save for later stages: detailed questions about leave, flexibility and benefits, which belong once interest is mutual rather than in a first screen.
Close deliberately. Ask about next steps and timing, and say clearly that you want the role if you do. Candidates who state interest plainly are remembered.
The Modern Layers You Should Expect
Interviews increasingly run through automated stages before a human appears: chat screening, AI voice calls, recorded video questions and assessments. The content of your answers does not change, but the delivery does, and our AI screening stack guide and one-way video guide cover each format.
Two rules that matter across all of them: speak slightly slower than feels natural, and answer completely rather than waiting for conversational encouragement that will not come.
Also note that using AI tools to feed you answers during a live interview is now widely detected and heavily penalised, as our AI cheating guide explains. Prepare with these tools as much as you like; perform on your own.
For International and Remote Candidates
- Address work authorisation plainly if it is relevant, in one calm sentence, using the wording in our work authorisation guide. Confidence matters more than the status itself.
- Do not apologise for your accent. Speak at a measured pace, pause between points, and if you are genuinely not understood, rephrase rather than repeat.
- Translate local context. Name employer size, sector and scale rather than assuming the interviewer knows the company, which is the same principle our CV conversion guide applies to resumes.
- Expect identity verification in remote processes, which is now routine rather than suspicious, as our identity verification guide explains.
- Prepare one relocation or logistics sentence so questions about timing and location do not catch you flat.
After the Interview
Send a short thank-you message within a day: three or four sentences, thanking them for their time, referring to one specific thing discussed, and restating your interest. It is a small signal, it costs nothing, and a surprising number of candidates skip it.
Then follow up once if the stated timeline passes, politely, and keep interviewing elsewhere until an offer is signed.
Interview Questions FAQ
How should I answer "tell me about yourself"? Present, past, future, in 60 to 90 seconds: what you do now, the most relevant thing you did before, and what you want next. Keep it professional rather than personal.
What is the STAR method? A structure for behavioural answers: Situation, Task, Action, Result. Spend most of your time on the Action, use "I" for what you personally did, and always end with a quantified result where possible.
How do I answer the weakness question? Name a real, moderate weakness that is not central to the job, then describe the specific thing you now do about it. Avoid disguised strengths, which interviewers recognise instantly.
What do I say about why I left my last job? State what you are moving toward in one or two sentences. If you were laid off, say so plainly. If you were dismissed, be brief, own it and show what changed. Never criticise a former employer.
How should I answer salary expectations? Ask for their budgeted range first where you can. If pressed, give a researched range rather than a number, and avoid volunteering your current salary, which employers are prohibited from asking in many places.
How many questions should I ask at the end? Two or three good ones. Focus on success criteria, challenges, why the role is open and how performance is reviewed, and save benefits questions for later stages.
Should I send a thank-you note? Yes, within a day, kept short and specific. It is a cheap, effective signal that many candidates skip.
Can I use AI to help me during the interview? Use it to prepare, never to perform. Live AI assistance is increasingly detected and penalised, and the preparation benefit is where the value was anyway.
Predictable Questions, Prepared Answers, Real Stories
Interviews reward preparation more than charisma, and preparation here is finite: five real stories told in STAR form, a 90-second professional summary, a forward-looking reason for leaving, an honest weakness with a fix attached, a researched salary range, and three questions of your own. That is a couple of hours of work that applies to every interview you will attend this year.
Do it once, practise out loud, and the next interview becomes a conversation about whether the role fits rather than a test you hope to survive.
And make sure the document that opened the door is as prepared as you are: a clean, quantified, professional CV, built free with MyCVCreator.
Related reading:
One-Way Video Interviews: How to Pass Them ·
AI and Automated Interviews: The Screening Stack ·
Laid Off vs Fired: The Differences That Matter ·
How Can I Make a CV for a Job?
