Software engineer interview questions with answer frames you can actually use

Example output

Illustrative examples only — not real candidate achievements or testimonials.

• Frame — p95 spike: traces in Datadog showed a new N+1 in the job query; we added a Redis cache and a regression test. p95 returned from 400ms to 80ms.

  Datadog · 80ms

• Frame — design a job ingest: Kafka for burst, consumer with idempotent writes to Postgres, dead-letter for poison payloads, Grafana lag alerts.

  Kafka · lag alerts

• Frame — failed deploy: GitHub Actions went green on unit tests; k6 in staging caught a 3x regression. We gated merge on the load test.

  k6 · 3x

• Frame — disagreement: product wanted a sync API; I argued for an async queue because of 8k RPS. We shipped async with a status endpoint.

  SQS · 8k RPS

• Frame — on-call: PagerDuty at 2am, bad config in Argo CD rolled to 30% of pods; we halted the rollout and reversed.

  Argo CD · 30%

• Frame — mentoring: I paired on EXPLAIN for a 12-second report query; indexing cut it to 90ms and we documented the pattern.

  Postgres · 90ms

System design is a conversation, not a diagram dump

Start with users, scale, and the failure you will not accept. Draw the smallest design that meets the numbers they gave. Name real tools you have used (Postgres vs Dynamo, SQS vs Kafka) and why — not a fashion list.

If you have never operated the thing, say so and reason from first principles. Interviewers would rather hear that than a hallucinated consensus algorithm.

Debugging and production stories

Keep a short list of incidents: what alerted, what you looked at first (metrics, traces, recent deploys), what you changed, how you prevented the next one. Datadog, Sentry, and deploy diffs are more convincing than "I stayed calm."

Quantify when you can: MTTR, error rate, customer impact. Ranges are fine.

Collaboration questions are not personality tests

"Tell me about a disagreement" wants a technical disagreement: API shape, consistency, launch risk. Name the other function (product, SRE, security), the tradeoff, and the outcome. Fluff about being a team player wastes the round.

Frequently asked questions