Top 20 Behavioural Interview Questions
Browse 20 real-world technical and behavioral interview questions about Behavioural. Review scenarios, edge cases, and architectural best practices.
How do you use AI tools in your daily work, and when do you refuse to trust an LLM's answer?
Describe your use of AI tools by task, each with its check: reading cited lines, running code, confirming APIs against the docs for your version. Refuse any answer you cannot check cheaply or that is costly to get wrong, keep restricted data out of unapproved tools, and back it with one real catch.
Tell me about something you built. Everything you have built so far was for coursework.
Pick one coursework project, say plainly that it was an assignment and what the brief fixed, then spend the answer on the decisions you made inside that brief, the problem that cost you the most time and what you would change. Owned decisions and honest scope matter more than how impressive the project sounds.
You are asked to bring a real piece of your own work and talk through it. What do you choose, and what do you have to be ready to admit?
Choose a work sample with real decisions in it that you still understand line by line and are allowed to share. Be ready to admit which parts were other people's or a tool's, what is wrong with it, and what you would change, because the interviewer can open any file and ask why it is there.
You are asked to design a product that does not exist, and the setup is missing details you would need in real life. Do you point that out?
Yes, once and briefly, with an assumption attached. In a hypothetical product exercise the scored move is what follows. Separate gaps that change the design from gaps that do not, choose assumptions that keep the problem hard, write them where both of you can see them, and say which parts of the design depend on each.
Tell me about a time you had to deliver with unclear requirements or a deadline you did not believe in.
Show that you made the ambiguity smaller before you started coding, that you wrote down the assumptions you were proceeding on, and - for the deadline half - that you renegotiated scope early with evidence rather than absorbing the pressure silently and missing the date.
Tell me about a time you broke something in production. What happened?
Own the change that caused it, walk the timeline from detection to recovery in real minutes, separate your mistake from the system that let it through, and say which fix is still in place today. Interviewers score the honesty of the timeline before the cleverness of the fix.
Tell me about a time you fixed something nobody had asked you to fix.
Pick unasked work that solved a problem other people were feeling, show that you sized it before starting and told someone you were doing it, and be able to say what you chose not to fix — unsanctioned effort only reads as initiative when it was also disciplined. Use this ownership answer to show the decision, trade-off, and evidence rather than a memorised definition.
Tell me about a time you had to give someone difficult feedback.
Describe feedback you delivered directly to the person, in words you can repeat, about behaviour that was affecting the work, and say what changed afterwards. The score turns on whether you said the hard sentence out loud or softened it until it disappeared. It also connects leadership to the point an interviewer is testing.
Do you have any questions for us?
Ask two or three questions that only someone who has done the job would think to ask, aimed at the specific interviewer in front of you, and treat the answers as real information about whether you want the role.
Tell me about a time you had far more work than you could deliver. How did you handle it?
Name the competing demands, say what you dropped or deferred and who agreed to it, and describe how you told the people whose work was affected. Interviewers listen for a decision made in the open, not for evidence that you absorbed the overload quietly.
How do you prepare stories for a behavioural round without ending up sounding rehearsed?
Prepare an inventory of six to eight real experiences rather than a script per question, check it against the competencies the loop will grade, hold each one as facts deep enough to survive three rounds of probing, and re-angle a story instead of retelling it.
Tell me about a time you got something adopted when you had no authority to mandate it.
Pick a case where someone competent genuinely disagreed with you, and spend the answer on what you did to change their mind - the evidence you gathered, the concession you made, the person you convinced first - rather than on how right you turned out to be.
What is the hardest piece of feedback you have received, and what did you do with it?
Choose feedback about your effect on other people rather than a skills gap, quote it close to how it was said, describe the reaction you actually had before the acceptance, and show a specific behavioural change that the person who gave it could confirm.
What is the piece of work you are proudest of, and why that one?
Choose work whose value you can state in the terms the business used, explain why you are proud of it in a way that reveals your standards, and be ready to be precise about which parts were yours. The choice itself is the signal the interviewer is reading.
There is a gap of just over a year on your CV. What were you doing?
Give the dates, give the reason in one sentence, say what ended it, and stop. The interviewer is checking that your account matches the record and that you can discuss it without discomfort, not whether the reason was impressive.
Walk me through your career.
Answer with the reasoning behind three or four choices rather than a chronology of employers, spend most of the time on the two most recent roles, and give a reason for each move that a manager would find rational rather than a reason that flatters you.
What do you still not know about this role that would matter to your decision?
Name the one or two things that would genuinely change your answer if you had an offer, ask them of the person best placed to answer, and say why they matter to you. Vagueness here reads as indifference to the job rather than as politeness.
What is the STAR method, and why do interviewers structure behavioural rounds around it?
STAR is a note-taking shape before it is an answer shape - Situation, Task, Action, Result - and interviewers rely on it because it forces the two things a rubric needs: what you personally did, and what changed as a result.
Tell me about a time you had to work closely with someone you found difficult.
Pick a real working conflict, describe the other person as a colleague with reasons rather than a villain, say what you changed in your own behaviour, and give the outcome as it landed. Interviewers grade the fairness of the account more than the resolution. It also connects collaboration to the point an interviewer is testing.
You have told me what the team did. What did you personally do?
Separate the team's work from your own by naming the decisions you made, the artefacts you produced and the conversations you had. This is the follow-up that most behavioural stories fail, and the failure is usually a habit of speech rather than dishonesty. Use this star method answer to show the decision, trade-off, and evidence rather than a memorised definition.