Loading
Pick a focused question that fits your time, stack, and interview goal.
206 results across 1 active filter
Page 3 of 9
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.
Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
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.
Explains soft delete in EF Core APIs with practical .NET data-access examples and production trade-offs.
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.
Places contract, use-case, domain, authorization, and database validation at the boundaries that can enforce each rule consistently.
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.
Designs comments with permissions, threading, mentions, notifications, editing history, and moderation concerns.
Designs draft, review, publish, rollback, and audit behavior for content managed by editors and admins.
Designs deletion, retention, soft delete, hard delete, backups, audit records, and asynchronous cleanup across related data.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Designs user reports, moderation queues, actions, audit history, abuse controls, and appeal-friendly decisions.