System Design
claim element
Shaping services, contracts and data flows before code exists.
cited in: 7 proving documents · 2 companies
proving documents
Founding an analytics service by moving reporting off the transactional database
Founded a new reporting service that separates heavy analytical reads from the transactional database, resolving indicator timeouts, framing the OLTP-vs-OLAP trade-off, critically reviewing the architecture decision, and building the walking skeleton and its data layer.
Responding to a production incident with the missing architecture decision, not just a patch
Root-caused a customer-blocking production incident to an undocumented architecture assumption, rebuilt the affected consumer with a post-mortem, an ADR, and business-rules documentation, then, after rollout exposed a database deadlock, diagnosed it to a Kafka partitioning mismatch and replaced silent message loss with retry, a dead-letter queue, and per-user serialization.
Designing a single computation path for a cross-service metric
Two services independently calculated the same customer-facing metric, causing inconsistent data. I redesigned the architecture so only one service owned the calculation while every other service simply signaled stale data.
Designing the safety guarantees for an AI-orchestrated cleanup, not just automating the grind
Designed and built a Claude Code skill that safely orchestrates parallel agents to remove expired feature flags across a shared frontend and two backend services, closing a 36-subtask cleanup epic (24 feature flags plus 3 expired product tours and a legacy page, ~3,100 lines removed in one commit), with disjoint-file-set batching so agents can't collide, diff-against-baseline validation instead of absolute pass/fail, and an enforced two-repository deploy order so infrastructure changes can never precede the code that depends on them.
Synchronizing a Cross-Service Data Edit Atomically
Made an edit to an organizational node in the asset hierarchy propagate consistently across denormalized copies in seven tables and two services, via a single atomic transaction with post-commit events, the work that made me the team's reference for cross-service synchronization.
Changing where a new state is handled, instead of teaching eight read paths about it
A new platform-wide asset state was specified as a rule that eight different read paths had to learn. I proposed applying it once at the write boundary instead, removing the asset from route scope and restoring it on reactivation, which made most of the original scope unnecessary and left the counters, reports, app sync and adherence untouched.
Introducing a Design System where none existed
Identified the absence of frontend standards, proposed a Design System, built it from scratch and taught the team how to adopt it.
exercised at