Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 8 of 29
Distinguishes callable delegate values from publisher-controlled events and makes subscription lifetime explicit.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
Design API error handling across validation errors, conflicts, auth failures, not-found responses, and unexpected exceptions.
Designs feature flag storage, targeting, safe defaults, auditability, and rollout observability for backend behavior.
Explains batching, tracking control, idempotency, validation, and operational safety for large EF Core imports.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
Designs tenant isolation across API, data, cache, background jobs, search, and admin access.
Designs an activity feed with event capture, fan-out strategy, pagination, privacy, and read performance.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.
Designs immutable audit records for sensitive administrative changes with useful before/after context and safe retention.
Explains how EF Core SaveChanges, transactions, and an outbox keep database changes and messages consistent.
Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.
Makes POST retries return one durable business outcome by combining scoped keys, request identity, atomic ownership, response replay, and reconciliation.
Builds a race-safe upsert around database-enforced identity, explicit conflict semantics, retries, ordering, and side-effect boundaries.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end boundaries.
Designs an external partner API with authentication, versioning, rate limits, idempotency, documentation, and compatibility.