Lists of “100 interview questions and answers” are close to useless, because memorising a hundred answers is impossible and the specific wording of a question rarely matters. What matters is recognising which of about eight underlying concerns a question belongs to, and having the material ready to address that concern.
This guide covers the questions that genuinely recur, grouped by what the interviewer is actually checking, with sample answers that show the reasoning rather than a script to memorise.
The eight things every interview is testing
- Can you do the work? — competence
- Will you stay? — motivation and fit
- How do you behave under pressure? — temperament
- Can you work with people? — collaboration
- Do you know what you are bad at? — self-awareness
- Why are you leaving? — risk
- What will you cost? — money
- Have you thought about this seriously? — engagement
Motivation: why here, why now
“Why do you want to work here?”
The failure mode is praise. “You’re a market leader with a great reputation and I’d love to be part of your journey” says nothing that could not be said to any competitor, and interviewers hear it constantly.
A good answer connects something specific about the company to something specific about you. Three reliable sources: the work itself, the stage the company is at, or a genuine encounter with the product or the people.
“Two things. The role is operations at a scale I have not worked at — about four times the team I run now — and the posting describes the capacity problem in a way that tells me it is a real one rather than a wish list. Second, you manufacture rather than just distribute, and the production constraint is the part of this I do not know. I would rather take a job where a third of it is unfamiliar than one where none of it is.”
“Why are you leaving your current job?”
Answer forwards, not backwards. The interviewer is assessing risk — whether you leave jobs easily, whether there is a problem you are not disclosing, whether the same thing will happen here.
Never criticise your current employer, even when the criticism is deserved and even when the interviewer invites it. It rarely lands as candour; it lands as a preview of how you will talk about them.
My manager micromanages everything and the company has no interest in developing anyone. It has become impossible to get anything done.
I have taken the operations role about as far as it goes at our size — the next step there does not exist. I want to run something bigger with a production element, and that means moving.
If you were made redundant, say so plainly: “The team was restructured in March and my role went with it.” It is common, it carries no stigma, and a straightforward account closes the question.
“Where do you see yourself in five years?”
They are not testing your ambition. They are checking whether your plausible next step exists inside their organisation, because if it obviously does not, you are a flight risk.
“Honestly, five years is further than I plan. What I want in two or three is to be running a larger operation with responsibility for the supplier side as well as scheduling — which from the outside looks like the shape of the role above this one. Beyond that I would rather see what the work turns out to be.”
Self-awareness
“What is your greatest weakness?”
The disguised strength — “I’m a perfectionist,” “I care too much” — fails, and it fails specifically because it answers a different question than the one asked. What is being tested is whether you can identify a genuine limitation and whether you do anything about it.
Pick something real, not disqualifying for this role, with a concrete mitigation.
“I am slow to delegate work I used to do myself. When I moved from doing the scheduling to managing it, I kept picking up the difficult days rather than letting the team learn them, and it was a bottleneck for about six months. What fixed it was making myself unavailable on purpose — I blocked out Tuesday and Thursday mornings for supplier work and made the team route around me. It is still the thing I have to watch when something goes wrong.”
Note that it ends with the limitation still existing. That is more credible than a weakness that has been fully resolved.
“What is your greatest strength?”
Pick one, make it relevant to the posting, and prove it immediately. A list of three adjectives is weaker than one strength with evidence attached.
“Tell me about a time you failed”
Covered in detail in our guide to structuring behavioural answers. In short: a real failure, a real consequence, and a specific behaviour change afterwards.
Competence and behaviour
These are behavioural questions and they all take the STAR structure — situation and task briefly, action at length, result at the end. The recurring ones:
- “Tell me about a difficult colleague or stakeholder.” Assessing: whether you describe their position fairly. Describe what they wanted and why it was reasonable from where they sat, then what you did.
- “Describe a time you had to persuade someone without authority.” Assessing: influence. The answer is almost always evidence, a pilot, or finding what they actually needed.
- “Tell me about working under pressure.” Assessing: prioritisation. Say what you dropped, not just what you did — that is the interesting decision.
- “Give me an example of a mistake you made.” Assessing: whether you disclose early. The strongest versions include telling someone before they found out.
- “How do you handle competing deadlines?” Assessing: whether you negotiate scope or silently miss things.
“How would your manager describe you?”
Answer as though your manager might be asked. Two or three characteristics, at least one that is a limitation, and something they would actually say.
“She would say I am the person she gives the messy problems to, and that I am difficult about deadlines I think are unrealistic — I will push back rather than agree and miss it. She has told me both of those things directly.”
The role itself
“What do you know about us?”
Fifteen minutes of preparation covers this. What they sell, who to, roughly how big, recent significant news, and who their competitors are. Do not recite the About page. Say what you understood and where you are uncertain.
“Why should we hire you?”
An invitation to summarise your case. Two or three specific reasons tied to the requirements, plus honesty about the gap.
“Three reasons. I have solved the scheduling problem you described, at a smaller scale but the same shape. I have run supplier renegotiation, which the posting lists and which people in operations often have not done. And I am comfortable being the person who says the current process is broken, which this role seems to need. The gap is manufacturing, and I would be learning that.”
“What would your first ninety days look like?”
Increasingly common, especially at manager level. The right answer is weighted toward learning, not action — a candidate who arrives with a full restructuring plan for a business they have not seen is a risk, not an asset.
“First month, mostly listening — sit with the schedulers, walk the floor, meet the suppliers, and find out where the time actually goes rather than where people think it goes. By the end of the second month I would want a view on the two or three biggest constraints and to have tested that view with the team. Third month, pilot one change — small, reversible, measurable — rather than rolling out anything wide.”
Money and logistics
“What are your salary expectations?”
Give a researched range and a basis for it, or deflect once and then answer. Covered fully in our guide on answering the salary expectations question.
“Are you interviewing elsewhere?”
Be honest without detail. “Yes, I am at final stage with one other company” is useful information for both of you and does not require naming anyone.
“When could you start?”
State your actual notice period. Offering to breach it signals how you will treat them on the way out.
The illegal and the borderline
In most of the UK, US, Canada, Australia, and the EU, employers may not make hiring decisions based on age, marital or family status, pregnancy, religion, disability, or ethnicity, and questions about these are either unlawful or strong evidence of unlawful intent. The specific rules vary by jurisdiction.
Common examples: “Do you have children?” “Are you planning to start a family?” “What year did you finish school?” “Where are you originally from?” “What is your current salary?” — the last of which is banned in many US states specifically.
You have three options, and all are legitimate:
- Answer the concern rather than the question. To “do you have children?”: “If you are asking about the travel in the role, that is not a problem for me.”
- Ask why. “Can I ask how that relates to the role?” Often it was thoughtless rather than deliberate, and this surfaces it politely.
- Decline. “I would rather keep that separate from the application, if that is all right.”
Treat the question as information about the employer as well. A hiring manager who probes your family plans has told you something worth knowing before you accept.
Preparation that works: six to eight real stories, fifteen minutes on the company, three questions to ask them, and one run-through of your “tell me about yourself” answer out loud. That covers the large majority of what any interview will ask. Memorising a hundred answers does not.
Common questions
Is it acceptable to take notes into the interview?
Yes, and it reads as preparation rather than weakness. Bring the job description, your questions, and brief prompts for your stories. Reading answers verbatim is a different matter.
What if I go blank?
Say so and buy time: “Give me a second to pick the right example.” A five-second pause is invisible to the interviewer and enormous to you. Filling the silence with improvisation is what actually damages the answer.
Should I ask for clarification if I do not understand a question?
Always. Answering a question you misheard wastes two minutes and reads worse than asking. “Do you mean within my team, or across the business?” is a good question, not a failure.
How honest should I be about not knowing something technical?
Completely. “I have not used that — here is the closest thing I have done” is a strong answer. Bluffing a technical answer to someone who does the work daily is transparent and ends the interview in practice if not in form.
Do I need to send a thank-you email?
It is expected in the US and optional elsewhere. A short note within 24 hours — three or four sentences, referencing something specific from the conversation — costs nothing and occasionally helps. A long one does not help more.
