Find your next engineering question

Database Internals & Transactions · Senior

Locating the newest value in an append-only store through an in-memory key directory, preserving tombstones, reclaiming segments, and rebuilding the index on restart.

Database Internals & Transactions · Staff

Defining a local durable-commit boundary and the role of WAL ordering, fsync, checkpoints, torn pages, and recovery under process versus system failure.

Database Internals & Transactions · Senior

How B-tree leaf and parent page splits preserve ordered lookup under concurrent writers, including latches, fillfactor, key distribution, and secondary-row fetches.

Database Internals & Transactions · Senior

Tracing LSM updates through WAL, memtables, immutable SSTs, overlapping L0 files, point reads, versioned deletes, and snapshots.

Database Internals & Transactions · Staff

Identifying an unsustainable background work rate and the distinct RocksDB stall triggers, then validating steady state without defeating durability or read health.

Database Internals & Transactions · Senior

Read-path economics with correct selectivity: random heap fetches versus sequential scan; why index presence does not establish a faster access route.

Database Internals & Transactions · Senior

Composite B-tree key ordering and ORDER BY satisfaction across multiple equality groups; indexes do not promise one global ordering across grouped ranges.

Database Internals & Transactions · Staff

Planner statistics and prepared-statement generic-vs-custom plan choice under extreme tenant skew, distinguished from correct high-volume work.

Database Internals & Transactions · Staff

Memory and I/O behavior of a hash join crossing its working-set threshold, including batch spill, concurrent memory multiplication, and remediation.

Database Internals & Transactions · Staff

Why index-only scans still consult heap MVCC visibility via the visibility map, and how volatile rows, vacuum, and HOT index-maintenance constraints change the tradeoff.

Database Internals & Transactions · Senior

Lost update from stale application-calculated assignments under Read Committed, distinguished from atomic SQL arithmetic, compare-and-swap, and short row locking.

Database Internals & Transactions · Staff

Multi-version visibility and snapshot lifetime, distinguishing Read Committed statement snapshots from Repeatable Read transaction snapshots and the vacuum retention cost.

Database Internals & Transactions · Staff

Write skew under snapshot isolation, demonstrating a cross-row predicate invariant violated without a write/write conflict and evaluated through guard-row locking or serializable retry.

Database Internals & Transactions · Staff

Real row-lock deadlocks versus ordinary contention, deterministic acquisition ordering, database victim selection and bounded whole-transaction recovery.

Database Internals & Transactions · Staff

Serializable Snapshot Isolation conflicts, SQLSTATE 40001, bounded full retries, read-footprint granularity and goodput versus wasted retries under contention.

Database Internals & Transactions · Senior

Decide when keyed lookup is sufficient, when a scan is unacceptable and what freshness contract a separate read model needs.

Database Internals & Transactions · Staff

Distinguish secondary lookup from uniqueness, then protect reassignment of an alternate key across separate records.

Database Internals & Transactions · Senior

Choose embedding versus referencing from boundedness, lifecycle, query shape and single-document atomicity.

Database Internals & Transactions · Senior

Derive Cassandra partitions, clustering order, bucketing and denormalized tables from concrete user queries.

Database Internals & Transactions · Staff

Distinguish Cassandra logged-batch atomic application from isolation, and assign authority and repair for duplicated query tables.

Database Internals & Transactions · Senior

Distinguish leading-wildcard scans, token retrieval and arbitrary substring matching, then select suitable indexes and semantics.

Database Internals & Transactions · Staff

Separate lexical BM25 score, candidate recall, graded ranking quality and user success using judged queries and safe experiments.

Database Internals & Transactions · Staff

Differentiate index durability, search refresh, Lucene commit, and immutable-segment merging without false ordering assumptions.

Database Internals & Transactions · Staff

Prove when local top-K is globally sufficient, identify shard-local scoring divergence, and design consistent pagination and fanout.

Database Internals & Transactions · Staff

Define exact facet query populations, distinguish post filters, and reason about approximate shard-local terms buckets.

Database Internals & Transactions · Principal

Migrate search mappings through consistent snapshots, change history, version-safe writes, cutover and reversible rollback.

Replication, Consistency & Consensus · Principal

Local transaction atomicity does not imply regional survival. Acknowledgment, promotion authority, and consequential publication must protect the same business decision.

Replication, Consistency & Consensus · Staff

Distinguish WAL receive, durable flush and replay visibility, and gate reads on a reliable apply boundary.

Replication, Consistency & Consensus · Senior

Define scope of read-your-writes and design client or account-level consistency tokens with fallback behavior.

Replication, Consistency & Consensus · Staff

Distinguish quorum intersection from monotonic reads and linearizability under partially applied or concurrent writes.

Replication, Consistency & Consensus · Staff

Diagnose write-history fanout, WAL-retention pressure, standby feedback and alternative read architectures.

Replication, Consistency & Consensus · Staff

Explain minority behavior, term-based elections, candidate freshness and the scope of reads under a network partition.

Replication, Consistency & Consensus · Staff

Distinguish log replication from commitment of prior-term entries, and connect Raft terms, election restriction and current-term commitment.

Replication, Consistency & Consensus · Staff

Distinguish lease expiration from the physical ability to write, and enforce non-regression with destination-side fencing.

Replication, Consistency & Consensus · Staff

Establish linearizable read authority using a quorum-confirmed read barrier and state-machine application, separate from local replay lag.

Replication, Consistency & Consensus · Principal

Prove overlapping authority across reconfiguration and plan learner promotion, joint consensus or sequential membership operations with failure recovery.

Networking & Protocols · Staff

Separating end-to-end client latency from instrumented server work, including requests that never produce an application span.

Networking & Protocols · Staff

The difference between assigning transport connections and routing requests when HTTP/2 channels are long-lived.

Networking & Protocols · Staff

Calculate BDP and distinguish receiver-window, congestion-window and application pacing limits on a long-RTT TCP flow.

Networking & Protocols · Staff

Diagnose how a small segment-loss rate can block ordered bytes, trigger retransmission timers and alter tail latency and congestion state.

Networking & Protocols · Staff

Differentiate incomplete SYN requests from completed connections awaiting accept, measure burst capacity and repair slow accept loops.

Networking & Protocols · Staff

Calculate destination-specific NAT mapping occupancy and distinguish gateway port exhaustion from local ephemeral ports and bandwidth limits.

Networking & Protocols · Staff

Diagnose size-dependent VPN loss through tunnel overhead, MTU and MSS arithmetic, ICMP feedback and black-hole-safe probing.

Networking & Protocols · Principal

Detect partial backend failures invisible to liveness probes using client-outcome dimensions and safely bounded outlier ejection.

Networking & Protocols · Senior

Trace stub, recursive and authoritative lookups, including TTLs, CNAME chains and negative caching.

Networking & Protocols · Staff

Design a safe DNS-based migration despite existing resolver caches, HTTP connections, stale answers and rollback limitations.

Networking & Protocols · Senior

Explain SAN hostname validation, intermediate and root trust chains, SNI and client-specific certificate policy.

Networking & Protocols · Staff

Compare full TLS 1.2 and TLS 1.3 setup, PSK resumption, early-data replay and safe application policy.

Networking & Protocols · Staff

Distinguish HTTP application serialization, TCP stream-level head-of-line blocking and independent QUIC stream delivery.

Networking & Protocols · Staff

Explain address-independent QUIC connection IDs, path validation, anti-amplification and backend affinity across network changes.

Networking & Protocols · Senior

Trace DNS, pod source address, private routes, security policy and the return path without assuming NAT.

Networking & Protocols · Principal

Choose peering, transit gateways and service endpoints from a traffic matrix while limiting failures and privileges.

Networking & Protocols · Staff

Separate BGP control-plane route withdrawals from healthy application servers, and diagnose internet reachability from outside.

Networking & Protocols · Staff

Explain shared anycast IPs, routing catchments, and why stateful TCP connections can fail when the chosen site changes.

Networking & Protocols · Staff

Diagnose failures after adding IPv6 AAAA records, including client fallback variation, NAT64, MTU and policy parity.

Networking & Protocols · Staff

Quantify the critical path from dependent WAN calls and move work to the data without weakening consistency.

Networking & Protocols · Senior

Move upload bandwidth off the API without delegating final publication or authorization to the browser.

Networking & Protocols · Staff

Bound transformation cardinality and secure decoding while using source and recipe identity in derivative cache keys.

Networking & Protocols · Staff

Explain independent edge misses and how hierarchical caching reduces eligible repeated origin fetches.

Networking & Protocols · Staff

Derive cache freshness and extension windows and choose a business-safe permitted staleness contract.

Networking & Protocols · Principal

Define policy-specific offline behavior using versioned, validated configuration snapshots and revocation limits.

Networking & Protocols · Staff

Design signed content delivery, partial resume, rollout waves and post-install health for massive downloads.

Partitioning & Distributed Data · Senior

Compute actual key movement under modulo 4 to 5, compare stable rings and logical slots, and separate owner mapping from physical migration.

Partitioning & Distributed Data · Staff

Diagnose one hot key versus a hot range or placement imbalance, then distinguish bounded-staleness read distribution from inventory-write authority.

Partitioning & Distributed Data · Staff

Choose physical placement from point-read and per-tenant ordered scan patterns, then manage whale tenants and the ordering cost of sub-bucketing.

Partitioning & Distributed Data · Principal

Specify online shard migration with snapshot and CDC boundaries, tenant-scoped write fencing, stale-router rejection, and rollback after target writes.

Partitioning & Distributed Data · Staff

Diagnose feedback between lost capacity, replica repair I/O, health checks and rebalancing, then size and prioritize recovery under a durability deadline.

Partitioning & Distributed Data · Senior

Classify storage by operations, mutation granularity, namespaces and durability contracts.

Partitioning & Distributed Data · Staff

Separate part acceptance, checksums, completion, conditional catalog publication and cleanup.

Partitioning & Distributed Data · Staff

Derive redundancy overhead, recovery thresholds, placement risks and repair IO.

Partitioning & Distributed Data · Staff

Detect latent corruption using expected checksums, scheduled scrub work and verified reconstruction.

Partitioning & Distributed Data · Principal

Protect committed manifests from stale mark-and-sweep decisions, delayed DELETE and ABA.

Caching & Performance · Senior

Recognize a read-fill/invalidation interleaving and select a freshness contract with correctly preserved ordering evidence.

Caching & Performance · Staff

Turn an expired hot key from a database stampede into bounded refill work, with explicit failure and staleness policies.

Caching & Performance · Senior

Translate a percentage-point hit-rate regression into origin demand, then diagnose workload and key-distribution causes.

Caching & Performance · Staff

Protect misses for absent keys using validation, scoped negative caching, optional membership filters and a safe creation freshness contract.

Caching & Performance · Staff

Treat cached identity as part of the authorization boundary, applying HTTP shared-cache rules to personalized responses.

Caching & Performance · Principal

Classify cache as a capacity dependency and design bounded recovery when the entire working set is cold.

Queues, Streams & Event Processing · Staff

Atomic order creation cannot make broker publication atomic. A durable publication obligation, relay recovery, and source ordering solve a new boundary.

Queues, Streams & Event Processing · Staff

Consumer offsets are progress markers, not proof of completed business effects. Atomic receipts and business identities defend separate races.

Queues, Streams & Event Processing · Staff

Replay is a separate capability with permission boundaries, history completeness, and cutover conditions. It is not just a consumer group reset.

Queues, Streams & Event Processing · Senior

Choose producer batching policies by tracing buffering and end-to-end event freshness, including quiet-partition behavior.

Queues, Streams & Event Processing · Staff

Diagnose partition-level limits and per-key skew before claiming more consumer instances add throughput.

Queues, Streams & Event Processing · Staff

Choose quarantine, repair and progress policy from per-key dependencies rather than applying a generic DLQ rule.

Queues, Streams & Event Processing · Staff

Treat retention as a replay and recovery contract, distinguishing retained offsets from recoverable historical events.

Queues, Streams & Event Processing · Principal

Design end-to-end per-tenant quotas, admission and physical isolation while preserving other workloads under shared broker saturation.

Queues, Streams & Event Processing · Senior

Explain the all-to-all exchange and distinguish input volume from shuffled bytes, with safe combinable pre-aggregation.

Queues, Streams & Event Processing · Staff

Diagnose a slow executor versus one oversized key and select speculation or workload restructuring accordingly.

Queues, Streams & Event Processing · Staff

Choose distributed broadcast versus shuffle join from post-filter size, per-worker memory and source cardinality.

Queues, Streams & Event Processing · Staff

Explain why high file counts hurt planning and reads, and how snapshot-safe compaction and writer layout repair it.

Queues, Streams & Event Processing · Staff

Describe multi-file atomic visibility through immutable data, manifests and catalog compare-and-swap, including unknown commits.

Queues, Streams & Event Processing · Principal

Separate job success from semantic and business data correctness, gate publication, and recover through versioned lineage.

Reliability & Failure Recovery · Senior

An HTTP timeout leaves the outcome unknown. Stable operation identity and a database constraint turn retries into one business decision.

Reliability & Failure Recovery · Staff

Turn RPO and RTO into explicit business promises and architecturally enforceable acknowledgment, failover and restore behavior.

Reliability & Failure Recovery · Staff

Restore an authoritative database, versioned blob store and derived index to one valid application cut using a checkpoint and protected references.

Reliability & Failure Recovery · Senior

Reconstruct PostgreSQL to a chosen point while preserving the original WAL history and legitimate post-incident commits.

Reliability & Failure Recovery · Principal

Design backup retention and clean-room restore so an administrator-level production compromise cannot erase the last recoverable copy.

Reliability & Failure Recovery · Staff

Diagnose a nine-hour restore by measuring transfer ceilings, replay, dependencies and the customer-ready critical path.

Reliability & Failure Recovery · Principal

Define realistic restore drills with varied recovery points, domain invariants, customer transactions and measured RTO.

Reliability & Failure Recovery · Staff

Find a customer-visible 40-second gap that is absent from a fast synchronous HTTP trace, using messaging context, event timestamps and population SLIs.

Reliability & Failure Recovery · Staff

Diagnose a release-specific tail regression with comparable cohorts, unbiased histograms and tracing aware of head and tail sampling.

Reliability & Failure Recovery · Staff

Detect silently dropped source updates with freshness, completeness and reconciled source-to-projection version checks.

Reliability & Failure Recovery · Senior

Derive actionable multi-window burn-rate alerts from a service-specific request SLI rather than thresholds on average success rate.

Reliability & Failure Recovery · Principal

Design independent service checks, bounded collector queues and degraded diagnostic paths without making customer requests depend on exporters.

Reliability & Failure Recovery · Principal

Lead the first ten minutes of an ambiguous production incident with customer evidence, controlled changes, safe mitigation and documented hypotheses.

Reliability & Failure Recovery · Senior

Use failure and slow-call signals, timeouts and bounded recovery probes to protect an optional dependency without inventing mandatory business outcomes.

Reliability & Failure Recovery · Staff

Follow cascading failure propagation through nested attempts, deadlines, abandoned work and redistributing failed backends, then cut the causal path.

Reliability & Failure Recovery · Principal

Define a self-contained application and state cell with safe local routing, bounded cell capacity, controlled deployments and ownership-aware migration.

Reliability & Failure Recovery · Staff

Derive shuffle-shard full-collision and partial-overlap probabilities, and use those to evaluate shared-pool noisy-neighbor protection.

Reliability & Failure Recovery · Principal

Diagnose self-sustaining failure after a trigger ends and stage recovery using goodput, reduced admission, retry control and safe backlog draining.

Capacity, Isolation & Operations · Senior

Using Little’s Law and pool budgets to explain why low CPU does not mean spare request capacity.

Capacity, Isolation & Operations · Staff

Understanding nonlinear queueing delay near saturation without turning a simplified model into a universal rule.

Capacity, Isolation & Operations · Staff

Choose which telemetry signal answers fleet health, individual decisions and distributed request paths without exploding metric cardinality.

Capacity, Isolation & Operations · Staff

Diagnose series-creation and label-churn pressure independently of sample volume and design observable safety limits.

Capacity, Isolation & Operations · Staff

Explain why delta-of-delta timestamps and XOR floats compress predictable series and when that advantage disappears.

Capacity, Isolation & Operations · Staff

Design retention, rollup dependencies, valid mergeable statistics and safe query precision across raw and coarse intervals.

Capacity, Isolation & Operations · Staff

Demonstrate the non-mergeability of local quantiles and design correct aggregation of histogram populations.

Capacity, Isolation & Operations · Staff

Protect the shared metrics store using read-work cost budgets, fairness, workload isolation and appropriate query resolution.

Capacity, Isolation & Operations · Staff

Explain bursty cgroup CPU quota enforcement and validate scheduling-related tail latency.

Capacity, Isolation & Operations · Senior

Diagnose Java GC-related tail latency using JFR events, allocation rate and live data size.

Capacity, Isolation & Operations · Staff

Measure serialization caused by global locks and redesign for per-key independent ownership.

Capacity, Isolation & Operations · Principal

Measure remote memory access and decide CPU/memory placement for database working sets.

Capacity, Isolation & Operations · Staff

Distinguish swap occupancy, active memory faults and reclaim stalls while designing memory budgets.

Capacity, Isolation & Operations · Senior

Explain why kernel-assisted file-to-socket transfer removes redundant user-space copies and its limits.

Capacity, Isolation & Operations · Senior

Separate cross-cutting edge responsibilities from domain authorization and client-specific BFF composition without creating a shared business monolith.

Capacity, Isolation & Operations · Staff

Explain fixed window burst boundaries and choose among exact or approximate sliding counts, token buckets and paced queues based on workload semantics.

Capacity, Isolation & Operations · Staff

Differentiate request arrival rate from concurrent scarce work using Little’s Law and build a feedback limiter with bounded queueing and oscillation controls.

Capacity, Isolation & Operations · Principal

Allocate scarce API work by criticality and work cost, preserve tenant fairness, and shed early rather than treat paid-user priority as unlimited access.

Capacity, Isolation & Operations · Staff

Specify different safe degraded behaviors for authentication, rate limiting, fraud scoring and feature flags with bounded freshness and auditable recovery.

Capacity, Isolation & Operations · Senior

Move ordinary configuration reads into validated atomic local snapshots, with safe bootstrap, watch recovery and differentiated staleness policies.

Capacity, Isolation & Operations · Staff

Distinguish updated service registry membership from per-client caches, existing connection pools and graceful versus unexpected backend loss.

Capacity, Isolation & Operations · Principal

Deliver versioned, semantically validated and compatible configuration to large fleets through measurable staged rollout and tested rollback.

Capacity, Isolation & Operations · Staff

Design deterministic local feature-flag evaluation, context propagation, version observability and critical kill-switch limits.

Capacity, Isolation & Operations · Principal

Reject routing configurations that pass parsing but violate weighted capacity, state ownership, residency or safe rollback conditions.

Capacity, Isolation & Operations · Principal

Use list/watch, coalesced rate-limited reconcile queues, controlled retries and idempotent external operations to recover from watch and API-server interruptions.