TypeScript Developer DBMS Concepts Interview Guide

At Read Committed, each statement receives a new snapshot, so later statements can see commits made in between. Higher isolation changes the guarantees and may require retrying serialization failures. Choose isolation from the business invariant, not from an assumption that every transaction freezes all reads.

Check your understanding: Interleave two sessions and document the snapshots each statement sees.

Common trap: Treating transaction atomicity and isolation as identical.

Concept reference: PostgreSQL: transaction isolation

An index is an option, not a command. The planner considers selectivity, statistics, table size and access cost. Read estimated and actual rows, filters and scan types before changing indexes. EXPLAIN ANALYZE executes the statement, so use safe data and transaction handling for writes.

Check your understanding: Compare estimated and actual row counts on representative data.

Common trap: Forcing an index without measuring the full query.

Concept reference: PostgreSQL: reading EXPLAIN plans

Check the grain of each table and whether the join creates several rows for one order. Aggregate at the intended business grain before joining, or use the correct relationship and key. Reconcile totals using a tiny fixture containing multiple child rows and an unmatched parent.

Check your understanding: Use one order with two child records and verify the total remains correct.

Common trap: Using DISTINCT as a universal repair for a wrong join.

Concept reference: PostgreSQL: reading EXPLAIN plans

No. Type annotations describe compile-time expectations; they do not validate a network response. Start external data as unknown, validate its shape and constraints, and only then expose a trusted application type. Distinguish malformed responses from legitimate empty data so callers can handle both.

Check your understanding: Feed a missing field, wrong type and unexpected enum value through the boundary.

Common trap: Using a type assertion as a runtime security check.

Concept reference: TypeScript: narrowing

Use a union with a literal status field and data appropriate to each state. Narrow by that field before reading the payload. An exhaustive switch can make adding a new state a compile-time task rather than leaving forgotten branches. Runtime input still needs validation before it enters the union.

Check your understanding: Add a new status and ensure all rendering branches must handle it.

Common trap: Several independent booleans that allow success and failure simultaneously.

Concept reference: TypeScript: narrowing

The assertion suppresses a compiler concern but adds no runtime check. Handle the absent user explicitly, then narrow the value before use. Preserve the distinction between not found, forbidden and unavailable at the service boundary without leaking another user’s data.

Check your understanding: Test an absent record and an authenticated caller who does not own it.

Common trap: Assuming authentication makes every looked-up record accessible.

Concept reference: OWASP: authorization checks

First, identify technical constraints and define measurable service objectives. Next, trace values through scope, task queues, type boundaries and observable side effects. Contrast architectural trade-offs across write cost, read latency, consistency and operational complexity, explicitly mitigate the risk of aggregate metrics hide the affected route, device or dependency, and confirm system stability using segmented service-level indicators, an exemplar trace and an alert threshold.

Common trap: Reaching for a specific library or framework before defining constraints, failure envelopes, and automated verification criteria.

Prioritise the failure mode exhibiting the highest user blast radius and lowest observability. Formulate an explicit containment boundary, implement idempotent retries with jitter, and establish an automated rollback threshold. Verify resilience through load-test results, retry counts and a measured cost estimate.

Common trap: Relying on passive monitoring dashboards without defining explicit error-budget alerts, rollback triggers, and verified recovery procedures.

Structure the response using Context-Decision-Tradeoff-Result: articulate the business and technical constraints, compare viable alternatives, explain the implementation (trace values through scope, task queues, type boundaries and observable side effects), and document the accepted trade-off. Provide concrete proof: an explain plan, concurrency test and recovery verification.

Common trap: Speaking only in high-level abstractions or team accomplishments without detailing your direct implementation decisions, trade-offs, and measured results.

Formulate a falsifiable hypothesis from observable telemetry before altering configurations. Then inspect task ordering, retained references, type assumptions and a minimal runtime reproduction. Isolate the defect to the smallest reproducible boundary, validate root cause with evidence, and confirm full resolution using a compatibility contract, expand-and-contract rollout and rollback rehearsal.

Common trap: Applying speculative fixes or restarting services blindly without establishing an observable signal connected to a falsifiable hypothesis.

Produce a typed boundary test with an event-order trace and bundle comparison. Document baseline assumptions, technical mechanism (trace values through scope, task queues, type boundaries and observable side effects), rejected alternatives, bounded failure envelopes, and deterministic pass criteria. Supply reproducible verification via a compatibility test matrix and a staged rollout metric.

Common trap: Presenting architecture diagrams or slides lacking automated unit/integration tests, observable metrics, or automated rollback configurations.