Skip to content
Resume Studioby M2Toolkit

45 role-specific questions

General Professional Interviews Interview Questions & Answers

Whatever the job, most interviews share a core: introduce yourself, explain your motivation, tell stories about teamwork, pressure and mistakes, and show judgement in “what would you do if” situations.

Free, no sign-up. 45 questions in this role's practice pool, including behavioural, HR and situational questions.

HR & screening interview questions

The questions in almost every interview: introductions, motivation, strengths, weaknesses, salary and questions for the interviewer.

  1. 1.

    Tell me about yourself.

    BeginnerHR

    What the interviewer is evaluating

    Whether you can give a concise, relevant pitch that frames your experience around this job.

    Key points a strong answer covers

    • Present. Start with your current role and what you do.
    • Relevant past. Pick the most relevant past experience.
    • Strength / achievement. Include one strength or achievement with evidence.
    • Why this role. Finish with why this role is the next step.

    Suggested answer structure

    1. Present — your current role in one or two sentences.
    2. Past — the experience most relevant to this job.
    3. Proof — one achievement or strength with evidence.
    4. Future — why this role is the logical next step.

    Common mistakes

    • Reciting your whole CV chronologically.
    • Personal life story unrelated to the job.
    • Going over two minutes.

    Likely follow-up questions

    • Why are you looking to leave your current role?
    • What would your manager say is your biggest strength?
    Example strong answer

    I'm a front-end developer with four years' experience, currently at a fintech start-up where I build the customer dashboard in React and TypeScript. Before that I spent two years at an agency building e-commerce sites, which taught me to work fast with lots of different clients. The thing I'm proudest of recently is leading our move to a shared component library, which cut the time to build new screens by about a third. I'm now looking for a role where I can work on a larger product with a strong design system, which is exactly what drew me to this position.

    Practise this question and get feedback
  2. 2.

    Why should we hire you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you understand the role and can match your strengths to its needs with evidence.

    Key points a strong answer covers

    • Role's needs. Show you understand what the role needs.
    • Matching strengths. Match two or three strengths to those needs.
    • Evidence. Back each with evidence.
    • Enthusiasm. Close with genuine enthusiasm.

    Suggested answer structure

    1. Name the two or three things the role needs most.
    2. Match each with your experience and evidence.
    3. Add what makes you different.
    4. Finish with genuine interest.

    Common mistakes

    • Generic claims like 'I'm hardworking' with no evidence.
    • Comparing yourself to other candidates you don't know.

    Likely follow-up questions

    • What would you do in your first 90 days?
    • What's one area where you'd need support?
    Example strong answer

    From the job description and our conversation, you need someone who can take ownership of the customer onboarding process, work with sales and product, and improve the numbers. I've done exactly that for three years: at my current company I redesigned onboarding for new accounts and cut the time to first value from 14 days to 6. I'm comfortable working across teams — I run a weekly session with sales and product on customer feedback — and I'm very data-driven, so I'd measure everything from day one. I'm also genuinely excited about your product, because it solves a problem I've seen customers struggle with.

    Practise this question and get feedback
  3. 3.

    Why do you want to work here?

    BeginnerHR

    What the interviewer is evaluating

    Genuine, researched motivation.

    Key points a strong answer covers

    • Company research. Mention something specific you learned about the company.
    • Connection to you. Connect it to what you care about.
    • Role fit. Connect the role to your skills and goals.

    Suggested answer structure

    1. Something specific about the company — product, mission, recent news.
    2. Why it matters to you personally.
    3. How the role fits your skills and next step.

    Common mistakes

    • Flattering generalities like 'you're a great company'.
    • Focusing only on benefits or salary.

    Likely follow-up questions

    • What do you know about our competitors?
    • Where else are you interviewing?
    Example strong answer

    Three things. First, your product: I've used your scheduling app with my previous team, and I like how much you've simplified something that's usually painful. Second, I read about your expansion into the healthcare sector, and I spent two years working with clinics, so I understand their constraints. Third, the role itself — it combines customer research and data, which is the work I enjoy most and want to grow in. And from what I've seen on your engineering blog, you share how you make decisions openly, which is the kind of culture I do my best work in.

    Practise this question and get feedback
  4. 4.

    What are your greatest strengths?

    BeginnerHR

    What the interviewer is evaluating

    Self-awareness and relevance, backed by evidence.

    Key points a strong answer covers

    • Specific strengths. Name two or three specific strengths.
    • Relevant to the job. Pick strengths relevant to the job.
    • Evidence. Give evidence for each.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Listing many clichés with no proof.
    • Strengths irrelevant to the role.

    Likely follow-up questions

    • Which of those strengths has been most useful recently?
    • How would your colleagues describe you?
    Example strong answer

    My biggest strength is turning messy problems into clear plans. For example, when our support backlog hit 400 tickets, I categorised them, found that three issues drove half the volume, and worked with engineering to fix them — the backlog was under 50 within a month. The second is communication with non-technical people: I run our monthly product update for the sales team, and they've told me it's the one meeting they don't skip. Both matter here, since the role involves a lot of prioritisation and working with stakeholders.

    Practise this question and get feedback
  5. 5.

    What is your greatest weakness?

    BeginnerHR

    What the interviewer is evaluating

    Honesty, self-awareness and active improvement.

    Key points a strong answer covers

    • Real weakness. Name a real, non-critical weakness.
    • Impact. Show you understand its impact.
    • Improvement steps. Show what you're doing about it.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • A disguised strength like 'I'm a perfectionist'.
    • A weakness that's core to the job.

    Likely follow-up questions

    • How do you know you're improving?
    • What other weakness would your manager mention?
    Example strong answer

    I've tended to say yes to too many requests from other teams. It came from wanting to be helpful, but last year it meant my own project slipped by two weeks because I was constantly switching between tasks. Since then I've changed how I work: I keep my priorities visible on a shared board, and when someone asks for help, I say when I can do it and check with my manager if it would push back planned work. My focus time has gone up noticeably, and in my last review my manager said my delivery had become much more predictable. I still have to consciously manage it, but it's improving.

    Practise this question and get feedback
  6. 6.

    Where do you see yourself in five years?

    BeginnerHR

    What the interviewer is evaluating

    Ambition, realism and whether you'll stay and grow here.

    Key points a strong answer covers

    • Direction. A clear direction for your growth.
    • Linked to this role/company. Linked to this role and company.
    • Skills to build. The skills you want to build.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • 'In your job' or an unrelated career.
    • Saying you have no idea.

    Likely follow-up questions

    • What would you need from us to get there?
    • What does success look like to you?
    Example strong answer

    In five years I'd like to be a senior analyst who's known for the quality of insight behind major decisions, and ideally mentoring junior analysts. Right now I want to deepen my experimentation and forecasting skills, which this role uses heavily. I'm drawn to companies where analysts work closely with product teams, as you do, because that's where I learn fastest. If I can grow here, I'd much rather build that career in one place where I understand the business deeply.

    Practise this question and get feedback
  7. 7.

    What are your salary expectations?

    BeginnerHR

    What the interviewer is evaluating

    Preparation, market awareness and professional negotiation.

    Key points a strong answer covers

    • Researched range. Give a researched range.
    • Total package. Consider the total package.
    • Flexibility. Show flexibility on structure.
    • Ask about their range. It's fine to ask their budgeted range.

    Suggested answer structure

    1. Thank them, and say you've researched the market for this role.
    2. Give a range for the total package.
    3. Say you're open on structure and ask about their range.

    Common mistakes

    • Naming a number without research.
    • Refusing to answer at all.
    • Lying about your current salary.

    Likely follow-up questions

    • Is that range flexible?
    • What's your current salary?
    Example strong answer

    Based on my research for similar roles in this city, and my five years' experience, I'm looking for a total package in the range of 65,000 to 72,000. That's for the whole package, so I'm open on how it's structured between base, bonus and benefits. Could you tell me the range you've budgeted for the role? I'm sure we can find something that works if it's the right fit on both sides.

    Practise this question and get feedback
  8. 8.

    Why are you leaving your current job?

    BeginnerHR

    What the interviewer is evaluating

    Positive motivation and professionalism.

    Key points a strong answer covers

    • Positive reason. Frame it around what you're moving towards.
    • No badmouthing. Speak respectfully about your employer.
    • Link to this role. Link it to what this role offers.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Criticising your manager or company.
    • Vague answers that raise suspicion.

    Likely follow-up questions

    • What would make you stay?
    • How did you feel about your last manager?
    Example strong answer

    I've learned a lot in my current role and I'm grateful for it — I joined as a junior and now run our paid search campaigns. But the company is small and focused on one channel, and I want to grow into broader growth marketing across channels, with a larger team to learn from. This role offers exactly that, which is why I applied.

    Practise this question and get feedback
  9. 9.

    Can you explain this gap in your CV?

    IntermediateHR

    What the interviewer is evaluating

    Honesty and confidence about breaks.

    Key points a strong answer covers

    • Brief honest reason. Give a brief, honest reason — you don't need to over-share.
    • What you did / learned. Mention anything you did to stay current.
    • Ready now. Show you're ready and focused now.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Over-explaining or sounding apologetic.
    • Lying about dates.

    Likely follow-up questions

    • How have you kept your skills up to date?
    • Is there anything that would stop you committing to this role now?
    Example strong answer

    I took eighteen months out to care for a family member. That situation is now settled, and I'm fully ready to return to work. During that time I kept my skills current — I completed the Google Analytics certification and did two freelance projects for local businesses, setting up their analytics and reporting. It also strengthened my organisation and patience, frankly. I'm really looking forward to being back in a team, and this role is a great fit for what I did before and what I've been learning.

    Practise this question and get feedback
  10. 10.

    Do you have any questions for us?

    BeginnerHR

    What the interviewer is evaluating

    Curiosity, preparation and genuine interest.

    Key points a strong answer covers

    • Ask questions. Always ask two or three questions.
    • About the work & success. Ask what success looks like.
    • About team & culture. Ask about the team and how it works.
    • Next steps. Optionally ask about next steps.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Saying 'No, I think you've covered everything'.
    • Only asking about holidays and pay in a first interview.

    Likely follow-up questions

    • Is there anything about your background we haven't covered?
    Example strong answer

    Yes, a few. What would success look like for this role in the first six months? What's the biggest challenge the team is facing right now? How does the team decide what to work on, and how does feedback work here? And what are the next steps in the process?

    Practise this question and get feedback
  11. 11.

    How do you stay productive and connected when working remotely?

    BeginnerHR

    What the interviewer is evaluating

    Self-management and communication habits.

    Key points a strong answer covers

    • Structure. A routine and focus time.
    • Communication. Clear, proactive communication.
    • Visibility of work. Make work and progress visible.
    • Connection. Deliberate connection with colleagues.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Only describing your home office setup.
    • No mention of communication.

    Likely follow-up questions

    • How do you handle time-zone differences?
    • How do you know when to switch from chat to a call?
    Example strong answer

    I keep a consistent routine and protect blocks of focus time in my calendar, with notifications off. Because people can't see me working, I make progress visible: our board is always up to date, and I post a short written update at the end of each day with what I finished, what's next and any blockers. I default to clear written communication, and move to a quick call when a chat thread starts going in circles. I also make an effort to stay connected — short virtual coffees with colleagues from other teams. In my last fully remote role that helped me deliver every project on time and build good relationships with people I'd never met in person.

    Practise this question and get feedback
  12. 12.

    What motivates you at work?

    BeginnerHR

    What the interviewer is evaluating

    Fit between your motivation and the role.

    Key points a strong answer covers

    • Specific motivator. A specific, genuine motivator.
    • Example. An example.
    • Link to role. Link it to this role.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Only money or perks.
    • Generic answers.

    Likely follow-up questions

    • What demotivates you?
    • Tell me about a time you felt really engaged at work.
    Example strong answer

    I'm most motivated when I can see the direct effect of my work on real people. In my current job I handle escalated customer issues, and the best days are when I fix a problem that's been frustrating someone for weeks and they tell me it saved them hours. I'm also motivated by getting better at things — I like setting myself small targets, like reducing my average resolution time, and seeing them improve. This role is customer-facing and has clear metrics, so it fits both.

    Practise this question and get feedback
  13. 13.

    How do you handle stress?

    BeginnerHR

    What the interviewer is evaluating

    Resilience and practical coping strategies.

    Key points a strong answer covers

    • Strategies. Practical strategies.
    • Communication. Asking for help and communicating early.
    • Example. A real example.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Claiming you never feel stress.
    • Strategies that don't sound workable.

    Likely follow-up questions

    • Tell me about a time stress affected your work.
    • How do you know when you're taking on too much?
    Example strong answer

    I deal with stress mostly by getting organised: when there's too much going on, I write everything down, decide what genuinely matters first, and tackle that, which usually makes the pressure feel manageable. If the workload is unrealistic, I say so early and ask my manager to help prioritise, rather than quietly struggling. Outside work, running helps me switch off. For example, during our year-end close last year, I broke the work into daily goals and flagged on day two that one reconciliation needed extra help — we finished on time without a last-minute panic.

    Practise this question and get feedback
  14. 14.

    Is there anything else you'd like us to know about you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you can close strongly.

    Key points a strong answer covers

    • Summary of fit. A short summary of why you fit.
    • Something not yet covered. Anything important not yet covered.
    • Enthusiasm. Clear enthusiasm.

    Suggested answer structure

    1. Answer directly in one or two sentences.
    2. Back it up with one specific example.
    3. Connect it to this role and this company.

    Common mistakes

    • Saying 'No, that's all'.
    • Introducing a new concern.
    Example strong answer

    Just that I've really enjoyed this conversation, and it's confirmed my interest. One thing we didn't get to: as well as the campaign work we discussed, I've trained three junior colleagues on our analytics setup, so I'd be happy to help with the team's onboarding too. I think my mix of hands-on campaign experience and analytics fits what you need, and I'd love to be part of the team.

    Practise this question and get feedback

Behavioural (STAR) interview questions

“Tell me about a time…” questions answered with Situation, Task, Action and Result.

  1. 1.

    Describe a difficult problem you solved at work.

    BeginnerBehavioural

    What the interviewer is evaluating

    Problem-solving approach, persistence and the impact you made.

    Key points a strong answer covers

    • Why it was hard. Make clear why it was hard.
    • Your approach. Show your approach step by step.
    • Result. Finish with the measurable result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Picking a problem that wasn't really difficult.
    • Describing what the team did, not you.

    Likely follow-up questions

    • What would you do differently now?
    • How did you know the problem was really solved?
    Example strong answer (a fictional story — use your own)

    At a logistics company, our weekly invoices to clients were wrong about one time in twenty, and nobody knew why. My task was to find the cause before the quarter-end billing run. I pulled three months of invoices and compared the wrong ones with shipment records, and noticed every error involved shipments split across two depots. I traced it to a rule that counted the handling fee once per depot. I wrote a fix with a test for split shipments and ran the old invoices through the new logic to confirm the differences. Billing errors dropped to zero for the quarter, and we refunded affected clients proactively. I learned to look for a pattern in the failures before reading the code.

    Practise this question and get feedback
  2. 2.

    Tell me about a time you disagreed with a teammate. How did you handle it?

    BeginnerBehavioural

    What the interviewer is evaluating

    Handling conflict constructively and keeping relationships.

    Key points a strong answer covers

    • Listened to their view. Show you listened to understand their view.
    • Used facts / common goal. Bring it back to facts or a shared goal.
    • Resolution & relationship. Resolve it and keep the relationship.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Making the other person the villain.
    • A story where you were simply right and they gave in.

    Likely follow-up questions

    • What if you couldn't reach agreement?
    • Have you ever been wrong in a disagreement?
    Example strong answer (a fictional story — use your own)

    On a website rebuild, a senior designer wanted an animated, image-heavy homepage, and I was worried it would hurt mobile load times and SEO. As the developer responsible for performance, I needed us to agree before the sprint started. I asked her to walk me through what she was trying to achieve — she wanted the brand to feel premium. I built two quick prototypes, one with her full design and one with lighter animations, and we tested both on a mid-range phone together. Hers took nearly six seconds to load. We agreed on a version that kept the key animation but lazy-loaded the rest. The page launched loading in under two seconds, and she later asked me to review designs earlier. I learned that testing together beats debating.

    Practise this question and get feedback
  3. 3.

    Describe a situation where you worked under pressure or to a tight deadline.

    BeginnerBehavioural

    What the interviewer is evaluating

    Prioritisation, composure and delivery.

    Key points a strong answer covers

    • The pressure. Make the pressure concrete.
    • Prioritised. Show how you prioritised.
    • Communicated. Show how you kept people informed.
    • Delivered. Show the outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Glorifying working all night as the solution.
    • No mention of prioritising.

    Likely follow-up questions

    • What would you do if it was clear you couldn't make the deadline?
    • How do you stop pressure affecting quality?
    Example strong answer (a fictional story — use your own)

    Two days before a client presentation, our analyst fell ill and I had to finish the market research report she'd been leading. I listed everything left and asked the account director which sections the client cared about most — pricing and competitor comparison. I focused on those, reused verified data from our previous report, and moved the appendix to a follow-up email. I sent a short update each evening so nobody was surprised. We delivered the core report on time, the client approved the next phase, and the appendix followed two days later. I learned to ask early what matters most rather than trying to do everything equally well.

    Practise this question and get feedback
  4. 4.

    Tell me about a mistake you made and what you learned.

    BeginnerBehavioural

    What the interviewer is evaluating

    Honesty, accountability and learning.

    Key points a strong answer covers

    • Real mistake owned. Own a real mistake.
    • Fixed it. Show how you fixed it and who you told.
    • Changed behaviour. Show what you changed afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing a fake mistake like 'I work too hard'.
    • Blaming others.

    Likely follow-up questions

    • How did your manager react?
    • How do you know you haven't repeated it?
    Example strong answer (a fictional story — use your own)

    In my first year as a marketing coordinator, I sent a promotional email to our whole list with the wrong discount code — I'd tested the email but not clicked the code itself. Within an hour customers were complaining that it didn't work. I told my manager immediately, set the wrong code to apply the discount too, and sent a short correction email with an apology. We lost very little revenue, and some customers replied thanking us for the quick fix. Since then I use a pre-send checklist that includes testing every link and code as a customer would, and I asked for a second person to check any campaign to more than 10,000 people.

    Practise this question and get feedback
  5. 5.

    Give an example of when you showed leadership without formal authority.

    IntermediateBehavioural

    What the interviewer is evaluating

    Influence, initiative and ownership.

    Key points a strong answer covers

    • Initiative. You took the initiative.
    • Influenced others. You influenced people you didn't manage.
    • Result. A measurable result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Describing a time you were simply the manager.
    • Taking credit for the whole team's work.

    Likely follow-up questions

    • How did you handle people who didn't want to follow?
    • What did you learn about leading?
    Example strong answer (a fictional story — use your own)

    Our support team had no shared answers for common questions, so replies were inconsistent and slow. I wasn't a team lead, but I volunteered to fix it. I analysed a month of tickets, found that 12 questions made up 40% of the volume, and drafted answers for them. To get buy-in, I asked two experienced colleagues to review and improve them, so it wasn't 'my' project, and demoed the macros in our team meeting. Within a month everyone was using them, average handle time fell by 25%, and our customer satisfaction score rose from 86% to 91%. My manager asked me to own the knowledge base afterwards. I learned that involving people early is what makes them adopt a change.

    Practise this question and get feedback
  6. 6.

    Tell me about a time you failed.

    IntermediateBehavioural

    What the interviewer is evaluating

    Resilience and reflection.

    Key points a strong answer covers

    • Genuine failure. A genuine failure.
    • Your role. Your part in it.
    • Learning applied. What you learned and how you apply it.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Describing a failure caused entirely by others.
    • No lesson.

    Likely follow-up questions

    • How did you recover from it emotionally?
    • Where have you applied that lesson since?
    Example strong answer (a fictional story — use your own)

    I led a pilot to move our team's project tracking from spreadsheets to a new tool. I picked the tool, configured it, and launched it to 15 people in one go. Six weeks later only four people were still using it, and the pilot was cancelled. When I asked the team why, the answers were clear: I'd set it up around how I worked, not how they did, and I hadn't trained anyone properly. The failure was mine. Since then, for any change I lead, I involve a few users in the setup, run a small trial first, and plan training as part of the launch. When we tried again a year later with that approach, adoption reached nearly everyone.

    Practise this question and get feedback
  7. 7.

    Describe a time you had to learn something new quickly.

    IntermediateBehavioural

    What the interviewer is evaluating

    Learning agility: how you get up to speed fast, and what you delivered with it.

    Key points a strong answer covers

    • What and why fast. What you had to learn and why it was urgent.
    • How you learned. How you learned efficiently.
    • Applied it. How you applied it and the result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Not explaining your learning method.
    • No result.

    Likely follow-up questions

    • How do you usually approach learning something new?
    • What are you learning right now?
    Example strong answer (a fictional story — use your own)

    When our only data engineer left, I was asked to take over our weekly reporting pipeline, written in Python with Airflow — and I'd only used Excel and a little SQL. The next client report was due in three weeks. I read the pipeline code with the documentation open, made a list of the parts I didn't understand, and booked two sessions with an engineer from another team to go through them. I practised by rebuilding one small report myself in a test environment. I delivered the next three client reports on time and later simplified one step that kept failing. I learned that a small, real practice project teaches me faster than courses alone.

    Practise this question and get feedback
  8. 8.

    Tell me about a time you went above and beyond for a customer.

    IntermediateBehavioural

    What the interviewer is evaluating

    Customer focus and judgement.

    Key points a strong answer covers

    • Customer need. The customer's need.
    • Extra effort. What you did beyond the expected.
    • Outcome. The outcome for the customer and business.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Breaking company policy and calling it customer service.
    • No outcome.

    Likely follow-up questions

    • Where do you draw the line?
    • How did it benefit the business?
    Example strong answer (a fictional story — use your own)

    A small bakery client of our accounting software called on a Friday evening because their payroll run was failing and staff were due to be paid on Monday. Support hours were ending, but I stayed on, reproduced the issue, and found a corrupted employee record from an import. I fixed the record with them on a screen share, ran the payroll test with them, and then emailed a short guide on checking imports. On Monday I called to confirm everyone had been paid. The owner later left a public review naming me, and renewed for two years. I also logged the import bug, which engineering fixed the following sprint. I learned that a quick follow-up call matters as much as the fix.

    Practise this question and get feedback
  9. 9.

    Tell me about a time you had to juggle several priorities at once.

    IntermediateBehavioural

    What the interviewer is evaluating

    Organisation and judgement.

    Key points a strong answer covers

    • Competing demands. The competing demands.
    • How you prioritised. How you decided what came first.
    • Communicated trade-offs. How you communicated trade-offs.
    • Outcome. The outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Saying you just worked harder.
    • Not mentioning communication.

    Likely follow-up questions

    • How do you decide what to drop?
    • What tools do you use to stay organised?
    Example strong answer (a fictional story — use your own)

    In one week I had a product launch email to finish, a quarterly report for my director, and an urgent request from sales for a customer case study. I listed them with their deadlines and impact: the launch email was fixed to the launch date, the report fed a board meeting, and the case study was for a deal closing the following week. I asked my director whether the report could move by two days — it could — and told the sales manager exactly when the case study would arrive. I blocked time each morning for focused writing. All three were delivered, and the deal closed. I learned that asking about deadlines often reveals more flexibility than I'd assumed.

    Practise this question and get feedback
  10. 10.

    Tell me about a time you received critical feedback. How did you respond?

    IntermediateBehavioural

    What the interviewer is evaluating

    Coachability and growth mindset.

    Key points a strong answer covers

    • The feedback. The feedback you received.
    • Reaction. How you responded — listening, not defending.
    • Change & result. What you changed and the result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Picking feedback that was really praise.
    • Showing defensiveness.

    Likely follow-up questions

    • Was there feedback you disagreed with?
    • How do you ask for feedback?
    Example strong answer (a fictional story — use your own)

    After my first client presentation as a junior consultant, my manager told me my slides were packed with detail and I'd lost the client's attention halfway through. My first instinct was to explain how much work was behind each slide, but I asked her for specific examples instead. She showed me where the key message was buried on slide eleven. For the next presentation, I wrote the one-sentence takeaway for each slide first, moved detail to an appendix, and rehearsed with her. The client asked twice as many questions and approved our recommendation in the meeting. I now ask for feedback after every important presentation.

    Practise this question and get feedback
  11. 11.

    Describe a time you improved a process.

    IntermediateBehavioural

    What the interviewer is evaluating

    Initiative and measurable improvement.

    Key points a strong answer covers

    • Problem with the old way. What was wrong with the old process.
    • What you changed. What you changed.
    • Measured impact. The measured impact.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • No numbers or evidence of improvement.
    • Changes imposed without involving others.

    Likely follow-up questions

    • How did you get others to adopt it?
    • What didn't work?
    Example strong answer (a fictional story — use your own)

    Our HR team onboarded about 20 new starters a month, and each one involved 30 manual emails and spreadsheet updates, so things were often missed — equipment wasn't ready on day one for about a third of starters. I mapped the steps with my colleagues, then built a shared checklist with automated reminders in our existing HR system, with each step assigned to an owner. We trialled it for a month with one department before rolling it out. Preparation time per starter fell from about four hours to one and a half, and missing equipment on day one dropped to almost zero. I learned to fix the process before automating it.

    Practise this question and get feedback
  12. 12.

    Tell me about a time you had to make an ethical decision or push back on something you felt was wrong.

    AdvancedBehavioural

    What the interviewer is evaluating

    Integrity and courage.

    Key points a strong answer covers

    • The issue. What felt wrong.
    • Raised it properly. How you raised it through the right channels.
    • Outcome. The outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Telling a story that breaches confidentiality.
    • Taking dramatic action without raising concerns first.

    Likely follow-up questions

    • What would you have done if your manager disagreed?
    • How do you balance loyalty and integrity?
    Example strong answer (a fictional story — use your own)

    In a sales role, my team was encouraged to tell customers a product upgrade was 'required' before a deadline, when it was only recommended. I was uncomfortable because customers would pay for something they didn't need. I raised it with my manager privately, showing the actual wording from the product team, and suggested we explain the benefits honestly instead. She agreed and took it to the sales director, who changed the script for the whole team. Our upgrade numbers dipped slightly that quarter, but complaints and refund requests fell. I learned that raising a concern early, with facts and an alternative, usually works better than staying quiet or confronting people.

    Practise this question and get feedback
  13. 13.

    Tell me about a successful team project and your role in it.

    BeginnerBehavioural

    What the interviewer is evaluating

    Collaboration and clarity about your own contribution.

    Key points a strong answer covers

    • Team goal. The team's goal.
    • Your specific role. Your specific role.
    • Collaboration. How you worked with others.
    • Result. The team result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Using 'we' throughout so your role is invisible.
    • Taking credit for everyone's work.

    Likely follow-up questions

    • What was the hardest part of working with that team?
    • What would your teammates say about you?
    Example strong answer (a fictional story — use your own)

    Our team of five built a booking app for a chain of fitness studios in three months. I was responsible for the payments integration and the class-booking backend. Besides my part, I set up a short daily check-in with the mobile developer because our pieces depended on each other, and wrote clear API documentation so he never waited on me. When our designer was off sick for a week, I helped test the booking flow on real phones. We launched on schedule, and in the first month 60% of bookings moved from phone to the app. My manager highlighted the payments work in my review, but what I was proudest of was how smoothly the team worked.

    Practise this question and get feedback
  14. 14.

    Tell me about a time your priorities changed suddenly. How did you adapt?

    IntermediateBehavioural

    What the interviewer is evaluating

    Adaptability: how you respond to sudden change, practically and positively.

    Key points a strong answer covers

    • The change. What changed.
    • Response. How you adapted — positively and practically.
    • Result. The result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Complaining about the change.
    • No practical actions.

    Likely follow-up questions

    • How do you handle changes you disagree with?
    • How do you help others through change?
    Example strong answer (a fictional story — use your own)

    Halfway through building a new reporting dashboard, the company was acquired and leadership paused all internal tools to focus on integrating systems. My task changed overnight to migrating our customer data to the new parent's CRM. I asked my manager why the priority had changed so I understood the urgency, documented where the dashboard had got to so it could be picked up later, and spent the first week learning the new CRM's data model. I built a mapping spreadsheet with the other team and ran three test migrations. The migration finished a week early with no data loss, and six months later the dashboard was restarted from my notes. I learned that documenting work before switching makes it far easier to pick up again.

    Practise this question and get feedback
  15. 15.

    Tell me about a time you persuaded someone to change their mind.

    IntermediateBehavioural

    What the interviewer is evaluating

    Influence and communication.

    Key points a strong answer covers

    • Their position. Their original position.
    • Understood their concern. Understanding their concern.
    • Evidence & framing. Evidence framed around what they cared about.
    • Outcome. The outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Winning by pulling rank.
    • Not explaining their concerns.

    Likely follow-up questions

    • What if the evidence had gone against you?
    • Who's the hardest person you've had to persuade?
    Example strong answer (a fictional story — use your own)

    Our finance director was against moving our team's servers to the cloud because she expected costs to rise. I was the systems administrator proposing it. Rather than arguing, I asked what worried her most — unpredictable monthly bills. I built a cost model comparing three years of our current hardware, maintenance and electricity with cloud costs, including a budget alert and reserved pricing to cap the monthly bill. I proposed a three-month pilot with one non-critical system. The pilot came in 18% under its budget, and she approved the full migration. I learned to address the specific concern behind an objection rather than the objection itself.

    Practise this question and get feedback
  16. 16.

    What achievement are you most proud of?

    BeginnerBehavioural

    What the interviewer is evaluating

    What you value, and evidence of impact.

    Key points a strong answer covers

    • The achievement. The achievement.
    • Your contribution. What you personally did.
    • Why it matters. Why it matters to you.
    • Result. The concrete result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing something irrelevant to the job.
    • No evidence of impact.

    Likely follow-up questions

    • What made it difficult?
    • What did it teach you about yourself?
    Example strong answer (a fictional story — use your own)

    I'm most proud of the mentoring scheme I set up at my last company. New junior developers were taking around six months to work independently, and two had left in their first year saying they felt lost. I proposed pairing each new hire with a mentor for their first three months, wrote a simple guide for mentors, and matched the first eight pairs myself. I collected feedback monthly and adjusted the format. Within a year, new hires were contributing independently in about three months, and none left in their first year. I'm proud of it because it helped people, not just a metric, and it continued after I left.

    Practise this question and get feedback

Situational interview questions

“What would you do if…” questions about judgement, priorities, ethics and working with others.

  1. 1.

    What would you do if you realised you were going to miss a deadline?

    BeginnerSituational

    What the interviewer is evaluating

    Transparency and problem solving.

    Key points a strong answer covers

    • Tell people early. Flag it as soon as you know.
    • Assess the gap. Work out how far off you are.
    • Options. Offer options: reduced scope, help, a new date.
    • Prevent repeats. Learn why it happened.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Waiting until the deadline to say anything.
    • Promising you'll just work all night.

    Likely follow-up questions

    • What if your manager is unavailable?
    • Has this happened to you?
    Example strong answer

    I'd tell the person depending on it as soon as I realised, not at the deadline. Before that conversation I'd work out how far off I am and why, so I could offer options: delivering the most important part on time and the rest a few days later, getting help from a colleague, or agreeing a new date. Then I'd let them decide what works best for them, and keep them updated. Afterwards I'd look at why it slipped — usually underestimating something — so I plan better next time.

    Practise this question and get feedback
  2. 2.

    What would you do if a colleague wasn't doing their share of the work on a shared project?

    IntermediateSituational

    What the interviewer is evaluating

    Handling peer conflict maturely.

    Key points a strong answer covers

    • Talk privately first. Talk to them privately first.
    • Assume good intent. Try to understand why.
    • Agree clear roles. Clarify who does what and by when.
    • Escalate if needed. Involve the manager only if it continues.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Going straight to the manager.
    • Silently doing their work and resenting it.

    Likely follow-up questions

    • What if it's affecting the deadline right now?
    • What if they're more senior than you?
    Example strong answer

    I'd talk to them privately first, without accusing them — something like, 'I've noticed the data section hasn't moved this week; is everything OK?' There may be a reason I don't know about, like they've been pulled onto something urgent. Then we'd agree clearly who's doing what and by when, and maybe split the work differently. If nothing changed and the project was at risk, I'd raise it with our manager, focusing on the project and the facts rather than the person, and suggest a solution.

    Practise this question and get feedback
  3. 3.

    What would you do if your manager gave you a task with unclear instructions?

    BeginnerSituational

    What the interviewer is evaluating

    Initiative and communication.

    Key points a strong answer covers

    • Clarify. Ask clarifying questions.
    • Understand the goal. Understand the goal and what success looks like.
    • Play back a plan. Summarise your understanding and plan.
    • Check in early. Share an early version for feedback.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Guessing and spending days on the wrong thing.
    • Repeatedly asking without trying to work it out.

    Likely follow-up questions

    • What if your manager is too busy to answer?
    • How do you avoid asking too many questions?
    Example strong answer

    I'd ask a few targeted questions straight away — mainly what it's for and what a good result looks like, plus deadline and format. Then I'd play back my understanding in a short message — 'So you need a one-page summary of last quarter's churn by segment, for Thursday's leadership meeting' — so we're both clear. If my manager was busy, I'd make reasonable assumptions, note them, and share an early rough version so they could correct my direction before I'd invested too much time.

    Practise this question and get feedback
  4. 4.

    Two senior people give you urgent tasks that you can't both finish today. What do you do?

    IntermediateSituational

    What the interviewer is evaluating

    Prioritisation and managing up.

    Key points a strong answer covers

    • Clarify urgency. Clarify the real deadlines and impact.
    • Don't decide alone. Let the right person decide the priority.
    • Communicate. Communicate clearly with both.
    • Options. Offer options like partial delivery or help.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Secretly picking one and ignoring the other.
    • Trying to do both badly.

    Likely follow-up questions

    • What if neither will compromise?
    • What if your own manager is one of them?
    Example strong answer

    First I'd find out the real deadlines and what happens if each is late — sometimes 'urgent' means 'this week'. If both genuinely need it today, I wouldn't quietly pick one. I'd tell both people about the conflict and ask my manager — or the two of them together — to decide the priority, offering options: one done today and the other first thing tomorrow, a quicker partial version of one, or a colleague helping. Then I'd confirm the decision in writing so expectations are clear.

    Practise this question and get feedback
  5. 5.

    What would you do if you discovered a mistake in work that had already been sent to a client?

    IntermediateSituational

    What the interviewer is evaluating

    Integrity and damage control.

    Key points a strong answer covers

    • Assess impact. Assess how serious it is.
    • Tell your manager. Tell your manager immediately.
    • Correct & inform the client. Correct it and inform the client transparently.
    • Prevent. Prevent it happening again.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Hoping nobody notices.
    • Fixing it silently without telling anyone.

    Likely follow-up questions

    • What if it was someone else's mistake?
    • What if it was tiny?
    Example strong answer

    I'd first check how serious it is — a typo is different from a wrong number that affects a decision. Then I'd tell my manager straight away with a proposed fix, rather than hoping nobody notices. For anything material, we'd send the client a corrected version quickly with a short, honest note explaining what changed. Clients usually respect a fast correction far more than discovering a mistake themselves. Afterwards I'd work out how it slipped through and add a check to prevent it.

    Practise this question and get feedback
  6. 6.

    What would you do if you strongly disagreed with a decision your manager made?

    IntermediateSituational

    What the interviewer is evaluating

    Speaking up respectfully and committing.

    Key points a strong answer covers

    • Understand reasoning. Seek to understand their reasoning.
    • Raise it privately with evidence. Raise your concern privately with evidence.
    • Disagree and commit. Once decided, support it fully.
    • Escalate only if serious. Escalate only for ethical, legal or safety issues.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Complaining to colleagues.
    • Undermining the decision afterwards.

    Likely follow-up questions

    • What if you turn out to be right?
    • When would you go above your manager?
    Example strong answer

    I'd first make sure I understand the reasoning — managers often have context I don't. If I still disagreed, I'd raise it privately and respectfully, with evidence: 'I'm worried this will delay the launch because of X; could we consider Y?' If my manager still decides to go ahead, I'd support the decision fully and help make it work, rather than complaining to colleagues. The exception would be if it were unethical, illegal or unsafe — then I'd escalate through the appropriate channels.

    Practise this question and get feedback
  7. 7.

    What would you do in your first 90 days in this role?

    IntermediateSituational

    What the interviewer is evaluating

    Planning, learning orientation and early impact.

    Key points a strong answer covers

    • Learn first. Spend the first weeks learning and building relationships.
    • Relationships. Meet the team and key stakeholders.
    • Early wins. Deliver some early wins.
    • Goals & plan. Agree goals and a plan with your manager.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Promising big changes before understanding the business.
    • Only describing learning, no contribution.

    Likely follow-up questions

    • What would you need from your manager?
    • How would you know you were on track?
    Example strong answer

    In the first 30 days I'd focus on learning: understanding the product, customers and current priorities, meeting my team and key stakeholders one-to-one, and agreeing with my manager what success looks like at three and six months. By 60 days I'd be contributing fully to the team's work and aim for a couple of early wins — small improvements I'd spotted while learning. By 90 days I'd own my areas independently and share a short plan for the improvements I think would have the biggest impact, based on what I'd learned rather than assumptions from my last job.

    Practise this question and get feedback
  8. 8.

    What would you do if a customer was angry about a problem that wasn't your fault?

    BeginnerSituational

    What the interviewer is evaluating

    Ownership and composure.

    Key points a strong answer covers

    • Stay calm & listen. Stay calm and listen.
    • Empathise without blame. Empathise without blaming colleagues.
    • Own the resolution. Take ownership of getting it resolved.
    • Follow up. Follow up until it's resolved.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Saying 'that's not my department'.
    • Blaming another team in front of the customer.

    Likely follow-up questions

    • What if you can't fix it yourself?
    • What if they ask to speak to your manager?
    Example strong answer

    To the customer, it doesn't matter whose fault it was — I represent the company. I'd stay calm, let them explain, and acknowledge their frustration and apologise for the experience, without blaming another team. Then I'd take ownership of getting it resolved: if I can't fix it myself, I'd find the person who can, explain the situation so the customer doesn't have to repeat themselves, and tell the customer exactly what will happen and when. I'd follow up until it's done.

    Practise this question and get feedback
  9. 9.

    What would you do if your manager asked you to do something you believed was unethical?

    AdvancedSituational

    What the interviewer is evaluating

    Integrity under pressure.

    Key points a strong answer covers

    • Clarify first. Make sure you've understood correctly.
    • Raise concerns. Raise your concerns and suggest an alternative.
    • Refuse if needed. Decline if it's genuinely unethical.
    • Escalate properly. Escalate through HR, compliance or an ethics line.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Saying you'd just do it.
    • Dramatic reactions without clarifying first.

    Likely follow-up questions

    • What if it might cost you your job?
    • Where's the line between unethical and uncomfortable?
    Example strong answer

    I'd first make sure I'd understood correctly, because sometimes a request sounds wrong without the full context. If it was still unethical — say, backdating a document or misleading a customer — I'd raise my concerns with my manager calmly, explaining the risk and suggesting an alternative that achieves the goal properly. If they insisted, I would decline and escalate through the right channel, such as HR, compliance or the company's ethics line. I'd keep notes of what happened. Protecting the company and customers matters more than avoiding an awkward conversation.

    Practise this question and get feedback
  10. 10.

    What would you do if you were asked a question you didn't know the answer to — in a meeting or by a customer?

    BeginnerSituational

    What the interviewer is evaluating

    Honesty and resourcefulness.

    Key points a strong answer covers

    • Be honest. Say honestly that you don't know rather than guess.
    • What you do know. Share what you do know or how you'd reason about it.
    • Find out & follow up. Commit to finding out and following up by a specific time.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Bluffing.
    • Saying 'I don't know' and stopping there.

    Likely follow-up questions

    • Has bluffing ever backfired for someone you worked with?
    • How do you follow up?
    Example strong answer

    I'd say honestly that I don't know rather than guess — a confident wrong answer does much more damage than 'let me check'. I'd share what I do know, if it helps, then commit to finding out and getting back to them by a specific time, and make sure I do. For example: 'I'm not certain whether that integration supports SSO; I'll confirm with our engineering team and email you by tomorrow afternoon.'

    Practise this question and get feedback

Problem solving interview questions

Reasoning out loud: estimates, decisions with incomplete information, prioritising and explaining complex ideas.

  1. 1.

    Estimate how many cups of coffee are sold in your city each day.

    IntermediateProblem solving

    What the interviewer is evaluating

    Structured reasoning and stating assumptions — not the exact number.

    Key points a strong answer covers

    • Clarify & assume. State your assumptions clearly.
    • Break it down. Break it into smaller, estimable parts.
    • Calculate. Calculate step by step, out loud.
    • Sanity check. Sanity-check the answer another way.

    Suggested answer structure

    1. Restate the problem and your assumptions.
    2. Break it into steps and reason out loud.
    3. Check your answer against an edge case.
    4. Summarise the result and what you'd verify next.

    Common mistakes

    • Guessing a number without showing reasoning.
    • Over-complicating with too many factors.

    Likely follow-up questions

    • How would you check this estimate with real data?
    • Which assumption has the most effect on the answer?
    Example strong answer

    I'll assume a city of about 2 million people. Roughly 75% are adults — 1.5 million. Let's say half of adults drink coffee daily, so 750,000 people, averaging about two cups each — around 1.5 million cups a day. But the question is about cups sold, not drunk; perhaps a third are bought from cafés, offices or shops, and the rest made at home, so about 500,000 cups sold. As a sanity check from the supply side: if the city has around 1,500 places selling coffee and each sells 300 cups a day, that's 450,000 — the same order of magnitude, so I'd say roughly half a million. The assumption that matters most is the share bought rather than made at home.

    Practise this question and get feedback
  2. 2.

    Tell me about a time you had to make a decision with incomplete information.

    IntermediateBehavioural

    What the interviewer is evaluating

    Judgement under uncertainty.

    Key points a strong answer covers

    • The uncertainty. What you didn't know.
    • How you reasoned. How you weighed the options and risks.
    • Decision & safeguards. The decision and how you limited the risk.
    • Outcome. The outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Waiting for perfect information.
    • No reasoning behind the decision.

    Likely follow-up questions

    • How do you decide when you have enough information?
    • What would you have done if it had gone wrong?
    Example strong answer (a fictional story — use your own)

    Our main supplier warned us of a possible two-week delay a month before our busiest season, but couldn't confirm it. I was the operations coordinator, and waiting for certainty would have been too late. I looked at what we did know — our stock levels covered nine days — and the cost of each option. Ordering a backup batch from a second supplier would cost about 8% more but avoid empty shelves. I recommended ordering half the usual batch from the backup supplier, which limited the extra cost while covering the gap, and I asked the main supplier for weekly updates. The delay did happen; we stayed in stock, and the extra cost was far less than lost sales. I learned to ask how reversible a decision is before deciding how much information I need.

    Practise this question and get feedback
  3. 3.

    Explain something complex from your field to me as if I were a ten-year-old.

    BeginnerProblem solving

    What the interviewer is evaluating

    Communication and depth of understanding.

    Key points a strong answer covers

    • Analogy. Use an everyday analogy.
    • Simple language. Plain words, no jargon.
    • Core idea correct. Keep the core idea accurate.
    • Check understanding. Check understanding or give an example.

    Suggested answer structure

    1. Restate the problem and your assumptions.
    2. Break it into steps and reason out loud.
    3. Check your answer against an edge case.
    4. Summarise the result and what you'd verify next.

    Common mistakes

    • Using jargon anyway.
    • Oversimplifying until it's wrong.

    Likely follow-up questions

    • Now explain it to a senior executive.
    • What did you leave out, and why?
    Example strong answer

    I'll explain how a website remembers you're logged in. Imagine going to a theme park: at the entrance they check your ticket once and give you a wristband. After that, every ride just looks at your wristband instead of asking for your ticket again. A website does the same: when you log in with your password, it gives your browser a little digital wristband called a cookie, and each time you click a page, your browser shows the wristband so the website knows it's you. That's also why you should never share it — anyone wearing your wristband can go on your rides. Does that make sense?

    Practise this question and get feedback
  4. 4.

    You arrive on Monday to 40 emails, three meeting requests and a report due Wednesday. How do you plan your day?

    BeginnerSituational

    What the interviewer is evaluating

    Practical prioritisation.

    Key points a strong answer covers

    • Triage quickly. Triage quickly rather than answering in order.
    • Urgent vs important. Sort by urgency and importance.
    • Protect focus time. Block time for the report.
    • Communicate / delegate. Decline, reschedule or delegate where possible.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Answering every email in order before starting the report.
    • Accepting every meeting.

    Likely follow-up questions

    • What if your manager adds an urgent task at noon?
    • Which tools do you use to stay organised?
    Example strong answer

    I'd spend the first 20 minutes triaging rather than replying in order: scanning the emails for anything urgent or from key people, flagging those, and noting the rest for later. For the meeting requests, I'd check whether each needs me — accept the ones where I'm essential, suggest a later slot or ask for notes on the others. Then I'd block two focused chunks of time today and tomorrow for the report, since that's the fixed deadline, and tell my manager if I see any risk to it. I'd handle the remaining emails in two short batches, late morning and end of day, instead of constantly checking.

    Practise this question and get feedback
  5. 5.

    A process at work keeps going wrong, and people keep patching it. How would you find the root cause?

    IntermediateProblem solving

    What the interviewer is evaluating

    Analytical method beyond quick fixes.

    Key points a strong answer covers

    • Gather facts. Gather facts about when and how it fails.
    • Root-cause technique. Use a technique like the 5 whys or a fishbone diagram.
    • Involve the people. Involve the people who run the process.
    • Fix & verify. Fix the cause and verify it worked.

    Suggested answer structure

    1. Restate the problem and your assumptions.
    2. Break it into steps and reason out loud.
    3. Check your answer against an edge case.
    4. Summarise the result and what you'd verify next.

    Common mistakes

    • Adding another patch.
    • Blaming individuals instead of the process.

    Likely follow-up questions

    • How do you know you've found the real root cause?
    • What if the fix needs another team?
    Example strong answer

    First I'd gather facts: when it goes wrong, how often, what the failures have in common, and what each patch did. Then I'd sit with the people who run the process, since they usually know where it breaks. With that, I'd use the five whys — for example, orders ship late; why? Picking starts late; why? The order list arrives at 11am instead of 8am; why? The overnight export fails when an order has a special character; why? The export script doesn't handle them. That's the root cause, not 'staff are slow'. I'd fix the cause, remove the patches, and measure for a few weeks to confirm the problem has gone.

    Practise this question and get feedback

Ready to answer them out loud?

Run a timed general professional interviews mock interview, type or speak your answers, and get a score breakdown with what to improve.

Interview questions for related roles