What Senior Sounds Like in a Design Interview
Two candidates, same components. The gap is rarely knowledge — it's unprompted trade-offs, naming non-goals, quantifying first and a qualified 'it depends'.
5 min read
On this page
Put two transcripts side by side, one from a candidate who got a mid-level offer and one from a candidate who got a senior offer, and strike out every proper noun. The component lists are nearly identical. Both said load balancer, cache, read replicas, queue, object storage, CDN. Both knew what each one does. Neither said anything factually wrong.
The levelling decision came from the sentences around the components, and there are four patterns that account for most of it. None of them require knowing more than you already know.
Trade-offs arrive before they are asked for
The mid-level pattern is: make the choice, wait for the challenge, then justify. It is not wrong — the justification, when it comes, is often good. But the sequence tells the interviewer that the trade-off was retrieved on demand rather than considered at the moment of choosing, and those feel different from the outside.
The senior pattern attaches the cost to the decision in the same breath.
"I'll denormalise the feed into a per-user table. That makes reads a single lookup, and it costs me a fan-out on every write plus a rebuild path when someone with a large following posts — I'll come back to that when we talk about the write path."
Nobody had to ask. And notice the last clause: they have flagged the weak point themselves, which means when the interviewer reaches it, the two of them are collaborating on a known problem rather than the interviewer discovering an oversight.
Volunteering the weakness in your own design is close to a pure signal. Candidates who do not understand a design cannot do it, because they do not know where the weakness is.
Saying what you are not building
Mid-level designs expand. Every feature mentioned gets a box, every "we could also" becomes a component, and by minute thirty-five the board has nine services and no time left to make any of them work.
Senior designs are visibly bounded, out loud.
"I'm not going to build search here — I'll assume it's a separate index that consumes the same change stream, and if you want to design that we can spend the time on it instead. I'm also not doing multi-region for now; single region with cross-region backups, and I'll say what would change if we needed active-active."
That does three things at once. It protects the clock. It shows you can tell a core requirement from an adjacent one. And it quietly demonstrates that you know how the excluded thing would work, without spending eight minutes proving it.
The strongest version of this is refusing complexity on purpose: "one leader handles this write rate comfortably, so I'm not sharding — sharding now would cost me cross-shard queries for a problem we don't have yet." Interviewers remember that sentence, because most candidates believe the exam rewards more machinery.
The number comes before the component
The single most reliable seniority tell is the order of two sentences.
Mid-level: "I'll add a cache here, because we'll have a lot of reads."
Senior: "Reads are running maybe a hundred to one against writes and the hot set looks like a few gigabytes, so a cache in front pays for itself — that's small enough to hold and skewed enough to hit."
The component is the same. The second one derived it, and the derivation is portable: it will still work when the interviewer changes the workload, because it was never about the component being generally good.
The same inversion applies everywhere. Do not say "we should shard" — say what the write rate is and then say it exceeds what one leader will take. Do not say "add a CDN" — say the egress figure and let it force the conclusion.
"It depends" with the dependency attached
Everyone knows "it depends" is the right answer. Said bare, it is the weakest sentence in the interview: it sounds like a hedge, and it puts the work back on the interviewer.
The fix is mechanical. Never let the phrase end a sentence. Follow it immediately with the variable, and then with both branches.
"It depends on whether a duplicate charge is recoverable. If finance can reverse it the next day, at-least-once delivery with idempotency keys is fine and much simpler. If it isn't recoverable, I need the payment write and the event publish in one transaction, and that pushes me to an outbox."
You have now answered the question twice, correctly, and shown exactly what would decide it. That is the opposite of a hedge.
The same content, two ways
| Mid | Senior |
|---|---|
| "I'll add a cache." | "Hot set is small and reads dominate, so a cache earns its keep — here's the invalidation story." |
| "We should shard the database." | "One leader takes this write rate, so I'm not sharding yet — but here's the key I'd pick when we do." |
| "It depends." | "It depends on whether stale reads are visible to the user — if they are, X; if not, Y." |
| "We can use a queue for spikes." | "A queue defers the spike; if arrivals stay above service rate I need to shed load, not buffer it." |
| "That should be fine." | "That's fine until the consumer lags — I'd alarm on queue age rather than depth." |
| "I'd use Postgres." | "Access is by primary key with no joins, so almost anything works; I'd take Postgres for the operational familiarity." |
Read down the right column and notice what is not there: nothing rarer, nothing newer, no technology the left column had not heard of. Every senior sentence is the mid sentence plus a reason, a cost, or a condition.
What to practice
The gap is not a reading list. You will not close it by learning another consensus protocol, and most candidates who are stuck at mid have already learned three.
Close it by changing what you say at the moment you place a box. One habit is enough to start: never put a component on the board without saying, in the same sentence, the number that justified it and the thing it makes worse.
Do that consistently and you will sound senior long before you feel it — which is roughly the order it happens in on the job as well.