Behavioral Questions
“Tell Me About Yourself”
The opening question in almost every interview. A well-rehearsed answer sets the tone — use the Present → Past → Future structure.
Present (2–3 sentences)
Current role: what you do, what you own, what you've built.
Pick 1–2 recent achievements that are relevant to this role.
Past (2–3 sentences)
Relevant background that explains how you got here.
Highlight the thread connecting your experience to this role.
Future (1–2 sentences)
Why this role / company specifically.
What you want to grow toward.Example structure:
"Currently I'm [role] at [company], where I own [area] and recently
[1 relevant achievement].
Before that I [brief background thread that leads here].
I'm looking for [what you want] because [genuine reason tied to
the company/role], and I'm particularly excited about [specific
thing that shows you did your homework]."When to use: Always — it’s the guaranteed opener.
Interview tip: Keep it to 90 seconds or less. End with a forward-looking statement that invites the interviewer to ask a follow-up question. Do not read your CV chronologically.
STAR Framework
The standard structure for answering behavioural and situational interview questions clearly and concisely.
S — Situation Set the scene. Where, when, what was the context?
T — Task What was your specific responsibility or goal?
A — Action What did YOU do? Be specific. Use "I", not "we".
R — Result What was the outcome? Quantify if possible.When to use: Any “Tell me about a time…” or “Give me an example of…” question.
Interview tip: Keep Situation and Task brief (20%). Spend most of your time on Action (60%) and Result (20%). Interviewers want to understand your thinking and impact, not the backstory.
SOAR Framework (Conflict Variant)
A variation of STAR optimised for questions about obstacles, conflict, or failure.
S — Situation What was the context?
O — Obstacle What went wrong or what challenge did you face?
A — Action How did you respond? What choices did you make?
R — Result What was the outcome, including what you learned?When to use: “Tell me about a time you failed”, “Describe a conflict with a teammate”, “What would you do differently?”
Interview tip: Do not skip the “what you learned” part of Result — growth mindset signals are important in senior interviews.
Behavioural Question Category Map
Prepare at least one strong story per category. A single story can often cover multiple categories.
Ownership & Initiative
→ "Tell me about a time you took ownership of something outside your role."
→ "Describe a time you identified and fixed a problem no one asked you to."
Conflict & Collaboration
→ "Tell me about a disagreement with a colleague. How did you resolve it?"
→ "How do you handle working with someone difficult?"
Failure & Learning
→ "Tell me about your biggest professional failure."
→ "What would you do differently in a past project?"
Ambiguity & Decision-Making
→ "Describe a time you had to make a decision with incomplete information."
→ "How do you handle shifting priorities?"
Influence Without Authority
→ "Tell me about a time you convinced others to adopt your idea."
→ "How have you driven change in an organisation?"
Technical Leadership
→ "Describe a technically complex problem you solved."
→ "Tell me about a system you designed or significantly improved."Communication: BLUF (Bottom Line Up Front)
Leads with the conclusion, then supports it with detail. Prevents burying the key point at the end.
❌ Without BLUF:
"We looked at three options. The first was X, which had these trade-offs...
the second was Y... after all that analysis, we decided to go with Z."
✅ With BLUF:
"We're going with Z. Here's why: [reason]. We considered X and Y but
ruled them out because [brief reason]."When to use: Status updates, design proposals, answering “what do you recommend?”, escalation emails.
Explaining Technical Concepts: The Feynman Technique
1. Name the concept simply.
2. Explain it as if to a non-expert (no jargon).
3. Identify gaps — where does your explanation break down?
4. Simplify or use an analogy to fill those gaps.When to use: “Explain X to a non-technical stakeholder”, “How would you explain this to a new engineer?”
Example analogy bank:
Load balancer → A traffic cop directing cars to open lanes.
Cache → A sticky note on your desk vs. walking to the filing cabinet.
Message queue → A to-do tray — producers drop tasks, consumers pick them up.
Container → A shipping container: runs anywhere, same contents regardless of ship.
Service mesh → A phone operator switchboard between microservices.Questions to Ask Interviewers
“Do you have any questions for us?” is not a formality — it is another evaluation. Good questions signal curiosity, preparation, and seniority.
About the role and team:
→ What does success look like for this role in the first 90 days?
→ What's the biggest challenge the team is facing right now?
→ How does the team handle on-call and incident response?
→ What's the split between new feature work and maintenance/tech debt?About technical culture:
→ How do engineering decisions get made — top-down or within the team?
→ How does the team approach code review and technical standards?
→ What does the deployment pipeline look like? How often do you ship?
→ How do you handle post-mortems after incidents?About growth:
→ What growth paths do engineers typically take here — IC or management?
→ How does the company invest in engineering development (conferences, learning)?
→ Can you tell me about someone who has grown significantly in this team?About decision-making:
→ What's a recent technical decision the team made that you're proud of?
→ Is there a decision made in the last year you'd make differently now?
→ How much autonomy does this role have over technical choices?When to use: Every interview — prepare 3–5 questions and rank them. If the interview runs short on time, lead with your highest-priority question.
Interview tip: Avoid questions answerable by reading the job description or company website. Tailor at least one question to something specific mentioned earlier in the interview — it demonstrates active listening.