50 Most Common Interview Questions & Answers

By Rehearsa Team · 2026-09-04

Most interviews are not original. Across recruiter screens, hiring manager rounds and final-stage panels, the same fifty or so questions come back again and again — reworded, reordered, but fundamentally the same. That is good news: the interview is a predictable exam, and you can revise for it.

This is the full list, grouped by the round you will hear them in, with a detailed model answer or step-by-step structure for each one. Do not memorise the scripts word for word — interviewers can hear a rehearsed answer. Learn the shape of each answer, swap in your own evidence, then rehearse out loud until it sounds like you.

How to use this list

Work through it in three passes:

Skim all fifty and mark the ten that make you uncomfortable. Those are your real prep list.
Draft your own version of each marked answer using the structure shown — bullet points, not a script.
Say them out loud, timed. Reading an answer and saying it are completely different skills, and only one of them is tested.

Round	Questions to focus on	Target answer length
Recruiter screen	1–12	60–90 seconds
Hiring manager	13–30	90–120 seconds
Behavioural / STAR	31–42	90–120 seconds
Culture and values	43–47	60–90 seconds
Your questions	48–50	Ask 3, listen hard

Most behavioural answers below use the STAR structure — Situation, Task, Action, Result. If that is new to you, read the STAR technique guide first; everything from question 31 onwards assumes it.

Opening and background questions (1–12)

These come up in the recruiter screen. They are filters, not deep dives. Keep them short, confident and consistent with your CV.

1. Tell me about yourself

Why they ask it: it is a calibration question, not an invitation to your life story. The recruiter wants to know whether you can summarise your professional identity in ninety seconds and whether it matches the role.

How to answer it: use the three-step formula — present role, one or two proof points, then the bridge to this job.

Present: one sentence on your current role and scope.
Proof: one or two achievements with a number in each.
Bridge: why this role, now, is the logical next step.

Model answer:

"I'm a customer success manager at a B2B software company, looking after around forty mid-market accounts. Last year I took our renewal rate from 82% to 94% by rebuilding how we onboard new customers, and I now run the quarterly business reviews for our five biggest accounts. I'm looking for a role with more ownership of the whole account lifecycle — and from the job description, that's exactly what this position is."

Three sentences, one or two numbers, one bridge. Nothing chronological, nothing personal.

2. Why are you looking to leave your current role?

Why they ask it: they are checking for red flags — conflict with a manager, performance issues, impatience. They also want to hear that you are running towards something, not just away.

How to answer it: neutral fact about your situation, then a forward-looking reason. Zero blame, zero bitterness. Two sentences is ideal.

Model answer:

"The team restructured last quarter and my remit narrowed to a single product line. I've learned a lot there, but I want breadth again — working across multiple products and stakeholders — and that's exactly what this role offers."

Never say your manager is difficult, the company is a mess, or that you are bored. Even if all three are true.

3. Why do you want to work here?

Why they ask it: this is the single most common screen-stage rejection reason. Generic enthusiasm ("great culture, exciting mission") tells the recruiter you applied to fifty jobs with the same cover letter.

How to answer it: name two specific things — one about the business, one about the role — and connect each to your experience.

Model answer:

"Two reasons. First, your move into the mid-market segment last year — I've spent four years serving exactly that customer base, and I know where companies get it wrong. Second, this role owns onboarding end-to-end, which is the part of my current job I've had the most impact on and want to do more of."

If you cannot name two specifics after ten minutes on their website and LinkedIn, you are not ready for the call.

4. What do you know about us?

How to answer it: one sentence on what the company does (in your own words, not their tagline), one on a recent development (funding, launch, expansion), one on why it matters to you. Check the careers page, the last quarter's news, and — if it is a product company — actually use the product for ten minutes.

Model answer:

"You build scheduling software for healthcare clinics, and from what I've read you've grown mainly through word of mouth. I saw you launched the patient portal last month — that tells me you're moving upmarket, which is exactly the customer transition I've managed before and the challenge I'd want to work on."

5. Walk me through your CV

Why they ask it: unlike question 1, this one is chronological — they want the story of your career decisions. The hidden test is whether your moves make sense.

How to answer it: compress hard. Thirty seconds per role maximum, and end each role with why you moved. The transitions are the interesting part, not the job duties.

Structure: "I started as X, where I learned [skill]. I moved to Y because [reason], and there I [achievement]. After that I wanted [gap], so I joined Z, which is where I [achievement]. And that's what brings me to this role — [bridge]."

Three roles, two minutes total. If you have a ten-year career, group the early roles into one sentence.

6. What are your salary expectations?

Why they ask it: budget calibration. Price yourself out of range and you may not get to the next round; price yourself too low and you start a negotiation from the floor.

How to answer it: give a researched range with a reason attached, then signal flexibility on the total package. Then stop talking — the silence afterwards is normal, and whoever speaks first loses leverage.

Model answer:

"Based on the market rate for this level in London — I've looked at comparable roles on Glassdoor and through recruiters I work with — I'm targeting £58,000 to £65,000 base. I'd flex on the exact number for the right scope and development budget, and I'd want to understand the full package."

Research the range before the call: job ads with posted salaries, salary surveys, recruiters, and peers in your network.

7. What is your notice period?

How to answer it: state it plainly, then add flexibility if you genuinely have it. Never inflate it to seem more in demand — offer letters get rescinded over discovered lies, and this one is easy to check.

Model answer:

"Officially four weeks. I've built a good relationship with my manager, so if we needed to negotiate a handover plan I could likely shorten it to three — but I'd commit to four as the safe answer."

If you are between jobs: "I could start within two weeks, or sooner if it mattered."

8. Are you interviewing elsewhere?

Why they ask it: they are gauging your timeline and how competitive the process will be — not trying to catch you out.

How to answer it: honest and unpanicked. Confirm you are active in the market (it signals demand), keep the detail vague, and reaffirm your interest in this role.

Model answer:

"I'm in early conversations with two other companies, both at first or second round. I want to be transparent that this role is my first choice — the scope matches what I want to do next more closely than either of the others."

If you are not interviewing anywhere else, say so calmly: "This is the first process I've entered — I was waiting for the right role rather than applying widely."

9. Why this industry / why this move?

Why they ask it: career changers and industry switchers get this. They want proof the move is deliberate, not a scattergun application.

How to answer it: connect one thing you already do well to one thing the new field needs, and show you have done homework on the differences.

Model answer:

"I've spent five years in retail operations, and the part of the job I was best at — and enjoyed most — was demand forecasting. Logistics runs on the same discipline but at higher stakes, and I've been deliberately building towards it: I completed the APICS certification last year and I've been shadowing our supply chain team for six months."

10. What are you looking for in your next role?

Why they ask it: a fit check. The recruiter is holding the job description in one hand and your answer in the other, checking whether they match.

How to answer it: answer in terms of this job description. Name the two or three elements of the role you most want — scope, growth, ownership — and skip anything the role does not offer. If your honest answer would not fit this job, this is the wrong interview.

Model answer:

"Three things: end-to-end ownership of projects rather than contributing a slice, a team where engineering and commercial work closely together, and a manager who gives real feedback. From everything I've read and our conversation today, this role ticks all three."

11. Can you explain this gap in your CV?

Why they ask it: gaps are rarely disqualifying — defensive, rambling explanations of gaps are.

How to answer it: three sentences. What happened, what you did with the time, why you are ready now. No apology, no over-explaining.

Model answer:

"I took eight months out as the primary carer for a parent. During that time I kept my skills current — I finished a data analytics course and did two freelance projects. I came back ready, and my last role showed that: I was promoted within a year."

Redundancy version: "My role was made redundant in a company-wide restructure along with forty others. I used the time to [course/project/freelance work], and I'm interviewing from a position of choice, not urgency."

12. What is your current or most recent role responsible for?

Why they ask it: calibration of your level. Titles mean nothing across companies; scope means everything.

How to answer it: scope first (team size, budget, region, accounts, revenue), then the outcome you personally own, then one line on how you spend your week.

Model answer:

"I own the onboarding function for our UK client base — that's a team of three and roughly £2m of first-year contract value flowing through us each year. My personal number is time-to-value: how fast a new client goes live. Day to day I split between running the team, handling escalations, and improving the playbook."

Role, skills and motivation questions (13–30)

The hiring manager round goes deeper. Every answer here needs evidence attached — a claim without an example counts as zero.

13. What are your greatest strengths?

Why they ask it: self-awareness plus fit. The hiring manager wants to hear strengths they actually need, not your personal favourites.

How to answer it: pick two strengths that appear (directly or implicitly) in the job description, and prove each with a one-line example. Two proven strengths beat four asserted ones.

Model answer:

"Two. First, turning messy processes into repeatable ones — at my current company I rebuilt the handover process between sales and delivery, and errors dropped by about 60%. Second, stakeholder communication — I run a weekly written update that three directors have told me is the only one they actually read."

14. What is your biggest weakness?

Why they ask it: a self-awareness test. "I'm a perfectionist" and "I work too hard" are disqualifying because they are evasions — they tell the interviewer you will not give them a straight answer.

How to answer it: a real, non-fatal weakness (nothing that breaks the core of the job — a salesperson should not say "I hate cold calling"), then the correction you have in progress, then evidence the correction is working.

Model answer:

"I used to hold on to work too long before sharing it — I wanted it finished before anyone saw it. It slowed feedback down and meant I occasionally polished the wrong thing. Now I deliberately share a rough version at the 40% mark and ask for direction early. My last project went through two fewer revision rounds because of it, so I know the fix is working."

15. Why should we hire you?

Why they ask it: this is your closing statement. They are handing you the floor — modesty here reads as a lack of conviction.

How to answer it: three reasons, each mapped to one of their top three requirements from the job description, each with evidence. Structure: "You need X — I've done X, here's the proof."

Model answer:

"From what you've described, you need three things. Someone who can own client relationships at senior level — I manage our five largest accounts directly. Someone who can fix onboarding — I rebuilt ours and cut time-to-value from six weeks to three. And someone who can work across teams without friction — I run the weekly sales-to-delivery meeting today. That's why I'd be confident taking this on."

16. What makes you a good fit for this specific role?

How to answer it: this is question 15's more literal cousin. Quote the job description back with evidence attached. The closer your answer mirrors their language, the easier you make their scorecard.

Model answer:

"The job description asks for someone who can 'run reporting and manage senior stakeholders' — in my current role I produce the monthly board pack and present it to our leadership team, so that's literally my Tuesday morning. It also asks for SQL — I use it daily and built two of the dashboards the team relies on."

17. How would your manager describe you?

Why they ask it: reference-check preview. They may actually call this person, so your answer must be one your manager would confirm.

How to answer it: use words you could defend under verification, then immediately add the example that earned the description. One trait, one story.

Model answer:

"She'd say I'm the person she doesn't have to check on. When she was on leave for two weeks last year, I ran the team stand-ups, handled two escalations, and she came back to zero surprises in her inbox. She mentioned that specifically in my last review."

18. How would your colleagues describe you?

How to answer it: different angle from question 17 — this is about collaboration behaviour, not output. Focus on reliability, clarity, and how you behave under pressure.

Model answer:

"Reliable, and calm when things go wrong. When we had the system outage in March, I was the one keeping the shared doc updated and fielding questions so the engineers could actually fix it. A colleague sent me a message afterwards saying my updates were the only reason the support team stayed sane that day."

19. What has been your biggest professional achievement?

How to answer it: full STAR, with the number at the end — and choose something relevant to this role, not the most impressive thing you have ever done. A hiring manager for an operations role cares more about your process improvement than your award.

Model answer:

"When I joined, client onboarding took six weeks and satisfaction scores were dropping. I was tasked with fixing it without adding headcount. I mapped every step, cut four redundant approvals, and introduced a kickoff checklist with clear owners. Onboarding dropped to three weeks, and first-90-day satisfaction went from 7.1 to 8.8 out of ten. That's the achievement I'd want to replicate here."

20. What are you most proud of outside of results?

Why they ask it: a values test disguised as a soft question. They want to know what you care about when nobody is measuring it.

How to answer it: mentoring someone who then succeeded, fixing a broken process nobody asked you to fix, raising a standard. One story, told plainly.

Model answer:

"I mentored a junior colleague who had been written off by her previous manager. We did a weekly thirty minutes for eight months. She's just been promoted, and she told the team the sessions were a big part of it. That mattered more to me than most of my numbers."

21. Where do you see yourself in five years?

Why they ask it: they are checking that this role is a step in your plan, not a stopgap — and that your ambitions are ones this company can actually satisfy.

How to answer it: direction, not job titles. "I want to be Head of X" can be a trap if the role reports into Head of X. Describe the kind of work, scope and impact you want to grow into.

Model answer:

"In five years I want to be the person a company trusts with its most important client relationships — deeper expertise, bigger accounts, probably mentoring others on how to do it. This role is the right next step because it's the first one where I'd own the full lifecycle rather than a slice of it."

22. How do you prioritise when everything is urgent?

Why they ask it: "everything is urgent" is most companies' default state. They need someone with a method, not someone who just works longer hours.

How to answer it: name your actual method — impact versus effort, a weekly triage, a shared priority list — then give a real example of something you deliberately dropped or deferred, and how you communicated it.

Model answer:

"I run a Monday triage: everything on the list gets scored on impact and deadline, and I share the ranked list with my manager so priorities are agreed, not assumed. Last quarter I deliberately deferred a reporting request from another team for two weeks — I told the requester on day one, explained why, and gave them a date. Nobody was surprised, and the urgent client work shipped on time."

23. How do you handle tight deadlines?

Why they ask it: "I work late" is not a method — it is a confession that you cannot plan. They want to hear planning, early escalation and scope negotiation.

How to answer it: show the sequence — assess, flag risks early, renegotiate scope if needed, then execute.

Model answer:

"First I work backwards from the deadline and find the critical path. Then I flag risks on day one, not day three — if something looks impossible, I go to the stakeholder early with options: cut scope, add help, or move the date. Last month that meant proposing we launch a report with three sections instead of five; the stakeholder chose that over a late full version, and the last two sections followed a week later."

24. Tell me about a time you managed competing stakeholders

How to answer it: STAR, and the result must be a decision everyone accepted, not just a task you completed. Hiring managers ask this because stakeholder conflict is where projects actually die.

Model answer:

"Sales wanted a feature shipped in two weeks; engineering said it needed six. My task was to get a plan both would commit to. I got both leads in one room with the data — sales' revenue estimate versus engineering's breakdown of the work — and we agreed a phased release: a basic version in three weeks, full version in eight. Both signed off in the meeting, and we hit both dates."

25. What tools and systems do you use day to day?

How to answer it: be specific and honest about depth. "Advanced in X, working knowledge of Y, learning Z" is a trustworthy answer; claiming expertise in everything is not.

Model answer:

"Daily: Salesforce at an advanced level — I build my own reports and dashboards. Excel, genuinely advanced — pivot tables, lookups, some macros. SQL at a working level — I can pull my own data but I'd struggle with complex joins. And I've started learning Tableau because I can see the team moving towards it."

26. How do you measure success in this role?

Why they ask it: they want to know whether your definition of success matches theirs — a mismatch means a painful year for everyone.

How to answer it: answer with their metrics where you can infer them from the job description. If you do not know them, say what you would measure in the first month and ask what they track — turning the question into a conversation is a strength, not a dodge.

Model answer:

"From the job description, I'd guess the core metrics are retention and expansion revenue. In my first month I'd confirm exactly how they're measured and where the baseline sits. What do you track most closely for this role? — because I'd want to be optimising for your definition of success, not my guess at it."

27. What would your first 90 days look like?

Why they ask it: this answer wins offers. It proves you understand how onboarding actually works — learn before you change things.

How to answer it: three thirty-day blocks: learn, deliver something small, propose a plan.

Model answer:

"First thirty days: learn. Meet every stakeholder, understand the current process, and resist changing anything — I'd want to earn context before I earned changes. Days thirty to sixty: pick one small, visible problem and fix it properly, so the team sees momentum. Days sixty to ninety: bring my manager a written plan for the next two quarters, based on what I've actually seen rather than what I assumed in the interview."

28. How do you keep your skills current?

Why they ask it: vague answers ("I read a lot") read as no answer. They want evidence of a real, running system.

How to answer it: name specific sources — a named newsletter, a course you finished (with the date), a community or practice habit.

Model answer:

"Three ways. I read the Growth in Reverse newsletter and two industry blogs every week. I finished the Reforge growth strategy course in the spring — paid for it myself. And I'm in a peer group of five people in similar roles who meet monthly to swap what's working. Between those three I'm rarely more than a month behind."

29. What is the most difficult decision you have made at work?

Why they ask it: they want your reasoning process and how you handled the fallout — not the drama of the situation.

How to answer it: STAR with the emphasis on how you decided: what options you weighed, whose input you sought, and how you handled the people affected.

Model answer:

"I had to recommend discontinuing a product line two people on my team had built. I spent two weeks on the data, asked both of them for their honest assessment — which I included in my recommendation — and then advocated internally for both to be moved to the new priority project. The line was cut, both kept their roles, and one of them later told me being consulted made the difference."

30. What motivates you?

How to answer it: tie it to the work itself first, then to the environment. Money alone reads badly; pretending money does not matter reads dishonestly.

Model answer:

"Honestly? Seeing something I built actually get used. When the onboarding process I rebuilt became the template for two other teams, that kept me going for months. Environment-wise, I do my best work where feedback is direct and fast. And I'd be lying if I said being recognised and paid fairly for impact didn't matter — it does, to everyone."

Behavioural and STAR questions (31–42)

These all start with "tell me about a time." Prepare six stories and you can answer all twelve — achievement, failure, conflict, pressure, persuasion, learning. Rehearse them out loud with Rehearsa's interview practice so the timing is trained, not improvised.

31. Tell me about a time you failed

Why they ask it: everyone fails; not everyone extracts the lesson. They are testing honesty and whether the failure produced a permanent change in behaviour.

How to answer it: own the failure without softening it, show specifically what you changed, and prove the change stuck with a later example.

Model answer:

"Early in my current role I launched a client survey without testing the questions on a small group first. The response rate was 9% and half the data was unusable. It was entirely my fault — I rushed it. I rebuilt the process: now every survey goes through a five-person pilot before launch. The next one got 41% responses, and the pilot step is now in the team playbook. That's the failure I think about most, because the fix outlasted the embarrassment."

32. Tell me about a conflict with a colleague

Why they ask it: they are not listening for the conflict — they are listening for the resolution. The result must be a repaired working relationship, not you winning.

Model answer:

"A colleague and I disagreed over who should own a client escalation — we both thought the other had dropped it. It got tense in a meeting. Afterwards I asked him for a coffee and started with what I could have done better, which lowered the temperature immediately. We agreed a simple rule: whoever touches a client issue first owns it until explicitly handed over. We worked together well for two more years after that, and the rule went into the team guidelines."

33. Tell me about a time you received difficult feedback

Why they ask it: defensive answers here are disqualifying. This question predicts how you will respond to your future manager.

How to answer it: reaction, action, outcome. Show that your first reaction was to listen, your second was to change something specific, and that the outcome is verifiable.

Model answer:

"My manager told me my written updates were so detailed that nobody read them — including her. It stung because I was proud of the thoroughness. I asked her what she actually needed, which was three lines and a red/amber/green status. I rewrote the format that week. Six months later she told me my updates were the ones she forwarded upward, so the feedback clearly landed."

34. Tell me about a time you led without authority

Why they ask it: especially for candidates without formal management experience, this is how they test leadership. The answer must show influence and alignment, not title.

Model answer:

"Three teams needed to agree a shared reporting format and it had been stuck for months — nobody owned it. I wasn't anyone's manager, so I couldn't direct anyone. I drafted a compromise version myself, visited each team lead separately to hear their objections before any meeting, and adjusted the draft twice. By the time we all sat down together, everyone had already seen their input in the document, and it was approved in twenty minutes."

35. Tell me about a time you solved a difficult problem

How to answer it: spend most of the answer on your diagnosis, not the fix. Interviewers want to see how you think; the fix is usually the boring part once the real problem is found.

Model answer:

"Customer churn spiked 15% in one quarter and everyone assumed it was pricing. I pulled the exit interviews and support tickets and found the real pattern: customers were leaving within ninety days of a staff change on our side — the relationship handover was broken, not the price. We built a structured handover process with a joint-call standard. Churn from that cause dropped by two-thirds in two quarters."

36. Tell me about a time you worked under pressure

How to answer it: one clear crisis, your specific decisions, the outcome. No heroics, no "I thrive under pressure" — show the method inside the chaos.

Model answer:

"Our biggest client's system went down two days before their board presentation, and their CEO was personally involved. I set up a twice-daily update rhythm so the client never had to chase us, pulled one engineer off another project with that manager's agreement, and gave the client a workaround within four hours so their demo could proceed. Full fix landed in thirty-six hours. They renewed three months later and cited the incident handling as a reason."

37. Tell me about a time you had to persuade someone

Why they ask it: the differentiator is whether you understood the other person's objection before you tried to address it. Persuasion by repetition is a fail.

Model answer:

"I wanted budget for a customer onboarding tool and my director kept saying no. Instead of re-pitching, I asked what his concern actually was — it turned out to be implementation time, not cost, because the team was already stretched. I came back with a phased plan where the vendor did the setup and we only committed two hours a week. Approved the same day. The lesson: the first no is rarely about what you think it is."

38. Tell me about a time you made a mistake with real consequences

Why they ask it: speed of disclosure matters more than the mistake. They want to know whether you hide problems or surface them.

Model answer:

"I sent a pricing proposal to a client with last quarter's discount structure — about 8% too low. I caught it the next morning. I called my manager first, then called the client myself within the hour, owned it plainly, and honoured the quoted price for that deal. It cost us margin, but the client renewed and mentioned the honesty in the renewal call. Hiding it or blaming a 'system error' would have been the real mistake."

39. Tell me about a time you improved a process

How to answer it: baseline number → change → new number. This is the cleanest STAR answer you can give, so make the numbers crisp.

Model answer:

"Our weekly reporting took the team six hours every Friday, mostly copy-pasting between systems. I mapped where the time went, then built one automated pull and a standard template. Friday reporting dropped to ninety minutes. That is twenty-plus hours a month returned to the team — and the report is more accurate now because nothing is retyped."

40. Tell me about a time you worked with a difficult manager

Why they ask it: interviewers hear this answer as a preview of how you will one day describe them. Neutral, professional, adaptive — never bitter.

Model answer:

"I had a manager who changed priorities weekly, which made planning impossible. Rather than complain, I adapted: I started sending a two-line written confirmation after every priority conversation — 'confirming the top three are X, Y, Z' — and asked him to correct me if wrong. He almost always replied, and the changes dropped noticeably because he could see his own pattern in writing. We actually parted on good terms."

41. Tell me about a time you missed a target

How to answer it: honesty plus analysis. What you would do differently is the whole answer — the miss itself is just the setup.

Model answer:

"I missed my quarterly renewal target by 12%. The honest reason: I spent the quarter chasing two large new deals that both slipped, and neglected the renewal base. My analysis afterwards showed renewals had been my most reliable revenue all along. The next quarter I ring-fenced two days a week for renewals regardless of what else was happening, and hit 108%. I still keep that ring-fence — the miss taught me where my revenue actually lives."

42. Tell me about a time you had to learn something quickly

How to answer it: method first, result second. How you learn is the transferable part they are buying.

Model answer:

"A colleague left suddenly and I inherited our SQL-based reporting with no handover and a board pack due in ten days. My method: I found the three reports that mattered most, reverse-engineered those queries line by line, and booked thirty minutes with someone in data engineering to sanity-check my understanding instead of struggling silently. The board pack went out on time. Within a month I was improving the queries, not just running them."

If your STAR answers feel thin, the fix is almost always missing results — see common interview mistakes for the pattern and the repair.

Culture, values and working style (43–47)

Often run by a peer or cross-functional interviewer rather than your future manager. See the culture fit questions guide for the full set.

43. What kind of environment do you do your best work in?

Why they ask it: a genuine mutual-fit question. Misrepresenting yourself here only buys you a job you will dislike — and they know it, so honesty reads as maturity.

How to answer it: be honest and specific about conditions, not perks: pace, feedback style, autonomy level, collaboration density.

Model answer:

"I do my best work where expectations are explicit and feedback is fast. I like autonomy on how I deliver as long as we're aligned on what good looks like. One thing I've learned about myself: I go quiet in very slow consensus cultures, and I know that about myself now. From what you've described — weekly priorities, direct feedback — this sounds like the environment where I produce my best work."

44. How do you like to receive feedback?

How to answer it: "direct, early, specific" is the answer — but it only counts if you attach an example of feedback that actually changed how you work.

Model answer:

"Direct and early. I'd rather hear something uncomfortable in week one than discover it in an annual review. For example, a manager once told me bluntly that I interrupted people in meetings. It wasn't fun to hear, but I started counting to two before responding, and within a month two colleagues commented on the difference. That's the kind of feedback I want more of."

45. Do you prefer working independently or in a team?

Why they ask it: a trap if you pick one — almost every real role needs both. The answer they want is judgement: knowing when each mode is right.

How to answer it: "both, with a switch" — then give the example that shows the switch.

Model answer:

"Both, and I think the skill is knowing when to switch. Deep work — analysis, writing, building — I do alone and protect time for it. But decisions that affect other teams I deliberately make in a group, early, before I've fallen in love with my own answer. For example, when I rebuilt our onboarding process I drafted it solo, then ran two workshops before finalising — the final version was about 30% theirs, and much better for it."

46. What would make you leave a job?

Why they ask it: they want your values in reverse — and they are checking whether your dealbreakers describe their own company.

How to answer it: answer with values, not grievances. No learning, no integrity, no direction — and never "bad management" or "politics," which invite follow-ups you do not want.

Model answer:

"Three things. If I stopped learning — I'd give that about six months before I got restless. If I was ever asked to do something I considered dishonest with a customer — that's an immediate one. And if the company lost its direction and nobody could articulate where we were going. Interesting problems and honest people keep me; that's really it."

47. How do you handle disagreement with a decision you did not choose?

Why they ask it: senior interviewers are listening for one specific pattern: disagree, commit, revisit. Nobody wants a passenger, and nobody wants a saboteur.

Model answer:

"I disagree honestly, once, with evidence — in the meeting where it matters, not in corridors afterwards. Then if the decision stands, I commit to it fully, including in front of my own team, because undermining a decision you disagreed with is worse than the decision itself. If the data later proves the concern, I bring it back with numbers, not 'I told you so.' Example: I disagreed with a tooling choice last year, committed anyway, and six months in the data supported my concern — we switched, with the original decision-maker's support, because I'd been a grown-up about it."

Your questions and the close (48–50)

The last five minutes decide more offers than candidates realise. This is where you stop being evaluated and start evaluating.

48. What questions do you have for us?

Why they ask it: "no, I think you've covered everything" is a quiet rejection. Your questions signal how seriously you think about work.

How to answer it: never "none." Ask three, written down beforehand: one about the role's first six months, one about the team, one about how success is measured.

Model questions:

"What would you want this person to have achieved by month six for you to feel the hire was a great one?"
"What's the team's biggest frustration right now that this role could help with?"
"How is success measured for this role, and how often is it reviewed?"
"What do the people who thrive here have in common — and what about the ones who don't?"

49. Is there anything that concerns you about my application?

Why they ask it: they do not — you ask this. It is the strongest closing question available because it surfaces objections while you are still in the room to answer them.

How to use it: ask it near the end, plainly: "Before we finish — is there anything about my background that gives you hesitation? I'd rather address it now." If they name a concern, answer it calmly with evidence. If they say none, you have made it easy for them to say it again in the debrief.

50. What are the next steps?

How to answer it: ask for the timeline and who you will meet next — this is practical information you are entitled to, and asking it signals you are organised. Then follow up within 24 hours with a short note referencing one specific thing you discussed, not a generic thank-you.

Model follow-up:

"Thank you for the conversation today — the point you made about the handover problem between sales and delivery stayed with me, and it's exactly the kind of problem I fixed in my current role. Looking forward to the next round on Thursday as discussed."

The 30-minute prep plan

If you only have half an hour before an interview:

10 minutes — draft answers to questions 1, 2, 3 and 6 using the structures above. These four decide most screens.
10 minutes — pick three STAR stories that cover achievement, failure and conflict, and bullet the numbers in each.
5 minutes — write your three questions for them.
5 minutes — say your "tell me about yourself" out loud three times, timed.

Reading answers builds false confidence. The gap between knowing an answer and delivering it under pressure — steady pace, eye contact, no filler — only closes with reps. Practise a full interview with Rehearsa and get scored feedback on your structure, clarity and body language before the real thing.

Related resources

More Interview Questions guides · Start free trial