Practice your software engineer interview out loud.
Behavioral rounds, project deep dives, and the "tell me about a technical decision" question — rehearsed until they sound natural.
You can solve the problem. The hard part is explaining it to a stranger under time pressure.
What Vera actually is
A phone call with someone who is not there. You say the thing out loud, they answer the way a real person would, and you get to do it again — as many times as it takes, with nobody listening.
15 minutes free · no card needed
15 minutes free · no card needed
Not practising doesn’t save you anything.
The ticket, the evening, the weeks of applying — all of it is spent before anyone says a word. The practice is the only cheap part, and the only part that changes how the rest goes.
15 minutes free · no card needed
What she'll actually ask
She asks these the way a real person would, then follows up on whatever you say.
- Walk me through a system you built end to end. What were the tradeoffs?
- Tell me about a time you shipped a bug to production. What did you do?
- Describe a technical decision you disagreed with. How did you handle it?
- How do you decide when code is good enough to ship?
- What is the most difficult debugging problem you have solved?
More about this one
Most software engineer interview prep is silent — LeetCode grinding, reading system design primers, rewriting your resume. But every loop, from the recruiter screen to the final behavioral round, is judged on how you talk. Vera calls your phone and runs the conversational parts of a software engineering interview: your background, your projects, how you handled a production incident, why you made a particular technical tradeoff. You answer out loud, get feedback on structure and specificity, and repeat until your stories stop wandering.
What she listens for
- behavioral round
- system design
- on-call incident
- code review
- technical tradeoffs
- production outage
- STAR method
- hiring loop
“I'd done 200 LeetCode problems and zero practice talking. The first Vera call was humbling — I rambled for five minutes. By the fourth I had it down to ninety seconds.”
Related practice
Common questions
Can Vera do a live coding interview?
No — Vera is a phone call, so there is no shared editor. It covers the behavioral rounds, project deep dives, and the parts of a technical screen where you explain your thinking out loud. Pair it with a coding platform for the editor work.
Will it ask real questions from specific companies?
Vera asks the question types that show up across engineering loops. You can tell it the company, level, and stack, and it will pitch questions at that bar.
How long should a prep call be?
Ten to fifteen minutes covers three or four questions with feedback. Most people get more out of three short calls across a week than one long one.
What if I am bad at it?
Everyone is, on the first one. That is the entire reason it happens here and not there.
What if I do not know what to say?
She asks the first question and follows up on whatever you answer. You never start from a blank page.
What if it is awkward?
It is, for about twenty seconds. Then it is a conversation, and nobody heard the twenty seconds.
Ready to try it?
Your first 15 minutes are free. No card required.