95Build an in-memory key-value database, then extend it across stages: TTL, transactions, snapshots.▼hardAnthropicOpenAIGoogle1 replies◆ premiumThe classic multi-round build screen: a plain key-value store that gains new requirements at each stage (TTL, transactions, scans). The signal is not stage 1, it is whether your code takes on stage 4 without a rewrite. Here is how to design for it.Open full answer →
100Refactor a 500-line function that parses, computes, and prints into unit-testable pieces without changing behavior. Walk me through it.▼hardOpenAIAnthropic◆ premiumMost candidates start rewriting. The interviewer is grading whether you isolate pure logic from side effects before you touch a line, because that is the difference between a safe refactor and a silent behavior change.Open full answer →
104Build a small tool to a loosely defined, shifting spec: clarify, structure for change, adapt mid-session.▼mediumGoogleAnthropicOpenAI2 replies◆ premiumGoogle's 'vibe coding' screen: the spec is intentionally vague and shifts mid-interview. The signal isn't the algorithm, it's whether you clarify before coding, structure for change, and keep tests green as the requirements move. Here is how to run that loop.Open full answer →
