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 36 of 37
Explains assignability by shape, excess-property checks, and the gap between compile-time compatibility and runtime identity.
Separates static annotations from runtime enforcement and explains how tools and frameworks can inspect type information.
Describes the context window as the bounded request state containing instructions, conversation, retrieved evidence, tool results, and output capacity.
Explains the path from Java source to bytecode and running code, including class loading and the JIT without turning the answer into JVM trivia.
Defines abstraction as a deliberate contract over essential behavior, then explains practical C# boundaries and the cost of weak abstractions.
Defines abstraction as a deliberate contract over essential behavior and keeps Java mechanisms secondary to the design purpose.
Explains closures as functions retaining access to lexical bindings, then connects them to callbacks, factories, state, and common capture mistakes.
Explains Java lambdas as implementations of single-abstract-method contracts and connects standard interfaces to API design.
Defines a large language model through next-token prediction and connects that mechanism to useful language behavior and its limits.
Explains LINQ deferred execution with EF Core with practical .NET data-access examples and production trade-offs.
Defines Django as a batteries-included Python web framework and separates framework conveniences from application design.
Defines FastAPI as an ASGI web framework and explains how types drive validation, dependency resolution, responses, and OpenAPI.
Explains how route values, query strings, headers, and request bodies become typed endpoint input.
Defines object-oriented programming clearly, then connects objects, responsibilities, and the main OOP mechanisms to practical C# design.
Defines OOP directly and connects Java objects, responsibilities, state, behavior, and collaboration to a practical design.
Distinguishes a Java type definition from a concrete runtime instance and keeps identity, state, and polymorphism tied to the question.
Separates deployment-level Django configuration from cohesive application features and explains the app registry.
Clarifies the difference between objects being retained accidentally and code simply allocating too much temporary memory.
Separates overlapping I/O work from simultaneous execution across processing resources.
Separates proving an identity from deciding whether that identity may perform a specific action on a resource.
Distinguishes a type's natural order from external, reusable sort strategies and connects comparison consistency to sorted collections.
Separates managing overlapping tasks from executing work simultaneously and connects both to Java backend design.
Separates view-oriented controller return handling from class-level response-body semantics without implying different request mapping.
Separates the persistence specification, its ORM implementation, and Spring's repository abstraction while keeping generated SQL visible.