Interview craft

How a staff engineer actually sounds

Senior engineers answer the question. Staff engineers answer the question behind it. The content below is the same for both levels — what changes is the shape of the delivery.

The four-beat answer

Use it on every design question

Frame the decision.

Name the trade-off before you pick a side. "This is really a recall-versus-latency question, so it depends on what the product tolerates."

Give the default.

Say what you'd do on day one with no data. Staff engineers have opinions; they just hold them loosely.

Name the measurement.

Every claim gets a number attached. Recall@k, nDCG, p95 latency, cost per thousand queries. If you can't measure it, say that too.

Name the failure mode.

"Where this breaks is…" This is the single biggest tell of seniority. Juniors describe the happy path. Staff engineers describe the pager.

Say this, not this

Same knowledge, different level

Say this

"Before I answer, what's the corpus size and how often does it change? That flips the design."

Not this

"You should use a vector database with embeddings and then do similarity search."

Say this

"We shipped the dumb version first — BM25 only — to get a quality baseline we could regress against."

Not this

"We used the latest embedding model because it's state of the art on MTEB."

Say this

"That cost us about 40ms at p95. We bought it back by batching the reranker."

Not this

"It was fast enough."

Say this

"I'd push back on building RAG here. The corpus is 200 docs — put them in the prompt."

Not this

Building whatever was asked for without questioning whether it's needed.

Scope signals that read as 15 years

What interviewers listen for

You talk about the team, not just the code.

"I wrote the eval harness mainly so three other squads could stop arguing from vibes."

You mention what you chose not to build.

"We skipped the reranker for six months because recall wasn't the bottleneck — the parser was."

You quantify blast radius.

"This touched 4 services and 11 million documents, so we did it behind a dual-write."

You own a bad call.

One honest "I got that wrong and here's the signal I missed" buys more credibility than five clean wins.

You cite boring wins.

Deleting a component, cutting cost 60%, reducing on-call pages. Staff work is often subtraction.

You translate to business.

"Support deflection went from 18% to 31%, which was roughly 9 headcount of ticket volume."