20 Common Interview Questions and How to Actually Answer Them

Most interview questions aren't actually testing what they appear to test on the surface — "tell me about yourself" isn't a request for your biography, and "what's your biggest weakness" isn't fishing for a genuine confession. Understanding what each common question is actually probing for makes it much easier to give an answer that lands, rather than memorising a generic script that could apply to anyone.

Opening and background questions

• "Tell me about yourself" — this is asking for a focused, professional narrative (roughly a minute) connecting your relevant experience to the role you're interviewing for, not a full life story. A useful structure: where you are now, the relevant experience that got you here, and why this specific role is the logical next step.
• "Why do you want to work here?" — a generic answer about the company being "innovative" or "a great culture" signals you haven't researched anything specific. A strong answer names something concrete about the company's product, mission or recent direction and connects it to your own specific interests or experience.
• "Why are you leaving your current job?" — frame this around what you're moving toward (growth, a specific kind of work, a better fit for your skills) rather than what you're moving away from — even a genuinely bad current situation is better described in terms of what you're now seeking.

Behavioural questions — the STAR method actually matters here

Questions starting with "tell me about a time when..." are behavioural questions, and the single most effective way to answer them is the STAR structure: Situation (brief context), Task (what you specifically needed to do), Action (what you actually did — the part that should get the most detail), and Result (the measurable or observable outcome). Without this structure, answers tend to either ramble without a clear point or skip straight to a vague outcome without explaining what you actually did to get there — both of which leave the interviewer unable to assess your actual contribution.

• "Tell me about a time you disagreed with a manager or teammate" — this is testing conflict-handling maturity, not whether you've ever disagreed with anyone. Pick an example where the disagreement was resolved professionally and led to a reasonable outcome, not one where you were simply right and someone else was wrong.
• "Tell me about a time you failed" — genuinely own the failure (don't disguise it as a humble-brag disguised as a weakness) and focus most of your answer on what you specifically changed afterward as a result.
• "Tell me about a time you had to meet a tight deadline" — focus on the specific prioritisation or communication decisions you made, not just that you "worked hard," since "worked hard" isn't a repeatable, transferable skill an interviewer can assess.

The weakness and strength questions

"What's your greatest weakness?" is testing self-awareness and whether you're actively working on something, not looking for a disqualifying confession or a thinly-disguised strength ("I work too hard" reads as evasive to most interviewers at this point). A genuine, moderate weakness — something real but not core to the role — paired with a specific, concrete step you're taking to address it, is a far stronger answer than either extreme. "What's your greatest strength?" is best answered with a strength directly relevant to the role, backed by a brief, specific example, rather than a generic trait with no evidence behind it.

Questions about gaps, career changes or unusual patterns

If your resume has an employment gap, a career pivot, or another pattern that invites a question, it's worth having a brief, honest, forward-looking explanation ready rather than being caught off guard — a gap for genuine reasons (caregiving, further study, health) explained plainly and briefly, followed by what you did to stay engaged or prepare for a return, generally lands better than either over-explaining defensively or hoping the topic doesn't come up at all.

Salary expectation questions

When asked your expected salary early in the process, giving a specific range grounded in market research (rather than dodging entirely or naming a single hard number too early) generally works best, since it signals you've done homework without over-committing to one figure before you know the full offer picture. For more on handling this conversation once an actual offer is on the table, see our guide on how to negotiate your salary.

Questions you should ask the interviewer

• "What does success look like in this role in the first six months?" — shows you're thinking about impact, not just getting hired.
• "What's the biggest challenge someone in this role would face right now?" — surfaces real, useful information about the actual job, not the idealised job-posting version.
• "How would you describe the team's working style?" — genuinely useful for assessing fit, and shows you're evaluating the opportunity, not just hoping to be picked.
• Avoid asking only about compensation, perks or time off in this slot — those questions are legitimate but land better in a later conversation once mutual interest is clearer.

Technical or role-specific questions

For technical roles, expect questions that test not just whether you know an answer but how you think through a problem you haven't seen before — narrating your reasoning out loud, including dead ends and how you'd verify your answer, generally scores better than silently arriving at a correct answer with no visible process, since interviewers are often assessing problem-solving approach as much as the final answer itself.

Common mistakes across all of these

• Giving generic, could-apply-to-any-company answers that show no specific research into the actual role or organisation.
• Rambling through behavioural questions without the STAR structure, leaving the interviewer unclear on your actual, specific contribution.
• Speaking negatively about a previous employer or manager, regardless of how justified the frustration might genuinely be.
• Having no questions at all for the interviewer when asked — this is consistently read as a lack of genuine interest in the role.
• Not connecting your resume's specific bullets and achievements to the answers you give — the interview should reinforce and expand on what's already on paper, not introduce a disconnected set of new claims.

Teamwork and collaboration questions

• "Tell me about a time you worked with a difficult team member" — this tests whether you can maintain professionalism and find a working path forward, not whether you can vividly describe someone else's flaws. Keep the focus on your own actions and the resolution, not an extended critique of the other person.
• "Describe your ideal working style" — answer specifically, with a real example of how you actually work (independently on deep tasks, collaboratively during planning, whatever's genuinely true), rather than a generic "I'm a team player" that could describe anyone and tells the interviewer nothing.
• "How do you handle receiving critical feedback?" — describe a specific instance where you received real feedback, took it seriously, and made a concrete change as a result — abstract statements about being "open to feedback" without a real example carry little weight.

Pressure and prioritisation questions

• "Tell me about a time you had to juggle multiple priorities" — the interviewer wants your actual prioritisation logic (what made you rank one thing above another, and why), not just a list of everything you were doing at the time.
• "Describe a high-pressure situation and how you handled it" — focus on the specific, deliberate actions you took to manage the situation, not simply that you "stayed calm," which is an outcome, not a demonstrable skill an interviewer can actually assess.
• "How do you handle ambiguity or an unclear brief?" — increasingly common as remote and cross-functional work grows more ambiguous by nature — describe how you sought clarification, made reasonable assumptions explicit, and iterated, rather than claiming you always have complete clarity from the outset.

Case-style and brainteaser questions

Certain roles (consulting, product management, some analytical positions) include case-style or estimation questions — "how would you estimate the market size for X" or "walk me through how you'd approach solving Y" — that are explicitly testing structured thinking under uncertainty rather than a single correct numeric answer. The strongest approach is narrating your framework out loud before diving into numbers: state your assumptions clearly, break the problem into logical components, and sanity-check your final answer against a rough intuition rather than presenting a number with no visible reasoning behind it — interviewers are typically far more interested in the structure of your thinking than whether your final estimate happens to be precisely correct.

Video interview specific considerations

A growing share of first-round interviews happen over video, which introduces its own small but real set of considerations beyond the content of your answers — testing your camera, microphone and internet connection well before the actual interview time, choosing a plain, well-lit background free of distractions, and looking at the camera rather than the screen when speaking (which reads as more natural eye contact to the interviewer on their end) all reduce avoidable friction that has nothing to do with your actual qualifications but can still affect the impression you leave.

Questions about your long-term goals

• "Where do you see yourself in five years?" — this is testing whether your trajectory reasonably aligns with what the role and company can actually offer, not demanding a precise five-year plan. A grounded answer connecting your growth interests to a plausible path within or adjacent to the role works better than either an overly rigid plan or a vague "I don't really think that far ahead."
• "What are you looking for in your next role?" — be specific about what genuinely matters to you (scope of ownership, a particular kind of technical challenge, team structure) rather than a generic answer that could apply to any job at any company.
• "Why should we hire you over other candidates?" — rather than trying to guess or disparage unseen competition, focus concretely on the specific combination of experience and skills you bring that's directly relevant to what the role actually needs.

Following up after the interview

A brief, genuine thank-you note sent within a day of the interview — referencing something specific discussed, not a generic template — is a small gesture that meaningfully more candidates skip than send, which is exactly why it's worth the few minutes it takes. It's not going to override a genuinely weak interview, but for a close call between similarly strong candidates, this kind of small, deliberate follow-through is sometimes the differentiator an interviewer remembers.

Preparing your own answers in advance without sounding rehearsed

The goal of preparation isn't memorising a word-for-word script for every possible question — an over-rehearsed answer tends to sound stiff and can visibly fall apart the moment a follow-up question deviates from the expected path. A more durable approach is preparing a mental list of 5-6 strong stories from your actual experience (a challenge overcome, a conflict resolved, a project delivered) that can each flex to answer several different question types, rather than a rigid one-to-one mapping between a specific question and a single memorised answer — this makes you noticeably more adaptable when a question is phrased slightly differently than you expected, which happens far more often than a purely scripted approach anticipates.

Panel interviews and multiple interviewers

When facing several interviewers at once, make eye contact with and address whoever asked the specific question first, but briefly bring the rest of the panel in as you elaborate, rather than fixating only on one person for the entire answer — panel members are often each assessing different dimensions (technical depth, cultural fit, communication), and an answer that engages the whole room reads as more confident and complete than one delivered to a single individual while the others are effectively ignored.

When you genuinely don't know an answer

Bluffing through a technical or factual question you genuinely don't know the answer to is usually more damaging than honestly saying so, then demonstrating how you'd go about finding out — interviewers generally respond far better to "I haven't worked with that specifically, but here's how I'd approach figuring it out" than to a confident-sounding but visibly incorrect answer, since the former still demonstrates genuine problem-solving ability.