Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
1225 drills fit a 20-minute session. Closest fits first.
Page 2 of 52
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
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.
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.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
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.
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
Designs scheduled jobs with locking, idempotency, observability, retries, and safe operations across multiple instances.
Designs saved filters, scheduled matching, alert delivery, and freshness trade-offs for search-driven product workflows.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Uses traces and saturation evidence to locate retry amplification, queue growth, exhausted workers, and failing fallback paths.
Uses traces to separate unclear goals, bad tool interfaces, missing state, contradictory results, poor termination, and retry amplification.
Diagnoses an AI regression by decomposing request stages, configuration changes, token growth, retries, routing, tools, retrieval, caching, and provider behavior.
Reproduces failing cases, compares versioned traces, isolates the first changed component, mitigates impact, and adds regression coverage.
Traces buffering through the production artifact, proxy chain, compression, cache, platform adapter, and version consistency.
Traces a missed answer through source ingestion, parsing, chunking, filtering, query construction, retrieval, fusion, and ranking.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Implements a safe in-memory paging helper with metadata and boundary handling.