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.
237 results across 1 active filter
Page 9 of 10
Separates SQL synchronization from transaction completion and explains recovery after database errors.
Distinguishes fewer network round trips from atomic execution and chooses the smallest correct Redis primitive.
Distinguishes the synchronous WSGI request contract from ASGI's asynchronous, multi-event application contract.
Connects stable hashing and equality to dictionary and set correctness, including custom types and mutable-key failures.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Defines omission, nullability, field ownership, invariants, concurrency, and effects for DRF partial updates.
Turns Django's production settings, server, storage, security, and operational dependencies into a repeatable release check.
Uses an explicit discriminator to model genuine request variants with predictable validation and OpenAPI output.
Chooses between small in-process follow-up work and durable, independently operated background execution.
Explains lazy query construction, evaluation triggers, result caching, and repeated-query surprises.
Uses generics to preserve relationships among types and introduces bounds, constraints, and variance only where they clarify a real API.
Chooses dataclasses for transparent data-oriented types while preserving invariants, safe defaults, and honest immutability claims.
Distinguishes small in-process post-response work from durable, retryable, independently operated jobs.
Uses generated examples to test stable invariants while preserving readable examples and reproducible failures.
Chooses a Django user model early and preserves swappable references without turning it into a profile dumping ground.
Varies DRF query and representation behavior deliberately across list, detail, and write actions.
Chooses between FastAPI-managed response processing and direct control over the HTTP response.
Chooses between synchronous and asynchronous FastAPI handlers based on the libraries and work they execute.
Uses fixture factories and test-data builders to keep setup flexible, readable, and owned by each test.
Aligns selected database data with an API read model and avoids unnecessary ORM state.
Uses task-aware context for tracing while keeping business inputs explicit and correctly reset.
Uses cryptographically secure token generation and timing-resistant comparison at credential boundaries.
Uses Django signals selectively and makes transaction timing and side effects explicit.
Distinguishes object identity from value equality and prevents fragile code based on interning or implementation accidents.