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 7 of 37
Builds a small, task-relevant, typed toolset with clear semantics rather than exposing an entire internal API surface.
Selects relevant, trustworthy, and budgeted context instead of treating the context window as storage.
Turns a product outcome into observable quality, safety, and operational criteria before selecting convenient scores.
Defines a narrow capability with a clear name, decision-oriented description, typed inputs, and safe result semantics.
Designs a narrow, typed, provider-supported schema that communicates the real downstream contract.
Balances route ownership, initial bundle cost, likely navigation, authorization, and measurable user experience.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Moves from user-visible latency to route, dependency, database, executor, JVM, and change evidence before selecting a fix.
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Uses Hikari metrics, thread evidence, database activity, transaction scope, and query behavior to separate leaks from slow or excessive work.
Triages heap, Metaspace, native, direct-buffer, thread, and container exhaustion using preserved evidence before changing limits.
Separates server request capacity from application executor capacity and finds blocking, queueing, rejection, or downstream causes.
Diagnoses queued work, blocked workers, nested submissions, common-pool contention, downstream waits, and misleading CPU symptoms.
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.