Skip to content
Vera
Interview Prep

Walk through the incident like you are in the room.

Postmortems, on-call judgment, and reliability tradeoffs — practiced out loud.

Incident stories are the whole interview, and nobody rehearses telling them.

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.

1She calls youA real phone call, about ten seconds after you tap. Lock screen, headphones, car — wherever you take calls.
2She plays the other personNot a coach reading tips. DevOps & SRE Interview Prep, with someone on the other end who answers back.
3She pushes when you are vagueFollow-up questions, interruptions when you ramble, and a straight read at the end on what landed.
Practice Incident Rounds

15 minutes free · no card needed

Practice Incident Rounds

15 minutes free · no card needed

“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 first 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.

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.

Practice Incident Rounds

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.

  1. Walk me through the worst incident you have been on call for.
  2. How do you decide whether to roll back or fix forward?
  3. Tell me about an alert that was firing constantly. What did you do about it?
  4. How do you set an SLO when the business wants 100%?
  5. Describe a change you made that caused an outage.
More about this one

SRE and DevOps loops revolve around incident narration: what alerted, what you checked, what you got wrong, what changed afterward. Told badly, a serious outage sounds like chaos; told well, it demonstrates exactly the judgment the role needs. Vera runs on-call and reliability rounds over the phone, pushing for the sequence of your reasoning rather than the resolution, and flags when a story skips straight to the fix.

What she listens for

Timeline disciplineDetection, hypothesis, mitigation, fix — in order, not jumbled.
Blameless framingHow you describe the person who shipped the change matters more than the change.
Follow-throughInterviewers wait for what changed structurally afterward.
  • postmortem
  • SLO and error budget
  • on-call rotation
  • rollback
  • alert fatigue
  • incident command
  • blast radius
  • toil reduction
“I told my biggest outage story out of order every single time until Vera stopped me at the same point three calls running.”
Greg P., Site Reliability Engineer

Related practice

Common questions

Is this useful for platform engineering roles?

Yes — the incident and reliability rounds are near-identical, and the tradeoff questions transfer directly.

Can Vera play an incident commander?

It can role-play the interviewer running the round. It does not simulate a live incident with real telemetry.

How many stories should I prepare?

Three incidents with genuinely different failure modes covers most loops. Practice each once and you will find the weak one fast.

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.