Loading
Pick a focused question that fits your time, stack, and interview goal.
613 results across 1 active filter
Page 17 of 26
Proves parallel speedup against a sequential baseline while accounting for overhead, saturation, tail latency, resource contention, and downstream impact.
Builds a story about helping a teammate grow while still moving the work forward.
Implements interval merging for scheduling-style time ranges with sorted output.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.
Builds a story about handling a missed estimate transparently and recovering with a realistic plan.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains how to monitor external and internal dependencies after a .NET service release.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Uses nullable annotations as a compile-time contract while still validating untrusted and legacy runtime inputs.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.