Interview at the senior bar, not the mid bar.
Practice the scope, influence, and judgment stories that separate a senior offer from a downlevel.
Most downlevels are not skill gaps. They are stories told at the wrong altitude.
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.
- Tell me about a technical direction you set that the team initially disagreed with.
- Describe a time you made a call with incomplete information. What did you get wrong?
- How have you grown other engineers on your team?
- Walk me through the largest scope you have personally owned.
- Tell me about a project you killed or descoped. Who did you have to convince?
More about this one
Senior software engineer interviews are calibrated on scope and influence, not correctness. The same project can read as mid-level or staff-adjacent depending on how you frame the ambiguity you absorbed and the people you moved. Vera runs the senior loop over the phone: cross-team conflict, technical direction you set, a decision you made with incomplete information, mentoring. It flags when you are describing execution where the interviewer needs to hear judgment — the most common reason strong engineers get downleveled.
What she listens for
- scope and influence
- downlevel
- staff engineer
- technical direction
- cross-team dependency
- level calibration
- promotion packet
- design review
“Vera kept asking 'and what did you decide?' until I realized every story I had was about execution. I rebuilt three of them before the onsite and got the senior offer.”
Related practice
Common questions
What actually determines level in an engineering interview?
Usually scope of ownership, ambiguity you handled without direction, and influence on people outside your immediate team. Vera prompts specifically on those three.
I was told I interview well but keep getting downleveled. Why?
A common pattern is answering at task altitude — what you built rather than what you decided and why. Practicing out loud is the fastest way to hear yourself doing it.
Can I practice for staff-level interviews?
Yes. Tell Vera the level and it will push harder on org-wide influence and long-horizon technical bets.
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.