Dev Skills
Track C

Interview archetypes

Six styles of interviewer, described by behaviour rather than by company. Pick one and problem pages, timed mocks and the follow-up blitz favour the follow-up questions that interviewer would ask.

Learning “the answer a particular company wants” falls apart once an interviewer goes off script. Learning to recognise how someone is testing you carries over to any interview, and the same design gets graded very differently by a Cost Auditor and a Scale Breaker.

Questions every decision. Keeps asking "why not the other way?"

Weights Tradeoffs mostQuestion the choiceForce the cost
A failing answer here

You change your answer the moment they push. If you switch from a queue to a direct call because they raised an eyebrow, you have told them the first answer was memorised.

Read and drill →

What does this cost per month? Is there a cheaper way? Who gets paged at 3am?

Weights Tradeoffs mostForce the costOperations
A failing answer here

You have no idea which line item dominates. If you cannot say whether bandwidth, storage or compute is the biggest cost, you have not connected your design to your estimates.

Read and drill →

Multiplies your traffic, adds celebrity users and hot keys, kills a region.

Weights Numbers mostBreak the scaleKill something
A failing answer here

"It scales horizontally." Some part never does, and not naming it means you have not looked.

Read and drill →

Picks one hard subproblem and stays inside it for thirty minutes.

Weights Design mostAttack consistencyKill something
A failing answer here

You run out of depth after two levels. You can say "we would use a cache" and "cache-aside", and then nothing.

Read and drill →

Changes the requirements halfway through, on purpose.

Weights Requirements mostChange the scopeQuestion the choice
A failing answer here

You start over. Most scope changes affect one part of a design, and rebuilding everything shows you cannot see the boundaries.

Read and drill →

Imposes a hard limit up front and grades everything within it.

Weights Requirements mostChange the scopeForce the cost
A failing answer here

You design the normal system and then bolt the constraint on at the end. It has to shape the design from Stage 1.

Read and drill →