The short answer
A behavioural mock interview (spelled behavioral in American English) is a practice round where an interviewer asks about real situations from your work and probes each story with follow-ups. On Revvox it is 60 minutes on video with an experienced engineer, marked 1 to 5 on structure, ownership, collaboration, impact and self-awareness, with a written report within 24 hours. One round costs ₹2,499 ($32).
What a behavioural round tests
Technical rounds show whether you can do the work. The behavioural round, often run by the hiring manager, decides whether the team wants to work with you and at what level. Interviewers listen for what you did yourself, how you handled people and pressure, and whether you learn from what goes wrong.
Level changes the bar more than people expect. A junior engineer can tell good stories about their own tasks. A senior engineer is expected to show influence beyond their team: changing a plan, mentoring, handling a disagreement with a manager, or owning an outage they did not cause. Many senior candidates pass every coding round and are down-levelled here, because their stories describe what the team did rather than what they did.
How it is scored
After the 60-minute round, the interviewer marks each line below 1 to 5 in your written report, due within 24 hours, with notes on what you said and wrote behind each mark. The verdict is one of Strong hire, Hire, Lean hire, Lean no hire or No hire.
| Skill (1 to 5) | What the interviewer looks for |
|---|---|
| Structure | Each answer has a clear situation, your actions, a result and a lesson, told in about two minutes. |
| Ownership | You show what you decided and did yourself, including the parts that went badly. |
| Collaboration | You describe others fairly, handle disagreement with respect and bring people with you. |
| Impact | Results are concrete, with numbers where they exist, and sized to the level you are interviewing for. |
| Self-awareness | You say what you would do differently and show that you changed how you work. |
Behavioural practice questions
Written by us in the style of real behavioural and hiring manager rounds. In a mock, expect three to five of these, each followed by deeper questions about your answer.
- Tell me about a technical decision you pushed for that others disagreed with.How you made the case, whether you listened, and what happened, including if you were wrong.
- Describe a time a release or project you owned went badly.Honest ownership, what you did in the moment, and the change you made afterwards.
- Tell me about a time you had to deliver with much less time than you needed.How you cut scope, who you told and when, and the quality of the trade-off.
- Describe a time you helped a colleague get better at something.Specific help, patience, and a visible change in the other person.
- Tell me about feedback you received that was hard to hear.Whether you acted on it, and how your work changed.
- Tell me about something you improved without anyone asking you to.Initiative, judgement about what mattered, and a result others noticed.
- Why are you leaving your current role, and why this one?A positive, specific answer that links your goals to the job, without criticising your employer.
How the round runs
- Five minutes: your story. A short version of your career and why this role. The interviewer listens for a clear thread.
- Forty minutes: four or five questions. Each one asks for a real situation. The follow-ups go deeper: what did you do, what did others think, what would you change.
- Five minutes: your questions. Good questions for the hiring manager count. We practise those too.
- Ten minutes: feedback out loud. Which stories worked and which to replace, while it is fresh. The written report follows within 24 hours.
How to prepare your stories
Build a bank of six to eight real stories before you practise questions. Most questions can be answered from a good bank, and a story told the second time is always better than the first.
- Cover the common themes: a hard technical decision, a conflict, a failure, a deadline at risk, helping someone else grow, and something you changed without being asked.
- Use a simple shape: the situation in two sentences, what you did in most of the time, the result with a number if there is one, and what you learned.
- Say "I" for what you did and "we" for what the team did. Interviewers notice the difference.
- Keep each story to about two minutes before the follow-ups. Long set-ups lose the interviewer.
- Prepare an honest failure with a real cost. A failure that is secretly a success does not score.
Common mistakes
- Answering in general terms ("I usually...") instead of telling one real story.
- Spending most of the answer on context and almost none on your own actions.
- Blaming a colleague or a manager in a conflict story.
- Giving no result, or a result with no link to what you did.
- Telling the same story for every question because it is the only one ready.