Loading
Pick a focused question that fits your time, stack, and interview goal.
104 results across 1 active filter
Page 3 of 5
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Implements correct half-open interval overlap logic for booking validation.
Diagnoses hidden per-row EF Core queries and replaces them with a bounded query shape without creating an oversized join.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Separates a live blocking chain from a deadlock victim, gathers the right database evidence, stabilizes the incident, and fixes lock duration or access order.
Explains N plus one query behavior, symptoms in APIs, fixes with set-based reads, batching, projections, and monitoring.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Explains join behavior using API-shaped data, missing related rows, and result-cardinality trade-offs.
Compares offset and keyset pagination for stable API lists, large tables, and user-facing result consistency.
Explains relational modeling, duplication, write consistency, read performance, and when denormalized data is justified.
Writes predicates the optimizer can use as index search arguments, then proves the effect through plans and reads while balancing computed columns, composite indexes, and write overhead.
Explains SQL three-valued logic, null-safe filters, optional relationships, and API behavior around missing values.
Explains parameter sniffing, data skew, cached plans, symptoms, and cautious mitigation options in SQL Server.
Explains how statistics and cardinality estimates affect plan choice, joins, memory grants, and slow queries.
Uses EXISTS instead of a row-multiplying join when the related table is only a filter.
Groups normalized email values to identify duplicates before adding or repairing a uniqueness rule.
Uses the gaps-and-islands pattern to find consecutive login-day streaks after deduplicating same-day activity.
Solves a many-to-many all-match filter with grouping and a deliberate empty-selection rule.
Uses NOT EXISTS to express an anti-join without null traps or duplicate parent rows.
Uses a recursive CTE to return hierarchy depth and a readable root-to-node path.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.