Loading
Pick a focused question that fits your time, stack, and interview goal.
298 results across 1 active filter
Page 4 of 13
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
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.
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.
Designs an external partner API with authentication, versioning, rate limits, idempotency, documentation, and compatibility.
Designs synchronization with an external system using cursors, retries, idempotency, rate limits, and reconciliation.
Explains reset-token generation, hashing, expiration, generic responses, session revocation, and abuse controls.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Designs a file workflow with metadata, durable storage, validation, access control, scanning, and safe downloads.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.
Designs authenticated, replay-resistant webhook intake with durable acknowledgement, idempotent asynchronous processing, ordering policy, and reconciliation.
Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.
Chooses response cache directives for public, private, sensitive, and revalidated API data without leaking user-specific content.