50 Most Common Interview Questions and How to Answer Them

How a job interview works (timeline)

Most hiring processes follow the same shape, whatever the job title on the ad.

1. Screening call (20-30 minutes). Usually a recruiter or coordinator. They check the basics: what you do now, why you applied, notice period, availability, location or right-to-work admin, and whether your expectations are in the same range as the budget. This is where "tell me about yourself" and "why this role?" first appear.
2. Hiring manager interview (45-60 minutes). The person who will manage you. They test whether you can do the work and whether they want you in their team. Expect behavioural questions — "tell me about a time…" — and follow-up probes on anything vague.
3. Task, test or presentation. Common in technical, analytical, creative and customer-facing roles. Sometimes a live exercise, sometimes work done at home and then discussed.
4. Panel or final round. Two to four people, often including a peer and someone from another team. They are checking consistency: do your stories hold up when someone else asks the same thing differently?

Seniority changes the emphasis, not the structure. Entry-level rounds lean on transferable examples from study, volunteering or part-time work. Mid-level rounds go deep on your own delivery. Senior rounds add scope questions — budgets, headcount, stakeholders, how you handle disagreement upwards — and often a conversation with a director or founder.

Timelines vary widely by employer and country. As a rough marker, Glassdoor's analysis of interview reviews put the average process at 23.7 days across the 25 countries it sampled in 2017, and SHRM's benchmarking has been cited as showing an average of 42 days to fill a role. Assume weeks, not days, and keep other applications moving.

What interviewers are assessing (list)

Behind the wording, most questions map to a handful of things an interviewer has to be able to write down afterwards.

• Structured communication — can you answer the question asked, in order, without a five-minute preamble? Shows up in "tell me about yourself" and in how you handle follow-ups.
• Evidence of impact — do your stories end in a result someone else noticed? Shows up whenever they say "what happened in the end?" or "how did you know it worked?"
• Judgement under pressure — how you choose when you cannot do everything. Shows up in prioritisation, deadline and "what would you do if…" questions.
• Ownership and honesty — whether you can describe a failure without blaming a manager, a client or a system. Shows up in weakness, mistake and feedback questions.
• Collaboration and conflict — how you behave when someone disagrees with you. Shows up in teamwork questions and in how you talk about your last employer.
• Motivation and fit — whether your reasons for applying survive one follow-up question. Shows up in "why us", "why now" and "where do you see yourself".

Common questions, by type (list)

Group your prep by type rather than memorising a list in order. Ten of these are answered in full in the next section.

General

• Tell me about yourself.
• Why did you apply for this role?
• What do you know about us?
• What are you looking for in your next job?
• Why are you leaving your current role?
• What are your strengths?
• What's your greatest weakness?
• How would your last manager describe you?
• What motivates you at work?
• Where do you see yourself in five years?
• What are your salary expectations?
• When could you start?

Experience

• Walk me through your CV.
• Tell me about a project you're proud of.
• Tell me about a time you missed a deadline.
• Describe a time you had to learn something quickly.
• Tell me about a time you disagreed with a colleague.
• Give me an example of working with a difficult customer or stakeholder.
• Tell me about a time you took on work outside your job description.
• Describe a time you received critical feedback.
• Tell me about a time you improved a process.
• What's the biggest mistake you've made at work?
• Tell me about a time you had to influence someone without authority.
• Describe a time you worked in a team that wasn't working.

In-depth

• How do you prioritise when everything is urgent?
• Talk me through the tools you use daily and what you use each one for.
• How do you measure whether your work has succeeded?
• What would your first 30, 60 and 90 days here look like?
• What would you do if you were given a task you didn't know how to do?
• How do you handle being given unclear instructions?
• What's a decision you'd make differently now?
• Why should we hire you over the other candidates?

Questions in depth, with sample answers (qa)

Behavioural questions reward structure. The STAR method — Situation, Task, Action, Result — is a widely used way to answer them, and it exists to stop you drifting (Big Interview). Use it as scaffolding, then take the scaffolding out of your voice.

Tell me about yourself

Why they ask: it tests structured communication and relevance — whether you can select the parts of your history that matter to this job. It also sets the frame for everything that follows.

How to approach it: give three beats in about 90 seconds — what you do now and at what scope, one or two proof points, and why this role is the logical next step. Do not narrate your life from school onwards. Finish on the job you are applying for so the next question is theirs to ask.

Operations coordinator, 4 years, applying to a logistics team

I'm an operations coordinator at a regional distribution site, where I handle inbound scheduling for about 40 deliveries a day and I'm the main contact for six carriers. The part of the job I'm strongest at is fixing the admin that slows people down — last year I rebuilt our booking sheet in Excel with a shared slot system, which cut our average driver wait time from around 50 minutes to 20 and stopped the daily phone calls to the gate. Before that I spent two years in customer service, which is where I got comfortable delivering bad news early. I'm applying here because this role covers carrier negotiation as well as scheduling, and that's the piece I've only done informally so far.

Mistake to avoid: starting with "I was born in…" and arriving at your current job four minutes in. Fix: write your first sentence out and make it your job title, scope and one number.

Why do you want to work here?

Why they ask: it tests motivation and fit, and whether you researched the employer or mass-applied. Interviewers are predicting how likely you are to accept an offer and stay.

How to approach it: name one specific thing about the organisation, one specific thing about the role, and connect both to what you want to do more of. Anything you could say about a competitor does not count.

Support agent applying to a small software company

Two things. First, the role: you've said support here owns the bug triage handoff rather than just escalating tickets. In my current job I raise around 25 bugs a month through Jira but never see the fix, and I want to be in the loop where the product actually changes. Second, the size. I've worked in a 60-person support floor and a 9-person team, and I was better in the small team — I knew the product properly instead of one queue of it. You're at the stage where I'd be covering a wider surface, which is what I'm after. I also read your public changelog before applying, and the fact you publish known issues openly matches how I like to talk to customers.

Mistake to avoid: praising the company's size, reputation or "great culture" with no example. Fix: quote one concrete thing you read, used or noticed, and say why it matters to you.

What is your greatest weakness?

Why they ask: it tests self-awareness and ownership. They want to see whether you can name a real limitation and show you are managing it, not whether you are flawless.

How to approach it: pick something true, non-fatal for this job, and already in hand. Structure it as weakness, evidence it caused a problem, what you changed, what it looks like now. Avoid disguised boasts.

Junior data analyst, two years in a marketing team

I over-polish. Early on I'd spend a day making a dashboard look right when the team needed a rough number by lunchtime. It came to a head when a campaign review was delayed because I was still fixing chart formatting. My manager's line was that a 70% answer today beats a perfect one on Thursday, so I changed how I work: I now send a first pass in Slack within a couple of hours, labelled as draft, and only build the full Looker view once someone confirms the question is right. It's saved rework too, because twice the question changed after the draft. I still have to consciously stop myself tidying, but nobody's waiting on me now.

Mistake to avoid: "I'm a perfectionist" or "I work too hard", offered with a smile. Fix: choose a weakness that cost something real, and say what the cost was.

Tell me about a time you failed

Why they ask: it tests ownership and learning. The failure itself matters less than whether you take responsibility and can describe what you changed afterwards.

How to approach it: choose something genuinely yours, from far enough back that the lesson is visible in how you work now. Spend a third of the answer on the failure and two thirds on the response. Never blame a named person.

Warehouse team leader, first year in the role

I took over a night shift of 11 people and decided in my first month to change the pick route without telling the day shift. I'd modelled it and it was faster on paper. In practice, day shift was restocking to the old layout, and we lost about two nights of productivity and had a genuinely bad-tempered handover. It was my call and I hadn't consulted anyone. I reverted it the same week, then went back and did it properly: I walked the floor with the day supervisor, we trialled the new route on two aisles for a fortnight, and we rolled it out together with a laminated map at each end. That version stuck, and pick times did come down. Now I don't change anything cross-shift without the other supervisor's name on it.

Mistake to avoid: choosing a fake failure — a project that succeeded anyway, or one caused entirely by someone else. Fix: pick a story where you say the words "that was my decision".

Tell me about a disagreement with a colleague

Why they ask: it tests collaboration and conflict handling — specifically whether you can hold a position without damaging the relationship.

How to approach it: pick a professional disagreement about work, not a personality clash. Show the other person's reasoning fairly, describe how you resolved it, and say what the working relationship was like afterwards.

Marketing executive in a three-person team

Our designer and I disagreed about a landing page. He wanted a single long scroll; I wanted the sign-up form above the fold because our analytics showed most traffic came from mobile and dropped off in the first ten seconds. We were going in circles in Slack, so I asked for 20 minutes with the numbers on screen. His point was fair — the long version told the story better for the people who did scroll. We agreed to test both for two weeks rather than argue about it. The short version won on sign-ups, but we kept his narrative section below the form, and that's now our template. What mattered more was that he suggested the next test himself. We still work together on every launch.

Mistake to avoid: saying you have never disagreed with anyone. Fix: it reads as either passive or evasive — bring one small, resolved example.

Walk me through a project on your CV in detail

Why they ask: it tests depth and honesty about your own contribution. Padded CVs collapse here, because the interviewer can keep asking "and how did you do that part?"

How to approach it: choose a project you personally did the work on, not one you were adjacent to. Cover the goal, your specific role, the constraints, one decision you made and why, and the outcome. Be explicit about which parts were someone else's.

Facilities administrator at a multi-site charity

The project was consolidating maintenance contracts across our four sites. I owned the data and the tender pack; my manager owned the final supplier decision. I started by pulling three years of invoices into one spreadsheet, which took a fortnight because two sites filed on paper. That showed we were using 11 contractors for work that overlapped heavily. I wrote the specification, ran the tender, and scored the responses against criteria we'd agreed up front — response time weighted highest, because our biggest complaint was waiting days for a callout. We went from 11 contractors to 3. Response time on urgent jobs went from two days to same-day for the main site. The bit I'd do differently is the paper filing — I should have asked for a week of admin help rather than doing it all myself.

Mistake to avoid: saying "we" for the whole story so your own contribution never appears. Fix: use "I" for what you did and name the colleague's part separately.

How do you prioritise when everything is urgent?

Why they ask: it tests judgement under pressure and whether you communicate trade-offs rather than quietly dropping things.

How to approach it: describe an actual method, not an attitude. Name how you rank, who you tell, and what happens to the work you deprioritise. One real example beats a general philosophy.

Office manager supporting a 40-person office

I rank by consequence and deadline, in that order. Anything that stops other people working — building access, a broken meeting room before a client visit — jumps the queue, because one blocked person costs more than my whole to-do list. Everything else goes into a Trello board with three columns: today, this week, and parked. The part people notice is the parking. If I'm dropping something, I message the person who asked and give them a new date rather than letting it go quiet. On one bad week we had a flood in the kitchen and an audit on the same day; I handled the flood, told the auditor's contact I'd have the documents by 2pm instead of 10am, and they were fine with it. Nobody minds waiting. They mind not knowing.

Mistake to avoid: answering with "I'm good under pressure and I just get it all done". Fix: name your actual system, even if it is a notebook, and say who you tell when something slips.

Why are you leaving your current role?

Why they ask: it tests motivation and professional judgement, and it is a risk check — they are listening for whether the thing driving you out will exist here too.

How to approach it: be honest but forward-facing. Name what you want more of rather than what you resent. If the reason is redundancy, a contract ending or a relocation, say so plainly and move on.

Retail supervisor moving into hospitality

I've been at the same store for three years and I've had a good run there — I went from part-time to supervising a team of eight. The limit now is that the next step up is a store manager role, and the two nearest stores have had the same managers for years, so realistically it's a long wait. I also found the part of the job I enjoy most is the shift leadership and training, and this role is more of that and less stock admin. There's nothing wrong with where I am. I gave my manager a heads-up that I was looking, and she's a reference. I'd rather move for a job I want than wait for a vacancy that might not appear.

Mistake to avoid: criticising a named manager or describing your current workplace as toxic. Fix: keep it to structure — scope, progression, commute, direction — and let it be short.

What are your salary expectations?

Why they ask: it tests preparation and whether you are in the same range as the budget. It is a screening question, not a negotiation yet.

How to approach it: find out what the role pays before you answer. Check the range in the advert, the published range where one is required, recruiters, professional bodies and public pay data for your country and region. Then either give a range you would genuinely accept, or ask what the band is. Pay structure matters as much as the number: base, bonus, shift premiums, overtime and benefits are not comparable across employers.

Project coordinator, second interview, mid-sized firm

I'd rather anchor this to your band than guess. The advert gave a range and I applied because it works for me — I'd expect to sit in the upper half of it given I've coordinated three concurrent projects and I'm already certified in the tool you use. Before I commit to a figure, can I ask two things? First, whether the band moves at all for someone who could also cover the reporting side, which the job description lists as desirable. Second, how the package is structured — whether there's a bonus element and how it's assessed. If the base is at the lower end but there's a clear review at six months, that changes my answer.

Mistake to avoid: naming a figure before you have checked what the role pays in that market. Fix: look up current rates for your country and region first, and keep the range narrow and defensible.

Where do you see yourself in five years?

Why they ask: it tests motivation and realism — whether your direction fits a path that exists here, and whether you have thought past the next paycheque.

How to approach it: talk about capability rather than job titles. Say what you want to be good at, what kind of responsibility you want, and how this role is step one. Being honest about uncertainty is fine if you are specific about direction.

Mechanical technician, five years' experience

I want to be the person who's trusted with the diagnosis, not just the fix. Right now I do planned maintenance and breakdowns on two production lines. In five years I'd like to be leading a small maintenance team and owning the reliability plan — deciding what we monitor and why, rather than reacting. To get there I need two things: more time on the condition-monitoring side, which this role has, and my level 4 qualification, which I've started. I'm not fixed on a title. If that ends up being a senior technician role with a mentoring element rather than a supervisor job, that suits me too. What I don't want is to still be doing exactly this job, on the same two lines, in five years.

Mistake to avoid: naming the interviewer's own job as your five-year goal. Fix: describe the responsibility you want, not the seat you want to take.

Questions to ask the interviewer (list)

Ask three or four. Having none looks like low interest; having twelve turns the room into your interview of them.

• What does a good first six months look like in this role? — tells you how they will judge you, and gives you the shape of your 30/60/90 answer if there is another round.
• What's the hardest part of this job that isn't obvious from the advert? — surfaces the real constraint: understaffing, a difficult stakeholder, a system nobody likes.
• Who would I work with most closely day to day? — reveals whether the role sits inside a team or alone between two departments.
• Why is the role open — is it new, or a replacement? — a backfill with high turnover is worth one more question; a new role means the scope is still being written.
• What are the next steps and when should I expect to hear? — sets a date you can follow up against without guessing.

Prep checklist (checklist)

• Write six to eight real stories from your own work, each with a situation, your action and a measurable result — the Situation-Task-Action-Result structure is the standard way to keep behavioural answers organised (Big Interview). Map each story to two or three of the questions above so you are never hunting for an example.
• Practise out loud, not in your head. CareerOneStop, the US Department of Labor's careers service, recommends reviewing common questions and rehearsing them with another person or in front of a mirror.
• Time your "tell me about yourself" answer. If it runs past two minutes, cut the oldest job.
• Re-read the job advert and underline every requirement, then check you have one example for each. Any requirement with no example is a gap to prepare for.
• Look up pay for the role in your country and region — the advert range, recruiters, professional bodies and public pay data — so the salary question does not catch you cold.
• For a video interview, do a tech check the day before: CareerOneStop's virtual interview guidance puts being tech-ready first, meaning your computer, camera and microphone are tested and working. Check lighting and background too.
• Prepare your three or four questions for them, and write down the name and role of everyone you will meet.

Frequently asked questions

Sources

1. CareerOneStop (U.S. Department of Labor) — Interview Tips
2. CareerOneStop (U.S. Department of Labor) — Virtual interviews
3. Big Interview — The STAR Interview Method: How to Answer + Examples
4. Workable — Time to fill and time to hire metrics FAQ
5. Glassdoor — How Long Does it Take to Hire? Interview Duration in 25 Countries (2017)