Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 19 of 29
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.
Chooses when to keep a sequence lazy and when to create a stable collection with ToList, ToArray, or another deliberate materialization.
Explains cache observability across hit rate, latency, source load, memory, evictions, stale data, and fallback behavior.
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.