Interview framework
A strong interview answer is not just about what you say. It is also about how you structure your thinking.
Interviewers often ask different types of questions:
- Tell me about something you have done.
- Describe a difficult situation.
- What did you learn from a failure?
- What do you think about a particular strategy?
- What would you do if something went wrong?
Trying to answer all of these using the same structure can make your answers either too long or poorly focused.
Several frameworks can help. The key is to understand when to use each one — and when not to.
 |
1. STAR — The Core Behavioural Framework
STAR is one of the most useful frameworks for behavioural interviews.
S — Situation
Briefly explain the context.
T — Task
What were you responsible for achieving?
A — Action
What did you personally do? Explain your decisions, approach and contribution.
R — Result
What happened? Quantify the outcome wherever possible.
Example
Question:
Tell me about a time you improved a digital customer journey.
Situation:
Our subscription journey had significant customer drop-off.
Task:
I was responsible for identifying the main friction points and improving the experience.
Action:
I analysed the customer journey and analytics, identified key drop-off points, worked with UX and development teams, and prioritised the most important improvements.
Result:
The redesigned journey reduced friction and improved the customer experience and conversion performance.
When to use STAR
Use it when the interviewer asks:
- “Tell me about a time when…”
- “Give me an example of…”
- “Describe a situation where…”
- “Tell me about a difficult project.”
- “Describe a conflict you handled.”
- “Give an example of your leadership.”
- “Tell me about a problem you solved.”
When not to use STAR
Don't force STAR into:
- Factual knowledge questions
- Opinion questions
- Simple questions about your experience
- Hypothetical scenarios
If the interviewer asks: “What is your experience with Google Analytics?”
a direct answer is better than inventing a Situation and Task.
STAR's golden rule
Keep Situation and Task concise.
The interviewer is primarily interested in: What did you do? Why did you do it? What happened?
Also distinguish between “I” and “we.”
“We launched the project” describes the team's work.
“I identified the issue, proposed the solution and coordinated the teams” demonstrates your contribution.
2. STAR-L — Add Learning
STAR-L extends STAR with one additional element: Situation → Task → Action → Result → Learning
The Learning component explains what you learned and how you changed your approach afterward.
Use STAR-L for:
- Failures
- Mistakes
- Difficult experiences
- Lessons learned
- Personal development
- Continuous improvement
Example
Result: The project was eventually delivered successfully, although some requirements had to be reworked.
Learning: I learned that involving key stakeholders earlier significantly reduces late-stage changes, so I now include them during the requirements phase.
Don't use STAR-L when:
There is no meaningful lesson to discuss. Don't add a generic: “The lesson I learned was to communicate better.” just because the framework has an L. The learning should be specific and relevant.
3. CAR — A Concise Version
CAR stands for:
C — Challenge
What needed to be solved or achieved?
A — Action
What did you do?
R — Result
What happened?
CAR is essentially a compressed version of STAR.
Use CAR when:
- You need a concise answer.
- The background is already obvious.
- You want to highlight an achievement or example quickly.
- The interviewer asks for a short example.
Example
Challenge: Website checkout abandonment was high.
Action: I analysed the journey, identified major friction points and worked with UX and development teams to simplify the payment experience.
Result: The revised journey reduced friction and improved completion.
Don't use CAR when:
The interviewer needs significant context to understand the situation. In that case, STAR provides better structure.
4. SOAR — For Complex Challenges
SOAR is useful when the obstacle or complexity is an important part of the story.
S — Situation
What was happening?
O — Obstacle
What made it difficult?
A — Action
How did you respond?
R — Result
What did you achieve?
Use SOAR for:
- Major transformation
- Crisis situations
- Complex projects
- Stakeholder conflict
- Resistance to change
- Difficult organisational situations
Example
Situation: A major digital platform migration was approaching launch.Obstacle: Multiple teams had competing requirements and a tight delivery timeline.
Action: I prioritised requirements, aligned stakeholders, coordinated dependencies and established clear UAT and release checkpoints.
Result: The migration was delivered within the agreed timeline with the critical requirements completed.
Don't use SOAR when:
The situation was straightforward. In most ordinary behavioural questions, STAR is simpler and more natural.
5. PREP — For Opinions & Recommendations
Not every interview question asks about your past. Sometimes the interviewer wants to understand how you think. That's where PREP works well.
P — Point State your position.
R — Reason Explain why.
E — Example Support your position with an example or evidence.
P — Point Reinforce your conclusion.
Example
Question: What makes a successful digital transformation?
Point: Digital transformation should start with business and customer outcomes rather than technology.
Reason: Technology alone doesn't solve process, adoption or customer-experience problems.
Example: A website migration, for example, should be measured through performance, conversion and customer experience — not simply whether the migration was completed.
Point: Successful transformation therefore connects technology, people, processes and measurable business outcomes.
Use PREP for:
- Opinions
- Recommendations
- Strategy questions
- Leadership philosophy
- Digital transformation discussions
- Business decisions
Don't use PREP when:
The interviewer asks: “Tell me about a time when you did this.”
That's a STAR question, because they want evidence from your experience.
6. GROW — For Future Scenarios
Not every question is about the past.
Interviewers may ask:
“What would you do if…?”“How would you handle this situation?”
“What would your approach be?”
For these hypothetical, future-oriented and coaching situations, GROW provides a useful structure.
G - Goal What are you trying to achieve?
R - Reality What is happening now? What are the facts, constraints and challenges?
O - Options What possible approaches could you consider?
W - Way Forward Which approach would you choose, and what would you do next?
Example
Question: What would you do if website conversion suddenly dropped by 30%?
Goal: Restore conversion while identifying the underlying cause.
Reality: First, establish when the decline started and whether it affects all users or specific devices, markets, journeys or traffic sources.
Options: Investigate analytics, technical performance, payment failures, campaign changes, UX issues and recent releases.
Way Forward: Prioritise the highest-impact issue, validate the hypothesis with data, implement the appropriate fix and establish monitoring to confirm recovery.
Use GROW for:
- Hypothetical questions
- Management scenarios
- Coaching situations
- Performance discussions
- Future problem-solving
- Situational leadership questions
Don't use GROW when:
The interviewer asks about something that actually happened to you.
For example: “Tell me about a time when website conversion dropped.”
That's STAR.
7. Which Framework Should I Use?
| Interview question | Best framework |
|---|---|
| “Tell me about a time…” | STAR |
| “Give me an example…” | STAR |
| “What did you learn from a failure?” | STAR-L |
| “What is one of your key achievements?” | CAR |
| “Tell me about a difficult or complex situation.” | SOAR |
| “What do you think about…?” | PREP |
| “What would you recommend?” | PREP |
| “What would you do if…?” | GROW |
| “How would you handle this situation?” | GROW |
8. Practical Answer-Building Template
Knowing the framework is only the first step. The real skill is turning your experience into a concise, evidence-based answer.
Before an interview, build a small library of real examples.
Step 1 — Choose the story
Think of a real situation involving:
- Leadership
- Problem solving
- Conflict
- Customer experience
- Digital transformation
- Innovation
- Failure
- Difficult stakeholders
- Cost or efficiency improvement
- A measurable achievement
Step 2 — Capture the story in five lines
Use this preparation template:
Question / Competency: What might the interviewer ask?
Situation: What was happening?
Task: What was I responsible for?
Action: What did I personally do?
Result: What changed?
Learning: What would I do differently or repeat next time?
Step 3 — Add evidence
Ask: Can I prove the result?
Look for:
- Revenue
- Conversion
- Cost savings
- Time saved
- Customer satisfaction
- NPS / CSAT
- Traffic
- Engagement
- Error reduction
- Project delivery time
- Adoption
- Productivity
- Quality improvement
If exact numbers are confidential, use a credible qualitative result rather than inventing statistics.
A Simple Answer Builder
For a typical behavioural question, prepare your answer like this:
Situation: In [context], we faced [problem/challenge].Task: I was responsible for [objective/responsibility].
Action: I first [action], then [action], and finally [action]. The key decision I made was [decision] because [reason].
Result: This resulted in [outcome], with [evidence/metric] where available.
Learning: I learned [specific lesson], which I now apply by [changed behaviour].
You don't necessarily need to say every label aloud during the interview. The structure is there to help you think.
9. The 60–90 Second Answer Test
A good behavioural answer is usually focused rather than exhaustive.
Before finishing your answer, check:
Context - Did I explain the situation quickly?
Ownership - Is it clear what I personally did?
Decision-making - Did I explain why I chose my approach?
Impact - Did I clearly explain the result?
Evidence - Did I quantify the outcome where possible?
Relevance - Did I actually answer the question?
If the answer is becoming too long, remove background detail before removing the Action and Result.
10. Build an Interview Story Bank
Instead of preparing one answer for every possible question, prepare 8–10 strong stories that can be adapted to different competencies.
| Story type | Possible competencies |
|---|---|
| Major achievement | Leadership, delivery, results |
| Difficult project | Problem solving, resilience |
| Stakeholder conflict | Communication, influence |
| Failure | Accountability, learning |
| Process improvement | Innovation, efficiency |
| Customer problem | Customer focus, UX |
| Team challenge | Leadership, collaboration |
| Tight deadline | Prioritisation, execution |
| Transformation | Change management, strategy |
| Difficult decision | Judgement, decision-making |
One strong story can answer several different questions if you change the emphasis.
For example, the same digital transformation project could demonstrate:
Leadership → how you aligned teams
Problem solving → how you handled obstacles
Stakeholder management → how you resolved conflicts
Results → what the project achieved
Learning → what you would do differently
11. Frameworks You Don't Need to Memorise Separately
You may come across several other variations.
PAR — Problem → Action → Result
Useful, but very similar to CAR.
SAR — Situation → Action → Result
Essentially a simplified STAR. These can be useful shortcuts, but there is little benefit in treating them as completely separate methodologies.
5W1H — Who, What, When, Where, Why, How
5W1H is excellent for:
- Investigation
- Requirements gathering
- Business analysis
- Problem definition
But it is primarily an analysis and information-gathering technique, rather than an interview-answer framework.
12. The Frameworks Worth Mastering
You don't need to memorise dozens of interview frameworks. For a senior management, Digital Manager or Digital Transformation interview, four core frameworks provide excellent coverage:
STAR - Prove your experience
STAR-L - Demonstrate maturity and learning
PREP - Demonstrate strategic and structured thinking
GROW - Demonstrate leadership and problem-solving
Then use:
CAR when you need a concise example.
SOAR when the complexity or obstacle is central to the story.
13. The Most Important Principle
Don't choose the framework first.
First ask: What is the interviewer trying to assess?
Then choose the structure that best demonstrates it.
A strong answer should make these elements clear:
Context → Responsibility → Decision-making → Action → Impact
And wherever possible:
Add evidence. Numbers, percentages, revenue impact, conversion improvement, cost reduction, time saved, customer satisfaction or other measurable outcomes make your answer much more credible.
The Simple Mental Model
Past experience → STAR
Past experience + learning → STAR-L
Concise example → CAR
Complex challenge → SOAR
Opinion / recommendation → PREP
Future / hypothetical scenario → GROW
The goal isn't to sound like you're following a framework. The goal is to make your answer structured, relevant, credible and easy for the interviewer to remember.
Comments
Post a Comment