Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
119 results across 1 active filter
Page 1 of 5
Turns a production-only role and payload failure into the smallest durable API regression test.
Aggregates log entries into per-minute error counts with deterministic output.
Partitions limits by authenticated user or trusted client address and returns useful 429 retry metadata.
Loads a resource once, evaluates owner-or-capability authorization, and avoids trusting route ownership claims.
Pre-aggregates two one-to-many relationships before joining them to prevent fanout from corrupting financial totals.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Implements a safe in-memory paging helper with metadata and boundary handling.
Builds a route-level Next.js failure UI with safe reporting, retry, and an escape route while keeping expected errors out of the boundary.
Implements bounded filtering and deterministic keyset pagination without accepting arbitrary query expressions.
Creates a resource through an explicit request DTO and returns typed 201, 409, and validation outcomes.
Builds several daily business metrics in one grouped query while keeping each metric definition explicit.
Models file validation, progress, cancellation, failure, and retry without losing the selected file.
Uses an ordered window aggregate to calculate a deterministic running balance per account.
Implements invoice total calculation with quantity, unit price, percentage discount, and rounding.
Combines daily aggregation, a calendar table, and a window frame to calculate true seven-calendar-day revenue.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Implements chunking for batch processing without dropping final partial batches.
Implements comparison for simple semantic version strings with missing patch parts treated as zero.
Builds optional EF Core predicates while preserving server translation, stable ordering, and a bounded result.
Implements a word-frequency counter with normalization, punctuation handling, and stable ordering.