Explore English
Behavioural Interviews for Software Engineers: Think Like the Recruiter
Katie’s interviewer-led guide to decoding questions, building a story bank and backing up your answers with evidence.
Accessibility options
What I listened for as an interviewer
When I interviewed candidates, I wanted to hear what they had done, why they had done it and what happened next. A small project can give you a strong example if you can explain your contribution. Think about coursework, volunteering, personal projects and part-time jobs as well as paid technical work.
Interviewers can read the same question differently. Use the clues in the wording and the job description to decide which part of your experience to bring forward.
DECODE the question
| Step | What to do |
|---|---|
| D · Discover | What skill or judgement might the question be assessing? |
| E · Explain | Give just enough context for a person outside your team. |
| C · Clarify | Say what you were responsible for. |
| O · Outline | Walk through your actions and the reasons for your decisions. |
| D · Demonstrate | Show what changed and how you know. |
| E · Evaluate | Explain what you learnt or would do differently. |
DECODE adds a step before you begin a STARL answer. Identify what the interviewer might be assessing, then tell the story with that point in mind.
Twenty questions and what they might assess
- Tell me about a difficult technical problem you solved. Show how you investigated and chose an approach.
- When did you work successfully as part of a team? Explain how you coordinated with others and what you contributed.
- How did you handle a setback? Show how you adapted when the original plan stopped working.
- When did you take ownership? Explain the responsibility you took on and how you followed through.
- Tell me about a mistake you made. Describe how you dealt with it and what changed in your work afterwards.
- When did you learn a new skill quickly? Show how you chose what to learn and applied it.
- Describe a disagreement with a teammate. Explain both positions, how you listened and how you moved forward.
- Tell me about a challenging deadline. Show what you prioritised, deferred or communicated.
- Describe a difficult bug or production issue. Explain the clues you used to narrow down the cause and verify the fix.
- How did you respond to constructive feedback? Name what you changed and what you observed afterwards.
- When did you explain something technical to a non-technical person? Show how you adapted your explanation to help them understand or make a decision.
- Tell me about a project that went off plan. Explain what changed, who needed to know and what you did next.
- When did you improve a process? Show the original problem, the change you introduced and the practical benefit.
- How did you handle competing priorities? Explain your criteria and what you agreed with others.
- How have you helped a colleague succeed? Describe your support and what it enabled them to do.
- When did you make a decision with limited information? State what you knew, the uncertainty and how you limited the risk.
- Describe a significant change at work. Explain how you adjusted your approach and helped the work continue.
- When did you spot a problem early? Show what made you investigate and how you raised it.
- Tell me about a difficult conversation with a stakeholder. Explain the concern, how you responded and what you agreed.
- When did your recommendation improve a project? Link your reasoning to the outcome for the team or users.
Build a story bank from the result backwards
Pick three real experiences. Use bullet points and begin with Result → Actions → Your role → Situation → Learning. When you speak, give the context first if your listener needs it.
- Result: What changed? How did you know?
- Actions: What did you do, and why? What other option did you consider?
- Your role: What did you own, and where did others contribute?
- Situation: What does someone unfamiliar with the project need to understand?
- Learning: What do you now do differently?
- Competencies: Which two or three skills does this story show?
A measured improvement is useful if you can explain the measurement. Other evidence counts too, such as a repeated issue disappearing, a colleague using your documentation or a customer completing a task they previously struggled with.
One story, three questions
Imagine a slow checkout page. You compared timings, traced repeated requests and changed how the page fetched data. You measured an improvement under the same conditions.
- For problem solving, explain the clues, the alternatives and how you checked the fix.
- For ownership, explain what you took responsibility for and how you followed up.
- For communication, explain how you described the user impact to colleagues and agreed what to address first.
Keep the facts consistent. Change which detail you lead with.
Practise the follow-up
As an interviewer, I sometimes interrupted a polished answer to ask about a decision or a small detail. I wanted to understand how the person had worked. Practise returning to the facts even when the conversation changes direction.
- Tell your story aloud from five bullet points.
- Ask someone to interrupt with “Why did you choose that?”, “What did you personally do?” or “How did you measure success?”
- Answer their question directly. Then add the result if it still helps the listener understand what happened.
- Repeat with a different competency in mind.
Try the mock interview communication challenge for more follow-up questions.
Continue the lesson
Katie Pirsoaga
Contents
Common Behavioural Interview Questions..................................................................................3
What Recruiters Are Really Looking For.......................................................................................4
DECODE Every Behavioural Question............................................................................................5
Build Stories, Not Scripts....................................................................................................................6
Bullet Points Beat Scripts....................................................................................................................6
Preparing Your Story Bank................................................................................................................ 7
The Interviewer IS Trying to Break Your Script...........................................................................8
Story Planner......................................................................................................................................... 9
Katie Pirsoaga
Most candidates prepare answers.
Good candidates prepare evidence and examples.
Excellent candidates understand what is actually being assessed.
Every behavioural interview question is designed to uncover evidence of one or more professional competencies. Your job is not to guess the "right" answer. Your job is to recognise what the recruiter is trying to assess and provide evidence that you have demonstrated that competency.
Common Behavioural Interview Questions
1. Tell me about a time you solved a difficult technical problem.
o Assesses: Problem solving, technical ability, decision making
2. Tell me about a time you worked successfully as part of a team.
o Assesses: Teamwork, collaboration, communication
3. Tell me about a time you faced a challenge or setback. How did you handle it?
o Assesses: Resilience, adaptability, problem solving
4. Tell me about a time you took initiative or ownership of a project or task.
o Assesses: Leadership, responsibility, proactivity
5. Tell me about a mistake you made or a project that didn't go as planned. What did you learn?
o Assesses: Self-awareness, accountability, growth mindset
6. Tell me about a time you learned a new technology or skill quickly.
o Assesses: Learning agility, adaptability, curiosity, self-development
7. Tell me about a time you disagreed with a teammate. How did you resolve the situation?
o Assesses: Communication, conflict resolution, emotional intelligence, professionalism
8. Tell me about a time you worked under pressure or had to meet a challenging deadline.
o Assesses: Prioritisation, time management, decision making, resilience
9. Tell me about a difficult bug or production issue you fixed.
o Assesses: Technical problem solving, analytical thinking, investigation, persistence
10. Tell me about a time you received constructive feedback. What did you do with it?
o Assesses: Self-awareness, coachability, growth mindset, professional maturity
Katie Pirsoaga
11. Tell me about a time you had to explain a technical concept to someone without a technical background.
o Assesses: Communication, business awareness, stakeholder management, empathy
12. Tell me about a time a project didn't go to plan. What happened?
o Assesses: Accountability, reflection, adaptability, ownership
13. Tell me about a time you improved a process or made something work better.
o Assesses: Initiative, innovation, continuous improvement, leadership
14. Tell me about a time you had competing priorities. How did you decide what to do first?
o Assesses: Organisation, prioritisation, judgement, planning
15. Tell me about a time you helped another developer or colleague succeed.
o Assesses: Teamwork, collaboration, mentoring, leadership
16. Tell me about a time you had to make a difficult decision with limited information.
o Assesses: Decision making, critical thinking, judgement, accountability
17. Tell me about a time you had to adapt to a significant change at work.
o Assesses: Adaptability, resilience, learning mindset, flexibility
18. Tell me about a time you identified a problem before anyone else noticed it.
o Assesses: Initiative, ownership, analytical thinking, proactive problem solving
19. Tell me about a time you had to work with a difficult customer or stakeholder.
o Assesses: Communication, professionalism, customer focus, conflict management
20. Tell me about a time you made a recommendation that improved the outcome of a project.
o Assesses: Initiative, business awareness, decision making, leadership
What Recruiters Are Really Looking For
Most behavioural questions assess combinations of the same core competencies.
| Competency | Sample evidence |
|---|---|
| Communication | "I explained a complex technical issue to a non-technical client so they could make an informed decision." |
| Teamwork | "I worked closely with designers and developers to deliver the |
Katie Pirsoaga
project on time."
Problem Solving "I identified the root cause of a production issue and implemented a permanent fix."
Leadership "I coordinated the team during a critical release and delegated tasks effectively."
Ownership "I took responsibility for the issue, even though it wasn't originally assigned to me."
Accountability "I acknowledged my mistake, fixed it quickly and shared what I learned with the team."
Decision Making "I evaluated the available options and selected the approach with the lowest risk."
Adaptability "I learned a new framework quickly so the project could stay on schedule."
Learning Mindset
"I actively sought feedback and used it to improve my work."
Initiative "I noticed an inefficient process and introduced a better way of working."
Conflict Resolution
"I helped resolve a disagreement by focusing on the project's objectives rather than personal opinions."
Resilience "I remained calm under pressure and kept the project moving despite unexpected setbacks."
Business Awareness
"I recommended a solution that reduced costs while still meeting the client's requirements."
Customer Focus "I prioritised features that would provide the greatest value to the end user."
Time Management
"I prioritised competing deadlines and delivered the most critical work first."
Recognise the competency first.
Then choose the best piece of evidence from your experience.
Katie Pirsoaga
DECODE Every Behavioural Question
Before you answer, stop and decode the question.
D – Discover what competency is being assessed.
E – Explain the situation.
C – Clarify your role.
O – Outline your actions.
D – Demonstrate the result.
E – Evaluate what you learned.
This is essentially STARL, but it starts by thinking like the recruiter.
Build Stories, Not Scripts
One story can answer several different questions.
For example:
Story: Production system outage
Could demonstrate:
- Problem solving
- Leadership
- Communication
- Working under pressure
- Decision making
- Collaboration
The story stays the same.
The emphasis changes depending on what is being assessed.
Bullet Points Beat Scripts
Don't write paragraphs.
Katie Pirsoaga
Write prompts.
For every story, note down:
| Prompt | Ask yourself... |
|---|---|
| Result | What changed because of me? |
| Situation | What was happening? Where was I working? What does the interviewer need to know to understand the story? |
| Your Role | What was I responsible for? |
| Key Actions | What did I actually do? |
| Learning | What would I do the same or difef rently next time? |
So, you end up with…..
| Prompt | Example |
|---|---|
| Result | Reduced page load times by 40%. |
| Situation | After a major system upgrade, customers reported that the website had become slow. I was working as a Full Stack Developer on the e-commerce platform. |
| Your Role | I was responsible for investigating the performance issues and implementing a solution. |
| Key Actions | Profiled the application, identifei d inefficient database queries, introduced caching and tested the improvements. |
| Learning | Always measure performance before and after making changes to demonstrate the impact. |
These should be enough to trigger the memory.
Everything else should be a natural conversation.
Remember, the recruiter knows nothing about your project, your company or your team. Give them just enough context to understand the story before explaining what you did.
Katie Pirsoaga
Preparing Your Story Bank
Don't start by thinking about interview questions.
Start by thinking about your career.
Go through your work history and identify the projects, challenges and achievements that demonstrate your skills.
For each story, start with the RESULT.
Why?
Because the result is the evidence.
It's also the part candidates forget most often.
Ask yourself:
- What changed because of me?
- What problem did I solve?
- What did I improve?
- What did I learn?
- What impact did my work have?
Once you know the result, work backwards.
Result Actions Your Role Situation Learning → → → →
By starting with the ending, you'll naturally build stronger stories and you'll never forget the most important part.
Remember, you're not writing interview answers.
You're collecting evidence from your career.
Practise aloud. Say the words. Practise with someone if you can. Behavioural interviews are conversations, not written exams.
The Interviewer IS Trying to Break Your Script
If you've memorised an answer, we'll know. And we'll expect it to fall apart.
As an interviewer, I wasn't trying to break the candidate.
Katie Pirsoaga
I was trying to break their script.
- I'd interrupt.
- I'd ask follow-up questions.
- I'd ask why they made a particular decision.
- I'd ask what happened next.
- I'd ask them to explain one small detail.
Why?
Because anyone can memorise an answer.
I wanted to know whether they had actually lived it.
That's why you should never memorise sentences.
Memorise your experience.
Your experience cannot be broken.
So don't panic if your story gets interrupted or takes a different direction.
That's normal.
Remember...
The interviewer isn't trying to break you. They're trying to break your script.
But this is your lived experience.
You know it.
Trust yourself, answer the question in front of you, and let the conversation flow naturally.
Katie Pirsoaga
Story Planner
Don't start by thinking about interview questions.
Start by thinking about your career.
Go through your work history and identify the projects, challenges and achievements that demonstrate your skills.
Remember, one story can answer several behavioural interview questions.
For each story, start with the RESULT and work backwards.
Result Actions Your Role Situation Learning → → → →
Don't write paragraphs.
Write bullet points.
These are prompts to help you remember your experience, not a script to memorise.
Story 1
Story Title: ________________________________________
Result (Start here!)
Situation
Your Role
Actions
Learning
Competencies this story demonstrates
Communication
Teamwork
Katie Pirsoaga
Problem Solving
Leadership
Ownership
Adaptability
Decision Making
Accountability
Initiative
Learning Mindset
Conflict Resolution
Resilience
Customer Focus
Business Awareness
Time Management
Which questions could this story answer?
Tell me about a difficult technical problem you solved.
Tell me about a time you worked successfully as part of a team.
Tell me about a challenge or setback.
Tell me about a time you took ownership.
Tell me about a mistake you made.
Tell me about a time you worked under pressure.
Tell me about a disagreement with a teammate.
Tell me about a time you learned something new quickly.
Tell me about a time you improved a process.
Other:
Evidence
Katie Pirsoaga
Can you support your story with evidence?
Time saved
Money saved
Bugs reduced
Performance improved
Users helped
Revenue increased
Customer satisfaction improved
Documentation improved
Team efficiency improved
Other:
Follow-up Questions
If I were interviewing you, these are the questions I'd ask to move you away from your script.
Can you answer them confidently?
- Why did you make that decision?
- What alternatives did you consider?
- What exactly was your responsibility?
- What happened next?
- What would you do differently?
- How did you measure success?
- What did you learn?
- How did your team respond?
If you can answer these naturally, you know your story well.
Top Tip
Katie Pirsoaga
Don't try to memorise your answers.
Know your story.
The interviewer isn't trying to break you.
They're trying to break your script.
Your script can fall apart.
Your lived experience can't.
Related resources
Book a session
Practise speaking in a real conversation or prepare for an interview with Katie.
Book a Session →