Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 4 of 29
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.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
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.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains loading, error, empty, success, refetch, stale data, and request lifecycle in client-rendered React.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Uses complexity as a first filter while accounting for constants, locality, allocations, data size, and the complete operation sequence.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Builds a story about explaining engineering risk in business terms without hiding uncertainty.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Compares cache-aside, read-through, and write-through by read and write ownership, freshness, failure behavior, invalidation, fallback, stampede control, and operational complexity.
Designs a narrow covering index from predicates and ordering, then weighs eliminated lookups against storage, write overhead, cache efficiency, overlap, and maintenance cost.
Explains when CSRF matters, how cookies change browser behavior, and what mitigations fit API clients.
Explains when local process memory is enough and when shared Redis-style caching is worth the extra dependency.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.