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 6 of 37
Tests serialization, headers, status mapping, timeouts, and retries against a controllable HTTP boundary instead of mocking fluent internals.
Exercises signal-based component contracts through Angular bindings and waits for scheduled rendering before asserting.
Tests anonymous, authenticated, forbidden, CSRF, JWT, method, ownership, and full credential flows without confusing mocked identity with authentication.
Explains why ordinary injection resolves once and chooses providers, factories, scoped proxies, or explicit parameters for shorter-lived dependencies.
Uses multiple thread dumps, CPU correlation, lock ownership, executor context, and request evidence to distinguish deadlock, contention, blocking, and hot loops.
Uses parametrization for one behavior across meaningful cases while keeping failures and intent easy to read.
Runs stable shared production-like dependencies with Spring service connections, real migrations, deterministic data, and bounded startup cost.
Handles multipart uploads with bounded size, untrusted metadata, content inspection, controlled storage, scanning, and cleanup.
Combines multipart limits, metadata validation, content inspection, safe storage, and asynchronous malware processing.
Uses cascaded validation for nested DTOs, class-level constraints for local invariants, and domain services for state-dependent rules.
Keeps FastAPI dependency resolution at transport and composition boundaries while application services use explicit dependencies.
Separates interruptible background rendering from time-based event or request suppression.
Uses versioned migrations and staged compatibility instead of letting Hibernate mutate a production schema automatically.
Handles token-budget overflow and incomplete generation through explicit prioritization, rejection, retrieval, summarization, continuation, and validation.
Separates provider refusals, safety blocks, token truncation, transport failure, and valid domain abstention.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Treats interruption as a cooperative request, preserves interrupt status, defines cleanup, and separates cancellation signals from guaranteed task termination.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Transforms conversational requests into bounded search inputs while preserving user intent, constraints, and traceability.
Balances retrieval precision, answer completeness, document structure, overlap, metadata, and model input limits.
Chooses a model from task-specific evaluation, operating constraints, safety, latency, cost, context, modality, and provider requirements.
Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.