Interview rubric
How Behavioural Interviews Are Scored: Rubric by Level (2026)
A behavioural interview is scored on 6 dimensions: situation and ownership (20%), actions and judgement (20%), impact and evidence (15%), reflection and learning (10%), answers the competency asked (15%), communication (20%). Each is rated 1 to 4 against anchors that rise with the level. At mid level, an outstanding score on situation and ownership means: "Tells a project story with real ambiguity, where they took ownership nobody assigned."
The dimensions and their weights
| Dimension | Weight | Solid (3) at mid level |
|---|---|---|
| Situation and ownership | 20% | Tells a specific story about owning a feature or project end to end, personal role clear. |
| Actions and judgement | 20% | Describes what they did, the alternatives considered and why they chose as they did. |
| Communication | 20% | Gives a structured, concise answer to the actual question, signposting the parts. |
| Impact and evidence | 15% | States the project outcome with metrics and links it to the user or business goal. |
| Answers the competency asked | 15% | Picks a story that clearly demonstrates the competency or principle asked. |
| Reflection and learning | 10% | Owns a specific mistake and explains what they would do differently. |
What changes between levels
On situation and ownership, the heaviest dimension, an outstanding mid-level answer "tells a project story with real ambiguity, where they took ownership nobody assigned", while an outstanding senior answer "tells a multi-team story where they defined the problem and took ownership across team lines". The same answer can score 4 at mid level and 2 at senior: senior candidates are expected to raise things unprompted that mid-level candidates may be asked about.
Every score, at every level
Situation and ownership (20%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | Gives a hypothetical or generic answer with no real situation from school, projects or internships. | Names a real project or club situation but cannot say what they personally did. | Tells a specific story from a course project, internship or club with a clear personal role. | Tells a specific story where they owned a clear piece, such as leading a team project module. |
| Junior | Gives a hypothetical answer or a story with no identifiable personal role. | Tells a real story but says "we" throughout until asked what they did. | Tells a specific story about their own task with a clear personal "I". | Tells a specific story about owning a whole feature, with their role clear without probing. |
| Mid-level | Gives a hypothetical answer or a story with no identifiable personal role. | Tells a task-level story, or needs probing to separate their part from the team's. | Tells a specific story about owning a feature or project end to end, personal role clear. | Tells a project story with real ambiguity, where they took ownership nobody assigned. |
| Senior | Gives a hypothetical answer or a story with no identifiable personal role. | Tells a single-feature story with no ambiguity or cross-team element. | Tells a multi-team or ambiguous project story, clearly owning direction, not just tasks. | Tells a multi-team story where they defined the problem and took ownership across team lines. |
| Staff | Gives a hypothetical answer or a story with no identifiable personal role. | Tells a project-level story confined to one team. | Tells an org-level story where they set direction or resolved conflicting priorities across teams. | Tells an org-level story where they identified an unowned problem and changed how several teams work. |
Actions and judgement (20%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | Cannot describe any action they took, only what happened around them. | Describes actions vaguely, such as "worked hard", without concrete steps. | Describes concrete steps they took and gives a simple reason for each. | Describes concrete steps and one alternative they considered, with a reason for their choice. |
| Junior | Cannot describe any action they took, only what happened around them. | Describes actions only when probed, with no reasoning behind them. | Describes concrete actions they took and explains why. | Describes their actions, an alternative they rejected and why their choice was better. |
| Mid-level | Cannot describe any action they took, only what happened around them. | Describes actions but cannot explain the reasoning or alternatives when asked. | Describes what they did, the alternatives considered and why they chose as they did. | Explains actions and trade-offs, including a difficult call they made under uncertainty. |
| Senior | Cannot describe any action they took, only what happened around them. | Describes sound actions but only within their own work, with no influence on others. | Describes judgement calls under ambiguity, including how they influenced people they did not manage. | Describes weighing competing stakeholder needs and making a call that held up, with reasons. |
| Staff | Cannot describe any action they took, only what happened around them. | Describes good judgement within one team but none at the cross-team level. | Describes decisions that set direction across teams, with trade-offs and how they gained agreement. | Describes a hard org-level trade-off, the alternatives weighed and how they brought sceptics along. |
Impact and evidence (15%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | States no outcome, or the story stops before anything happened. | States a vague outcome such as "it went well" with no detail. | States a concrete outcome, such as a grade, a demo shipped or users of a project. | States a concrete outcome with a number, such as load time cut or event attendance doubled. |
| Junior | States no outcome, or the story stops before anything happened. | States a vague outcome with no number or concrete result. | States a concrete result of their task, with a number where one exists. | States a measured result and links it to a user or team benefit. |
| Mid-level | States no outcome, or the story stops before anything happened. | States outcomes vaguely, without numbers even when asked. | States the project outcome with metrics and links it to the user or business goal. | States metrics, explains how they were measured and what changed because of them. |
| Senior | States no outcome, or the story stops before anything happened. | States metrics for their own work only, not the wider project outcome. | States multi-team outcomes with metrics and ties them to business results. | States business impact with metrics and explains the lasting change it caused beyond the project. |
| Staff | States no outcome, or the story stops before anything happened. | States project-level metrics with no wider organisational effect. | States org-level impact with metrics, such as cost, revenue or reliability across teams. | States org-level impact with metrics and a durable change in how the organisation operates. |
Reflection and learning (10%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | Says they would change nothing, or blames others for every problem. | Gives a generic lesson such as "communication is important" when asked. | Names a specific thing they learned and would do differently next time. | Names a specific lesson and shows how they applied it in a later project or internship. |
| Junior | Says they would change nothing, or blames others for every problem. | Gives a generic lesson only when asked. | Names a specific mistake or lesson and what they would do differently. | Names a specific lesson unprompted and describes applying it since. |
| Mid-level | Says they would change nothing, or blames others for every problem. | Gives a generic or self-flattering lesson only when asked. | Owns a specific mistake and explains what they would do differently. | Owns a mistake unprompted and describes a habit or process they changed because of it. |
| Senior | Says they would change nothing, or blames others for every problem. | Reflects on their own execution only, not on judgement or approach. | Reflects on a judgement call they got wrong and how their approach changed. | Reflects candidly on a judgement error and a change they drove in their team as a result. |
| Staff | Says they would change nothing, or blames others for every problem. | Reflects on their own work but not on wider decisions or their effect on others. | Reflects on an org-level decision, what they would do differently and why. | Reflects on an org-level misjudgement and the mechanism they built so others avoid it. |
Answers the competency asked (15%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | Tells a story unrelated to the question, such as a success story for a failure question. | Tells a story that only loosely touches the competency asked. | Picks a school, project or club story that clearly shows the competency asked. | Picks a well-fitting story and names how it shows the competency without being asked. |
| Junior | Tells a story unrelated to the competency asked. | Tells a story that only loosely fits the competency asked. | Picks a story that clearly shows the competency or principle asked. | Picks a strong-fitting story and draws out the competency explicitly. |
| Mid-level | Tells a story unrelated to the competency asked. | Tells a story that fits loosely, or covers a different competency than the one asked. | Picks a story that clearly demonstrates the competency or principle asked. | Picks a story that demonstrates the competency strongly and handles follow-up probes on it. |
| Senior | Tells a story unrelated to the competency asked. | Shows the competency, but only at a scale below the target level. | Shows the competency at multi-team scope and survives follow-up probes. | Shows the competency strongly at multi-team scope, with a second story ready when asked. |
| Staff | Tells a story unrelated to the competency asked. | Shows the competency only at single-team scope. | Shows the competency at org scope and survives probing on their personal part. | Shows the competency at org scope convincingly, with fresh examples for every follow-up. |
Communication (20%)
| Level | 1 · Poor | 2 · Borderline | 3 · Solid | 4 · Outstanding |
|---|---|---|---|---|
| Intern / new grad | Rambles without a clear point, or gives one-line answers that need constant probing. | Gets to the point only after several follow-up questions. | Tells the story in a clear order, situation to result, within a few minutes. | Tells a clear, concise story in STAR order and answers follow-ups directly. |
| Junior | Rambles without a clear point, or gives one-line answers that need constant probing. | Tells the story out of order and needs steering back to the question. | Tells a structured, concise story that answers the question asked. | Leads with the headline, tells a tight story and answers follow-ups crisply. |
| Mid-level | Rambles without a clear point, or gives one-line answers that need constant probing. | Answers the question but with long tangents or too much background. | Gives a structured, concise answer to the actual question, signposting the parts. | Leads with the headline, adjusts detail to the interviewer's interest and stays on time. |
| Senior | Rambles without a clear point, or gives one-line answers that need constant probing. | Answers clearly but spends too long on context and too little on their decisions. | Answers top-down and concisely, focusing on decisions and impact, not background. | Answers top-down, anticipates follow-ups and handles pushback calmly with evidence. |
| Staff | Rambles without a clear point, or gives one-line answers that need constant probing. | Answers clearly but cannot summarise a complex org story briefly. | Summarises complex org stories crisply and goes deeper only where asked. | Summarises crisply, frames the stakes for each audience and handles challenge with ease. |
Company-specific signals
Get scored against this rubric
Thita's AI interviewer runs a live behavioural round and scores you against exactly this rubric, dimension by dimension, for the level you choose.
Practise a behavioural roundWhere this rubric comes from
These rubrics are researched: they follow the scoring methods big-tech companies describe publicly (behaviourally anchored ratings, bar raisers, leadership principles, named interview signals) and how their rounds are commonly run. No company publishes its actual scoring sheet, so the level-by-level wording is our own synthesis. It is the same rubric our AI interviewer scores every mock against.
Questions, answered
- How is a behavioural interview scored?
- A behavioural interview is scored on 6 dimensions: situation and ownership (20%), actions and judgement (20%), impact and evidence (15%), reflection and learning (10%), answers the competency asked (15%), communication (20%). Each is rated 1 to 4 against anchors that rise with the level. At mid level, an outstanding score on situation and ownership means: "Tells a project story with real ambiguity, where they took ownership nobody assigned."
- What is the difference between a mid-level and a senior behavioural answer?
- On situation and ownership, the heaviest dimension, an outstanding mid-level answer "tells a project story with real ambiguity, where they took ownership nobody assigned", while an outstanding senior answer "tells a multi-team story where they defined the problem and took ownership across team lines". The same answer can score 4 at mid level and 2 at senior: senior candidates are expected to raise things unprompted that mid-level candidates may be asked about.
- What does a score of 3 mean?
- Scores are relative to the level you are interviewing for. A 3 means solid for that level: the bar is met without help on the key points. A 4 means the candidate also raised the important points unprompted. A 2 usually means the interviewer had to lead the candidate to them.
- Is this the official rubric used by Google, Meta or Amazon?
- These rubrics are researched: they follow the scoring methods big-tech companies describe publicly (behaviourally anchored ratings, bar raisers, leadership principles, named interview signals) and how their rounds are commonly run. No company publishes its actual scoring sheet, so the level-by-level wording is our own synthesis. It is the same rubric our AI interviewer scores every mock against.