Loading
Pick a focused question that fits your time, stack, and interview goal.
108 results across 1 active filter
Page 3 of 5
Frames a vague system-design problem with explicit flows, constraints, scale estimates, and measurable quality targets before selecting components.
Builds a story about making competing work visible and helping the team choose intentionally.
Builds a story about turning unclear requirements into a scoped, testable plan without overbuilding.
Chooses immutable values and controlled mutable entities based on identity, concurrency, invariants, allocation cost, and update semantics.
Builds a story about improving code quality incrementally while still delivering product value.
Builds a story about improving team workflow with lightweight, useful process changes.
Uses inheritance only for stable behavioral subtyping and tests whether derived objects preserve the promises callers rely on.
Uses the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.
Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.
Balances declarative transformations with explicit control flow when allocation, early exit, mutation, diagnostics, or complex state matters.
Builds a story about learning a new technology in a structured way and applying it safely.
Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.
Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.
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.
Chooses when to keep a sequence lazy and when to create a stable collection with ToList, ToArray, or another deliberate materialization.
Builds a story about helping a teammate grow while still moving the work forward.
Builds a story about handling a missed estimate transparently and recovering with a realistic plan.
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.