Pick a focused question that fits your time, stack, and interview goal.
491 results across 1 active filter
Page 2 of 21
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.
Explains composing dynamic LINQ filters while keeping query execution in SQL and index-friendly.
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.
Use CancellationToken to stop wasted work when clients disconnect, timeouts expire, or background operations are being shut down.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Chooses contracts and shared implementation based on substitutability, state ownership, evolution, and inheritance constraints.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Chooses a sequential collection from size, mutation, access pattern, memory locality, and the behavior callers actually need.
Avoids hidden quadratic work by indexing repeated matches while preserving duplicate, missing, ordering, and memory semantics.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Chooses a type shape from identity, value semantics, mutation, copy cost, default values, and serialization boundaries.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Creates valid objects with clear intent while choosing construction patterns proportionally to optional data, validation, and lifecycle complexity.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Separates ordinal identity comparison from culture-aware display ordering and keeps hash-based collection semantics consistent.
Chooses database test infrastructure by the provider behavior a test must prove.