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.
878 drills fit a 10-minute session. Closest fits first.
Page 19 of 37
Compare endpoint styles in real services, including organization, conventions, testing, filters, and OpenAPI behavior.
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
Explains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.
Explains database constraints versus application validation with practical data-access examples and production trade-offs.
Distinguishes instants, local calendar values, offsets, and named time zones so APIs and persistence survive daylight-saving and locale boundaries.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Distinguishes callable delegate values from publisher-controlled events and makes subscription lifetime explicit.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
Explains reset-token generation, hashing, expiration, generic responses, session revocation, and abuse controls.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Explains how to split components around ownership, reuse, readability, state, and API-like prop contracts.
Explains retry strategy for transient failures and poison-message handling for permanent failures.
Explains how custom hooks share stateful behavior while preserving ownership, lifecycle, and a focused contract.
Explains N plus one query behavior, symptoms in APIs, fixes with set-based reads, batching, projections, and monitoring.
Explains command messages versus event messages and how ownership changes their design.