Architecture & reliability review
Two to three weeks. I read the code and the dashboards, interview the people on call, and write a report that ranks your failure modes by likelihood and cost, with a design for each fix.
Clients
Work with me
I help teams whose backend has started to fail in ways that are hard to explain: messages that go missing, retries that turn a blip into an outage, queues that hide trouble until they don't, migrations that never finish.
Hard backend builds
Real-time delivery, event-driven pipelines, multi-tenant data, payment and ledger flows. I design it, build the critical path with your team, and leave it documented and owned.
Second opinion
A two-hour session on one design decision before you commit to it. You bring the diagram; I bring the questions your outage will ask later.
How it starts
- 1. Email me two paragraphs about the system and what's hurting.
- 2. A 30-minute call to see if I'm the right person.
- 3. A fixed-scope written proposal. No retainers, no surprises.
I take on a small number of engagements at a time, alongside my full-time role.