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.
405 results across 1 active filter
Page 7 of 17
Designs live updates with polling, server-sent events, or WebSockets while preserving authorization, ordering, scale, and fallback behavior.
Designs scheduled jobs with locking, idempotency, observability, retries, and safe operations across multiple instances.
Builds request and response contracts that tolerate independently deployed clients through explicit ownership, additive evolution, stable semantics, and measured deprecation.
Designs saved filters, scheduled matching, alert delivery, and freshness trade-offs for search-driven product workflows.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.
Designs a controlled support impersonation workflow with scoped access, approvals, visible banners, audit trails, and session boundaries.
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Explains hot-key behavior, traffic concentration, partition pressure, payload size, and mitigation options.
Diagnoses hidden per-row EF Core queries and replaces them with a bounded query shape without creating an oversized join.
Investigate a production API slowdown caused by blocking async calls, thread-pool pressure, and dependency waits.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Investigate a slow API by checking database queries, blocking async, dependency latency, serialization, logging, and runtime pressure.
Pairs a bounded isolated reproduction with telemetry and a disposal fix for leaked database connections.
Decide whether Azure SQL errors are transient platform faults or a real application/query regression.
Builds deterministic images efficiently by controlling context, restore layers, dependency inputs, and cache invalidation.
Uses Compose for reproducible local dependencies while preserving fast inner loops, realistic readiness, and clear differences from production orchestration.
Diagnoses thread-unsafe scoped dependencies inside parallel execution and redesigns the data boundary without exhausting shared resources.
Investigate and fix an API where client retries create duplicate orders, payments, or records.
Compare minimal API endpoint filters and MVC filters by context, scope, and use case.
Turns a modular-monolith choice into enforceable code and data ownership rather than relying on folders and team discipline alone.