Designs by Duhart

Designs by Duhart · work inventory

Twenty-eight projects, ranked for one job

Distributed Systems Engineer — Google / Spotify / financial institution. Scored against what those loops actually test, not against how impressive it looks.

The rubric — weight × rating, max 120

Canonical DS primitives ×5Partitioning, event logs, idempotency, fan-out, backpressure
Production evidence ×4Deployed, measured, runbooked, failure modes named
Concurrency correctness ×4Races found, fixed, and tested for
Scale artifacts ×3Shard keys, consumer groups, TTLs, hot keys
Language fit ×3Go, Java, Python, C++
Contract discipline ×2OpenAPI / AsyncAPI / protobuf, CI-enforced
Written communication ×2Design docs stating trade-offs and costs
Frontend / mobile ×1Real work; not what this role hires on

Each project is rated 0–5 per signal. Ratings are a hiring judgment, not a measurement — treat differences under about five points as ties.

Tier S

95+

Lead with these. They are the interview.

Within 5 points of 120 — that is noise. GlobalChat edges the rubric on production evidence and breadth. The Activity Graph leads anyway because it is the canonical systems-design question with every trade-off already written down. Open with it; bring GlobalChat as proof you have carried something this size in production.

Tier A

75–94

Strong support — infrastructure, ML platform, media.

Tier B

60–74

Real systems work, narrower interview surface.

Tier C

under 60

Breadth and depth-of-craft. Mention, don’t lead.

Reading paths

Google1 → 3 → 4 → 11
Spotify1 → 21 → 8 → 6
Bank2 → 12 → 16 → 11

Supporting documents

Résumé bulletsPre-sorted by employer, with quotable numbers.Interview storiesEight stories with the follow-ups each invites.The full index documentThe source inventory in long form.