Teams & systems that
hold up under load.
The systems your business runs on — and the team that runs them.
Twelve years, from first commit to steady state.
How an engagement unfolds,
start to finish.
From setting direction and hiring, through building the systems, to securing and running them in production.
Fractional tech lead / advisory
define goals, set strategy
Hiring & team building
interview loops, bar-raising
Building from the ground up
0→1 greenfield systems
Backend architecture & microservices
event-driven, DDD
Legacy → cloud migrations
monolith → EKS / Terraform
Engineering processes & velocity
CI/CD, faster TTM
Performance & scalability audits
high-load, latency
Something else?
let's scope it
Security & compliance
SOC2, data protection
FinOps & cost optimization
right-sizing, spot, budgets
Case studies.
A few systems I've shipped.
Cutting a $150k/mo AWS bill by 6% — without touching SLAs
Spot, right-sizing and budget guardrails on a B2B SaaS platform.
Lifting a legacy monolith into EKS, account by account
A staged lift-and-shift to a multi-account, highly available architecture.
A billing engine that survives enterprise contracts
ACID-safe ledgers and reconciliation for high-volume transactions.
From 2-month demo setups to 2 weeks: a CI/CD overhaul
Automated provisioning that accelerated delivery across teams.
Notes on building systems.
All writing →Cutting a $150k/mo AWS bill by 6% — without touching SLAs
What actually moved the needle on FinOps, and what didn't.
From 2-month demo setups to 2 weeks
Treating environment provisioning as a product.
Lifting a legacy monolith into EKS, account by account
A migration playbook that didn't page anyone at 3am.
Twelve years across billing systems and B2B SaaS — Rust and TypeScript on the backend, AWS and Kubernetes underneath. I've led migrations off legacy monoliths, built teams from the first hire, and kept enterprise SLAs intact while cutting cloud spend.
Have a system that's
too important to break?
Tell me what you're building. I reply within a day.