Backend Engineering

Design stable resource-oriented endpoints with deliberate error contracts and pagination.

Design stable resource-oriented endpoints with deliberate error contracts and pagination.

Accept retried mutations gracefully by keying operations so duplicates return the original result.

Run two versions in parallel, observe usage, and sunset safely with real telemetry.

Normalize enough to stay consistent, denormalize deliberately where reads demand it.

Normalize enough to stay consistent, denormalize deliberately where reads demand it.

Normalize enough to stay consistent, denormalize deliberately where reads demand it.

Find top offenders from real traffic, read plans, add targeted indexes, verify improvements.

Expand-contract deployments so schema changes ship without locking tables or breaking running code.

Decide what caches where (CDN, app, Redis) and how entries die so staleness stays bounded.

Queue async work with retries, dead-letters, and observability so failures surface instead of vanishing.

Cookies, rotation, and revocation done right for server-rendered apps.

Parse, don't validate: coerce untrusted input into typed values once at the edge.

Strong vs bounded-staleness vs eventual mapped to business harm scenarios, not fashion.

Residency, replication lag, failover semantics, and write-conflict strategy before the second region exists.

Command/event separation, upcasting discipline, and projection rebuild strategies that survive year three.

Introduce breaking API improvements while every existing client keeps working.

Cut p95 query times on a growing table set before the next traffic spike.

Process money mutations with idempotency guarantees and clean audit trails.

Consistency models chosen by harm math with multi-region topology that survives evacuation.