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.
1345 results
Page 41 of 57
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
Diagnoses incompatible cached HTML and immutable assets across CDN, browser, service-worker, and rollout boundaries.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Uses static members for type-wide stateless behavior and constants while avoiding hidden global mutable state and lifetime problems.
Wraps widget creation, listeners, observers, timers, and destruction in one lifecycle boundary and verifies repeated navigation does not accumulate resources.
Explains session state choices for scaled-out ASP.NET Core APIs and when Redis-backed state is appropriate.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Distinguishes operators that can yield incrementally from operators that must consume substantial input before producing results.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Uses async streams for incremental asynchronous production while preserving cancellation, disposal, backpressure expectations, and API boundaries.
Diagnoses schema-valid quality regressions across inputs, context, prompts, examples, models, schemas, tools, and downstream interpretation.
Structures xUnit tests around per-test instances and shares only expensive infrastructure through deliberate class, collection, or assembly fixture lifetimes while preserving isolation and parallel safety.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Investigate blocked request threads and thread-pool starvation caused by Result, Wait, or GetAwaiter().GetResult().
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.
Explain when Task.Run is useful, when async/await is enough, and why Task.Run is usually wrong for I/O in ASP.NET Core.
Compare Task and Thread in .NET, including abstraction level, scheduling, and when direct thread management is rarely appropriate.
Moves invariant-sensitive decisions toward the owning object while keeping orchestration, queries, and cross-boundary work appropriately explicit.
Shows honest ownership of a project that missed its goal, including evidence, recovery, and changed judgment.
Builds a concrete story about owning a feature from requirements through release, verification, and follow-up.