Behavioural interview question bank

Conflict and disagreement

Tell me about a time you disagreed with your manager.

A strong answer names the specific decision, states your reasoning briefly without relitigating it, and describes raising the concern once, respecting the final call, and what happened afterward.

Describe a conflict with a coworker and how you resolved it.

Focus on the underlying interest behind the disagreement, not the argument itself, and end with what changed about how you work together — not just that it "worked out."

Tell me about a time you had to give someone difficult feedback.

Interviewers listen for whether you addressed the behaviour privately and specifically, not the person’s character, and whether you checked afterward that it landed.

Describe a time you pushed back on a request you thought was wrong.

Show you understood the requester’s constraint before pushing back, offered an alternative, and were willing to be overruled and still execute well.

Failure and mistakes

Tell me about a time you failed.

Pick a real failure with a concrete consequence, not a humblebrag disguised as a weakness, and state what you would do differently rather than just that you "learned a lot."

Describe a project that did not go as planned.

Name the specific miscalculation — scope, timeline, a technical assumption — rather than blaming external factors, and describe the recovery, not just the outcome.

Tell me about a time you missed a deadline.

Good answers show the risk was flagged early rather than staying silent until it was too late, plus what changed in how you estimate or communicate afterward.

Describe a time you received critical feedback.

The interviewer wants the feedback taken at face value first, without a defensive reflex, and one concrete change made because of it.

Ownership and initiative

Tell me about a time you went beyond your job description.

The bar is a real gap you noticed and owned, not a task your manager assigned you that happened to be extra.

Describe a time you identified a problem nobody had asked you to fix.

Strong answers explain how you noticed it — data, a recurring complaint — and why it was worth your time over other priorities.

Tell me about a decision you made without complete information.

Focus on how you bounded the risk, such as a small test or a reversible choice, rather than claiming certainty you did not have.

Describe a time you had to learn something new quickly.

Concrete detail on the learning method — who you asked, what you built to test understanding — matters more than the fact you eventually succeeded.

Teamwork and collaboration

Tell me about a time you worked with a difficult team member.

Answers that stay focused on adapting your own communication style land better than ones that catalogue the other person’s flaws.

Describe your role on your most successful team project.

Be specific about your individual contribution among several people — "we" answers make it hard to tell what you actually did.

Tell me about a time you had to influence someone without authority over them.

Look for evidence of building a case with data or a small proof of concept, rather than simply asking repeatedly.

Describe a time you disagreed with a team decision but still committed to it.

This tests whether you can execute well on a call you did not make, which is different from just complying resentfully.

Prioritisation and time management

Tell me about a time you had too much to do and not enough time.

A strong answer states the actual prioritisation criteria used — impact, deadline, dependency — rather than "I just worked harder."

Describe how you handled competing deadlines from two stakeholders.

Look for whether the candidate renegotiated scope or timeline explicitly, rather than silently absorbing the overload.

Tell me about a time you said no to a request.

The interviewer wants the reasoning and how it was communicated, not just that the answer was no.

Describe a time your priorities changed midway through a project.

Good answers separate what was salvaged from what was cut, and why.

Ambiguity and change

Tell me about a time you had to work with unclear requirements.

Strong answers describe how the ambiguity was reduced — a clarifying question, a quick prototype — rather than guessing and hoping.

Describe a time a project’s direction changed after you had already started.

Look for adaptability without resentment, and whether earlier work was salvaged or genuinely wasted.

Tell me about a time you had to adapt to a significant change at work.

Reorganisations, tool changes or new leadership are common; the answer should show a concrete behaviour change, not just "I stayed positive."

Describe a time you took a calculated risk.

The bar is naming the downside you accepted and why the odds still favoured acting, not just that it happened to work out.

How this is worked out

• Twenty-four questions across six themes: conflict, failure, ownership, teamwork, prioritisation, and ambiguity.
• Each entry explains what the interviewer is listening for, so you can shape your own real story to it.
• Use the STAR answer builder on this site to turn a chosen story into the structured version you would say out loud.

Questions people ask

How many stories should I actually prepare?

Five to seven well-developed stories usually cover most of a bank this size, since one good conflict story can answer several differently worded questions.

Is it bad to reuse the same story for two questions in one interview?

It is fine across separate interviews or rounds. Within the same round with the same interviewer, reusing a story back to back looks thin — have a backup ready.

Should my failure story be about something small?

It should be real and have had an actual consequence. A trivial failure signals you are avoiding the question; a catastrophic one with no recovery signals poor judgement — aim for something in between with a clear lesson.