Loading
Pick a focused question that fits your time, stack, and interview goal.
618 drills fit a 20-minute session. Closest fits first.
Page 13 of 26
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Explains the risks of Redis-based distributed locks and when database constraints, queues, or idempotency are safer.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.
Evaluates whether read-heavy access justifies a reader/writer lock instead of a simpler lock or immutable snapshot.
Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.
Separates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.
Builds a story about protecting quality while still making practical delivery decisions.
Builds a story about resisting unnecessary complexity and choosing maintainable design.
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Builds a story about explaining engineering risk in business terms without hiding uncertainty.
Designs useful local database and cache resources without confusing container lifetime, durable data, bind mounts, parameters, and production secrets.
Improve diagnosis when App Service log stream does not show enough information during an incident.
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Diagnose browser CORS errors after moving an Azure-hosted API or frontend to a new custom domain.
Collects a bounded EventPipe CPU trace and reads stack evidence without confusing hot methods, blocked time, native work, or sampling artifacts.
Builds a story about resolving technical disagreement in review without ego or passive approval.
Builds a story about turning an incident into regression guards, observability, and process improvement.
Builds a story about making competing work visible and helping the team choose intentionally.
Builds a story about turning unclear requirements into a scoped, testable plan without overbuilding.
Builds a story about improving team workflow with lightweight, useful process changes.
Builds a story about learning a new technology in a structured way and applying it safely.
Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.
Builds a story about helping a teammate grow while still moving the work forward.
Builds a story about handling a missed estimate transparently and recovering with a realistic plan.