Skip to content
Vera
Interview Prep

System design is a talking exam.

Practice narrating a design, defending tradeoffs, and handling the follow-up that changes everything.

You can draw the diagram. The score comes from what you say while drawing it.

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. System Design Interview Practice, 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 System Design

15 minutes free · no card needed

Practice System Design

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 System Design

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. Design a URL shortener. Start by telling me what you need to know.
  2. How would you scale this to ten times the traffic?
  3. What breaks first in your design, and how would you know?
  4. Now assume writes must be strongly consistent. What changes?
  5. Where would you put a cache, and what does it cost you?
More about this one

System design interviews are scored on communication as much as architecture: how you clarify requirements, narrate tradeoffs, and respond when the interviewer changes a constraint halfway through. Studying design primers builds the vocabulary and none of the delivery. Vera runs the round by voice with no whiteboard, which forces the verbal structure the interviewer is actually grading, then pushes with the follow-up constraints that reveal whether you understood your own design.

What she listens for

Requirements firstJumping to components before establishing scale and constraints.
Tradeoff languageNaming what a choice costs, not only what it buys.
Recovery under changeWhether a new constraint makes you adapt or restart.
  • load balancing
  • sharding
  • consistency model
  • caching strategy
  • queue backpressure
  • read replica
  • capacity estimation
  • failure mode
“No whiteboard was the point. If I could not say it clearly, I did not actually understand it.”
Victor H., Software Engineer

Related practice

Common questions

Is voice-only really useful for system design?

Surprisingly yes. Interviewers grade the narration, and removing the diagram exposes gaps you can otherwise draw around.

Which prompts does it use?

Standard categories — feeds, messaging, storage, rate limiting — and you can name a specific one.

Should I still practice on a whiteboard?

Yes, do both. Use Vera for structure and delivery, and a whiteboard for the visual half.

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.