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.
300 results across 1 active filter
Page 6 of 13
Uses documented thread-safe scheduling APIs and keeps event-loop objects confined.
Uses a password-specific algorithm, measurable work settings, and gradual rehashing without blocking service capacity.
Reuses bounded redis-py pools for the application lifetime and closes async resources deliberately.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Separates stale checkout protection, connection aging, pool waits, statement timeouts, and uncertain transactions.
Treats cancellation as cooperative control flow with reliable resource cleanup and propagation.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Uses Optional to model absence at return boundaries and avoids eager defaults, null Optionals, unsafe get calls, and awkward field or parameter usage.
Places the application class above owned components, uses capability-oriented packages, and keeps scanning and imports deliberate.
Stores salted adaptive password hashes, supports algorithm migration, and separates password verification from encryption.
Uses Pydantic models as explicit transport contracts without making them persistence or domain models automatically.
Keeps Celery messages small, safe to deserialize, and compatible across rolling deployments.
Aligns pytest-asyncio discovery, loop lifetime, and async fixture ownership without custom loop competition.
Defines one explicit SQLAlchemy session and transaction owner for each request, job, thread, or async task.
Explains decimal construction, scale, equality, rounding, and why BigDecimal needs a money contract around it.
Designs backpressure, worker ownership, completion tracking, failure, and shutdown around asyncio queues.
Builds an immutable Java type through valid construction, final state, defensive copying, controlled exposure, and safe sharing.
Combines selective Celery retries with bounded backoff, idempotent effects, and a terminal failure path.
Finds repeated relationship queries and fixes the data shape without introducing a larger query problem.
Connects one slow Python request to generated SQL, representative parameters, database plans, and measured validation.
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Maps DRF and application failures into stable client errors while preserving internal diagnostic evidence.
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.