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.
1225 drills fit a 20-minute session. Closest fits first.
Page 22 of 52
Treats the model-facing schema and downstream consumer contract as a versioned API with compatibility and rollout concerns.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Keeps cached reads acceptably fresh and prevents hot-key reloads from overwhelming the database across application instances.
Maps validation, HTTP, domain, and unexpected failures into a stable client contract while preserving diagnostics.
Places an idempotency key at the Spring boundary while persisting request identity and terminal outcome atomically with business work.
Coordinates startup work, readiness, schema compatibility, warmup, and mixed-version traffic during a rolling release.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Organizes Django configuration without duplicating environments or leaking secrets into source code.
Carries an original version through an API update and turns an optimistic-lock failure into an explicit conflict workflow.
Frames allocation reduction as measurement-driven API work rather than premature micro-optimization.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Builds a readable request with stable instructions and clearly delimited, provenance-aware untrusted inputs.
Sizes per-instance database concurrency from workload and database capacity instead of equating more connections with more throughput.
Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.
Uses thread dumps, heap dumps, logger changes, mappings, and configuration evidence through a tightly controlled operator path.
Checks model, feature, API, region, quota, commercial access, lifecycle, and dependent-service compatibility before rollout.
Builds a story about improving code quality incrementally while still delivering product value.
Builds a concrete story about earning alignment through evidence, listening, and a low-risk path rather than positional power.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Explains when to store large payloads outside the broker and pass references through messages.
Design a bounded-concurrency approach for calling an external API safely from .NET code.
Predicts when an in-memory LINQ pipeline runs and prevents repeated work, changed results, and hidden side effects.