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.
171 results across 1 active filter
Page 2 of 8
Explains dependency graphs, sub-dependencies, request-local caching, failures, and deliberate cache bypass.
Builds a cooperative scheduling model for tasks, callbacks, readiness, and I/O polling.
Uses separate Pydantic input and output models to prevent mass assignment and accidental data disclosure.
Explains suspended generator execution, lazy production, deferred failures, cleanup, and one-pass consumption.
Explains Python assignment as name binding and connects identity, type, value, aliasing, mutation, and rebinding.
Models alternative value types accurately and narrows them through checks without confusing optionality with default arguments.
Explains how input conversion, strict validation, and extra-field policies change what an API accepts and preserves.
Explains pytest fixture dependency resolution, caching, lifetime, and the isolation cost of wider scopes.
Explains module identity, package organization, import caching, execution context, circular dependencies, and side-effect boundaries.
Explains object identity, tracked changes, flush ordering, and the limits of session-level caching.
Uses Django cache configuration to control freshness, namespace sharing, and safe cache migrations.
Explains per-worker memory and copy-on-write savings without preloading process-unsafe resources.
Connects Django deployment interfaces with the real sync and async call chain.
Explains reverse-order fixture cleanup and designs teardown that remains safe when setup or tests fail.
Chooses Python collections by ordering, uniqueness, lookup, mutability, and domain intent rather than complexity slogans alone.
Chooses the smallest DRF view abstraction that expresses an endpoint clearly.
Chooses a concurrency model from workload, libraries, isolation, runtime build, and operational cost.
Chooses relationship loading from cardinality, query count, result size, and hidden-I/O boundaries.
Finds synchronous I/O or CPU work that prevents the event loop from scheduling other tasks.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Combines asyncio debug evidence, task inspection, warnings, profiling, and capacity signals.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Defines fail-fast, all-results, and partial-success behavior for concurrent asyncio operations.
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.