A mock behavioral interview that asks the second question.
A mock behavioral interview is only useful if someone pushes back. Remy asks for a story, listens, and follows up on the part you glossed over — what you did, what happened, and what you would change.
What a behavioral interview tests
Your part, not the team’s
Interviewers listen for "I". What did you decide, and what would not have happened without you?
A result you can name
Stories that end with what changed — a number, a launch, a decision — instead of trailing off.
Honesty under follow-up
The second and third question test whether the story holds up. Real detail survives; rehearsed lines do not.
She listens to the whole story, then asks about your part.
Stories, out loud
A 30 minute round usually covers three questions, each with its own follow-ups.
The follow-up you were avoiding
"What did you do when they still said no?" She moves on when the answer is good enough, not before.
Your words, quoted
The report quotes the sentence where the story slipped and suggests how to say it next time.
12 behavioral questions you can practise
Every question in the Interview Hero library for this round, with its level and topics. Pick any of them when you build a round.
Behavioral
12 questionsOwnership end to end
Tell me about a project or system you owned end to end.
Standardownershipaccountabilityend to end deliveryDisagree and commit
Describe a time you disagreed with a technical or product decision.
Standarddisagree and commitconflictinfluenceCustomer impact
Tell me about a time you improved something meaningful for a customer.
Standardcustomer impactuser researchproduct senseFailure and recovery
Tell me about a time you failed or a project that went badly.
StandardfailuregrowthpostmortemWorking through ambiguity
Describe a time you worked on a problem with unclear requirements or shifting goals.
Hardambiguityproblem framingstakeholder alignmentDeep dive on a hard project
Pick the most technically complex project you have worked on.
Hardtechnical deptharchitecturetradeoffsInfluence without authority
Tell me about a time you changed how another team or a more senior person worked, even though you did not own their roadmap.
Standardinfluencestakeholder managementcross teamPrioritization and saying no
Walk me through a time you had more requests than capacity and had to choose.
Standardprioritizationtradeoffsstakeholder managementGrowing engineers through mentoring
Tell me about someone you mentored on your team.
StandardmentoringcoachingfeedbackLearning something new under pressure
Describe a time you had to become productive in an unfamiliar area quickly.
StandardlearningadaptabilitygrowthCross-team conflict
Tell me about a conflict where another team's incentives genuinely differed from yours.
Hardconflictcross teamstakeholder managementQuality under delivery pressure
Describe a time when a deadline pushed you to compromise on quality.
Harddeliveryqualityrisk management
Your own words, and what to say next time.
Say the trade-off before you start coding.
“I'll just use a hash map and sort it, it's probably fine.”11:40 · right before you started typing
“A heap keeps this at n log k. Sorting everything is simpler — I'll start there and say why it's fine for this input.”
About the behavioral round
Should I use the STAR format?
It is a good default: situation, task, action, result. If your story leaves one of the four out, Remy asks a short follow-up for the missing part.
Can I reuse one story for several questions?
You can, but a loop usually has several interviewers. Have a few stories ready so each question gets a fitting one.
Will Remy judge whether my story is true?
No. She asks for the detail a real interviewer would, which is where invented or vague stories tend to fall apart.
More ways to practise
Try a behavioral round with Remy.
Your first two practices are free. No card needed.
Already have an account? Sign in