01 / ARCHITECTURE
Software Architecture Reviews
An outside read on whether the design will hold up.
Service boundaries, data flow, failure modes, scale ceilings. Written report with prioritized findings. Typically 2–4 weeks.
Done early enough that they hold up. The studio of Kristerpher Henderson. Pattern recognition across climate science, media, big tech, and critical infrastructure.
Most teams skip
the early work.
Re-architecting under load.
Guardrails after the incident.
Do it early enough
that it holds up.
An outside read on whether the design will hold up.
Service boundaries, data flow, failure modes, scale ceilings. Written report with prioritized findings. Typically 2–4 weeks.
A risk-focused review, not a checklist.
Auth, authz, input handling, secrets, dependencies, logging. Real risk over checklist theater. Reproductions and remediation included.
Deployment, observability, and Splunk depth.
Cloud and on-prem: deployment topology, networking, observability, CI/CD, cost structure. Deep Splunk expertise is a frequent specialty.
Recurring 1:1 work with engineers and leads.
Technical decisions, career arc, leadership mechanics. Usually a recurring monthly engagement.
"I measure my own success the same way. Most people count tasks completed. I count tasks that stopped needing to exist." — Kristerpher Henderson
Email is the fastest way in. Reply within 1–2 business days. Project-based and retainer structures available.
Pennsylvania, USA · Remote-first · Weekdays ET