The 10 Most Common Interview Questions (and How to Answer Them)

Interviews feel unpredictable. They mostly are not. The same handful of questions come up across industries and seniority levels, which means the single highest return hour you can spend is preparing answers to them before you are sitting in the room.

The trap is preparing the wrong way. Memorised answers sound memorised, and interviewers have heard every polished script. What works is knowing what each question is actually asking, having two or three real stories ready, and being able to shape them to whatever comes.

Below are the ten questions you should expect, what sits behind each one, and the difference between a weak answer and a strong one.

First, the tool you will need for half of them

Behavioural questions ask you to describe something you did. The structure that keeps those answers from wandering is STAR: Situation, Task, Action, Result.

• Situation: one or two sentences of context. Where, when, what was going on.
• Task: what you specifically were responsible for.
• Action: what you did. This is the longest part, and it should be I, not we.
• Result: how it ended, with a number if one exists.

Most people over invest in Situation and run out of steam by Result, which is the part the interviewer wanted. Aim for roughly 15% situation, 15% task, 50% action, 20% result.

Before any interview, write out three stories in this shape: a success, a problem you solved, and something that went wrong. Between them they will cover most behavioural questions you get asked.

Everything else that goes into getting ready, the research, the logistics and the questions you ask them, is in the job interview preparation guide.

1. Tell me about yourself

What they are really asking: give me a reason to keep listening, and show me you can be concise.

This is not an invitation to narrate your life. It is a sixty to ninety second positioning statement: what you do now, one relevant proof point, and why this role is the logical next step.

Weak: Well, I grew up in Leeds, studied business because I was not sure what else to do, then fell into recruitment, then moved into operations... Strong: I am an operations analyst, six years in retail supply chain. Most recently I rebuilt our monthly close reporting and took the cycle from nine days to four. I am looking for a role where that reporting work sits closer to commercial decisions, which is what drew me to this one.

End pointed at the job, not trailing off.

2. Why do you want this job?

What they are really asking: have you actually looked at us, or are you applying everywhere?

Name something specific and connect it to what you want to do. Vague enthusiasm reads as no research.

Weak: It seems like a great company with a strong culture and I think I would learn a lot. Strong: You sell into retail and wholesale off one stock pool, which is the hardest version of the forecasting problem I have been working on. I would rather solve that than run clean reports on a simpler business.

3. Why should we hire you?

What they are really asking: summarise your fit, because I am going to repeat it to someone else later.

Two or three strengths matched to the role's actual priorities, each with a quick proof. Be direct. Modesty here reads as uncertainty.

4. What is your greatest strength?

What they are really asking: do you know what you are good at, and can you back it up?

Pick a strength that matters for this role, then prove it with an example rather than an adjective. "I am organised" is worth nothing. "I ran three overlapping projects last year and all three landed on date, because I front load the dependency mapping" is worth something.

5. What is your greatest weakness?

What they are really asking: are you self aware, and are you honest under mild pressure?

Name a real weakness that is not fatal for this job, then say what you actively do about it. The failure modes are the humblebrag ("I care too much"), and the disqualifier (naming the core skill of the job).

Weak: I am a perfectionist, I just care too much about quality. Strong: I under communicate when I am heads down on something. I used to assume no news read as fine. Now I send a short Friday update to anyone depending on my work, whether or not there is anything dramatic to report, and it has removed most of the chasing.

6. Tell me about a challenge you overcame

What they are really asking: how do you behave when things are difficult?

Full STAR. Choose a real difficulty with a real resolution, and be specific about your own actions rather than the team's.

7. Tell me about a time you failed

What they are really asking: can you take responsibility, and did you learn anything?

This one catches people because the instinct is to dodge. Do not pick a fake failure, and do not blame someone else. Pick a genuine one, own your part plainly, and spend most of the answer on what changed afterwards.

Weak: I once took on too much because I wanted to help the team. Strong: I shipped a pricing change without checking it against the legacy contracts, and about forty customers were billed incorrectly for a month. I flagged it the day I found it, worked with finance on the credits, and wrote the pre release checklist we still use. Nothing has gone out unchecked since.

8. Where do you see yourself in five years?

What they are really asking: will you stay long enough to be worth training, and is your ambition compatible with this role?

Nobody expects a precise plan. They want direction and no red flags. Talk about the kind of work you want to be doing and the depth you want to reach, rather than a title ladder or a plan that obviously exits the company.

9. Why are you leaving your current job?

What they are really asking: is there a problem I should know about, and how do you talk about people who are not in the room?

Never criticise your employer, your manager, or your colleagues, however justified. Frame it as moving toward something rather than away from something, and keep it short.

Weak: My manager micromanages everything and the company has no direction. Strong: I have taken the reporting work about as far as it goes in a team of that size. I want to be somewhere the analysis feeds directly into commercial decisions.

If you were made redundant, say so plainly. It is common and carries no stigma when stated without embarrassment.

10. What are your salary expectations?

What they are really asking: are we in the same range, so we do not waste each other's time?

Answer with a researched range rather than a single number, and where possible get them to go first: "what have you budgeted for the role?" is a perfectly normal question. If you must give a figure, give a range whose bottom you would genuinely accept, because that is the number you will be offered.

The five concerns behind the ten questions

Preparing ten answers is a lot of work, and it produces ten separate scripts that fall apart the moment the wording changes. Preparing five is less work and survives rewording, because interviewers are not really asking ten things. They are checking five, and the questions are just the doors they use.

| The real concern | The questions that test it | |---|---| | Can you do the work? | Greatest strength, challenge you overcame, the technical and behavioural questions | | Will you stay? | Where do you see yourself, why are you leaving, why this company | | Is this the job you actually want? | Why do you want this job, why should we hire you | | What are you like to work with? | Tell me about yourself, time you failed, greatest weakness | | What will you cost, and when can you start? | Salary expectations, notice period, availability |

Two things follow from reading it this way.

Most answers should serve more than one concern. A story about a project you rescued can demonstrate competence and, in the last sentence, say something about how you behave when things go wrong. You have a limited number of stories and an unlimited number of possible questions, so each story should be built to face in two directions.

You can hear what is actually being asked. When someone asks "where do you see yourself in five years", the honest translation is usually "am I going to be recruiting for this role again next spring". An answer describing your ambition in the abstract misses it. An answer that connects what you want to something this role plausibly leads to hits it directly.

If you only have an hour to prepare, spend it on the five, not the ten.

The questions people dread, and the honest way through

There is a second set of questions that no amount of general advice prepares you for, because they are about something you would rather not discuss. They are asked more often than the polished ones, and they are where interviews are most commonly lost, usually not because of the fact itself but because of how the person handles being asked.

The pattern that works in all of them: short factual answer, no defence, then move forward. Length signals discomfort. What convinces is the ease with which you say it.

"There is a gap here. What happened?" Name it plainly and say what closed it. "I was out for eight months after my role was cut. I did a data analysis course in that time and took two freelance projects, and I started looking seriously in the spring." That is the whole answer. Do not apologise, and do not present the gap as an unbroken period of self improvement, which nobody believes. The version of this that lives on your CV is a separate problem: how to handle employment gaps on the page covers it.

"You have had three jobs in four years." The worry is that they will be back here in eleven months. Give the reason for each move in one clause, and make the pattern point somewhere. "The first was a fixed term contract, the second I left when the team was restructured, the third I chose to leave because the role narrowed. What I want now is a place I can stay and go deeper." If two of the three moves were genuinely your choice, say so; the honesty costs less than the evasion.

"Why did you leave after eight months?" or "Were you let go?" Answer the question that was asked, factually, and stop. "Yes. The company cut about a fifth of the staff in March and my team went from six to two." Or, if it was performance related and you can say so: "It was not working. The role turned out to be much more X than the description suggested, and neither side wanted to keep going." Never criticise the previous employer at length, not because it is unfair, but because the interviewer cannot verify your account and will file the complaint as a personality trait.

"You seem overqualified for this." This is a real concern, not a compliment, and it deserves a real answer. Say why you want a role at this level, in terms that are true. Wanting less travel, wanting to be closer to the work, wanting to leave management, wanting stability after a period of chaos: all of these are believable. What is not believable is pretending you had not noticed.

"How would you feel reporting to someone younger than you?" or the variants about a smaller team, a smaller budget, a step sideways. The answer is the same shape: acknowledge the difference matter of factly, then give the concrete reason it does not bother you.

One thing to hold on to: you are allowed to decline. "I would rather not go into the details of why I left, but I can tell you it ended cleanly and my former manager is happy to speak to you" is a legitimate answer, once, delivered calmly.

The phone screen asks the same questions with different stakes

Before any of this happens in a room, there is usually a twenty minute call with a recruiter, and people prepare for it as if it were a small interview. It is not a small interview. It is a different exercise with a different goal.

The screener is looking for reasons to stop, not reasons to continue. They have a list and limited time. Disqualifiers get checked first: salary range, notice period, location and work authorisation, the one or two hard requirements from the advert. Depth is not being assessed, so depth is not what to bring.

Answers should be a third of the length you would give a hiring manager. Thirty to sixty seconds. If they want more they will ask, and them asking is a good sign.

Salary will come up, often in the first five minutes. Have a range ready before you pick up the phone, because this is the stage where being unprepared costs you most: an unconsidered number said out loud becomes the anchor for everything that follows. The detail on how to handle it is in the salary expectations question.

Your job on this call is to be easy to advance. The screener has to write a short summary and defend passing you on. Give them the sentence they need: what you do, the scale you do it at, and why this role. If they can copy your own phrasing into their note, you have made their job easy, and easy candidates get advanced.

The question at the end

"Do you have any questions for us?" is not a formality, it is part of the assessment, and "no, I think you covered everything" is a poor answer.

Prepare three or four. The best ones are specific and reveal that you are thinking about doing the job, not getting it:

• What does the first ninety days look like for whoever takes this?
• What is the thing about this role that people underestimate?
• How does this team decide priorities when everything is urgent?
• Why is the role open?

Avoid asking about holiday, hours, or benefits at first interview. Those get settled at offer stage.

What you send a few hours later matters too, and the format is in the thank you email after an interview.

What varies by country

The ten questions travel well. What changes is the order, the formality, and which questions are normal to ask at all.

United States. Behavioural questions dominate, often explicitly signposted ("tell me about a time when"). Several questions that are asked casually elsewhere are unlawful for employers to ask here, including age, marital status, children, religion and national origin, with the details varying by state. If one comes up, you can answer the concern behind it rather than the question itself: "if you are asking about availability for travel, that is not a problem".

United Kingdom. Competency based interviewing is the norm, often against a published framework, and answers are expected to be structured rather than conversational. Salary is usually raised by an agency recruiter before the employer stage, not in the room.

Germany, Austria, Switzerland. Interviews are more structured and more literal. A two to three minute self presentation at the start is expected rather than optional, formal address is the default, and questions about your notice period and earliest start date come early because both sides treat them as real planning constraints. Your account of why you left previous roles should be consistent with your written references, since those documents are actually read here.

Spain and Latin America. Availability and start date come up early. In Spain, expect salary discussed as an annual gross figure and pay attention to whether it is quoted across twelve or fourteen payments, because the monthly reality differs. In much of Latin America the process includes stages that are less common in Europe, such as psychometric testing or a medical check, and part of the first contact often happens over messaging rather than email.

France. The interview tends to be more formal in register, with the polite form used throughout unless the other side breaks it first. Expect a direct question on your salary expectations in gross annual terms, and be ready for the status and contract type to be part of the conversation rather than an afterthought.

Turkey. The self introduction is often the whole opening and tends to run long, which is a mistake: keep it to the work. Salary comes up early and the single most important thing is to state clearly whether you are talking net or gross, since the gap is large and the misunderstanding surfaces late. Questions about military service status are common for men. You may also still be asked about marital status or family plans; this is not lawful ground for a hiring decision, and you can redirect to the underlying concern, but you should decide in advance how you want to respond rather than being caught by it.

Frequently asked questions

How long should an answer be?

Sixty to ninety seconds for most, up to two minutes for a full STAR story. If you are past two minutes without being asked to continue, you have lost the room.

Should I write my answers out word for word?

Write out the stories, not the scripts. Bullet points for each STAR beat. Word for word answers come out flat and collapse the moment the question is phrased differently.

What if I do not know the answer?

Say so and reason out loud about how you would find out. For technical questions especially, watching you think is often more useful to the interviewer than a correct answer would be.

What if I have no relevant experience for a behavioural question?

Use something adjacent: a project, volunteering, a part time job, coursework. Interviewers are looking for the behaviour, not the setting. Saying "nothing comes to mind" is the only wrong answer.

Is it acceptable to take notes into the interview?

Yes, and it usually reads as prepared rather than unsure. Keep it to one page and do not read from it.

Should I ask about salary in the first interview?

Only if they raise it, or if you are late in the process and it still has not come up. Very early, it shifts the conversation before you have built any leverage.

They asked something I think was unlawful. What do I do in the moment?

You have three options and all of them are legitimate: answer it, answer the concern behind it, or decline politely. Redirecting usually keeps the conversation intact: "I am fully available for the schedule in the advert" answers what they actually need to know. Declining is also fine, said evenly. What you should not do is decide in the moment; think about which of the three you want to use before you are sitting there.

I gave a bad answer twenty minutes ago. Can I fix it?

Yes, and doing so scores better than pretending it did not happen. At the end, when they ask if you have anything to add, use one sentence: "Earlier I gave you a weak example for the conflict question, and I would like to give you a better one." Interviewers read that as self awareness, which is one of the things they were measuring anyway.

Should I answer differently if the interviewer is clearly reading from a script?

Match the format rather than fighting it. A scripted interview usually means the answers are being scored against fixed criteria, sometimes by someone who is not the hiring manager, so structured and explicit beats charming. Signpost your answers: say what the situation was, what you did, and what resulted, in that order, so the person scoring can find each part.

What if the same question comes up in three different rounds?

Give the same facts with different depth. Repeating your answer word for word sounds rehearsed; contradicting yourself is worse. Assume everyone in the process compares notes, because they do, and use the extra rounds to add detail rather than to reinvent the story.

How much should I prepare for a job I am not sure I want?

Enough for the phone screen, and no more, until you know. The screen is where you find out the salary, the actual scope and the process length, which is exactly the information you need to decide. Preparing forty minutes of answers before knowing whether the range works is how people waste evenings.

Do these questions change for remote or hybrid roles?

Two get added. Expect something about how you work without supervision, and something about your setup and overlap hours. Both are checking the same underlying concern as the rest: whether hiring you will create work for someone else. Answer with specifics about how you organise and communicate rather than reassurance that you are disciplined.

Before the interview, check the document that got you there

Interviewers ask about what is in front of them, so what your CV emphasises largely determines which questions you get. If it emphasises the wrong things, you will spend the interview defending them. Our guide on tailoring your CV to a job description covers how to fix that, and CvLaunch will show you what an employer's system actually extracted from your file. It takes seconds, it is free, and it needs no sign up.