I work where infrastructure, delivery, and operations meet.
9 years building cloud platforms that are secure by default, observable in production, and simple enough for teams to use without a handbook.
Most of my recent work is Azure platforms serving several business units at once — shared foundations, isolated tenants, one delivery path.
The goal is never more tooling. It is a smaller, clearer operating model: secure defaults teams inherit rather than implement, releases that are repeatable and auditable, reliability that is measured instead of asserted, and cost decisions made with numbers in front of you.
What I hold to
- 01
Secure by default, not by review
Guardrails belong in the module and the pipeline, not in a checklist someone runs at the end. If the safe path is also the fast path, teams take it without being asked.
- 02
Fewer moving parts
Most platform problems are not solved by adding a tool. They are solved by removing a decision. I optimise for the smallest operating model a team can actually hold in their heads.
- 03
Reliability you can point at
SLOs, real telemetry, and incident loops that change something afterwards. Uptime claims without instrumentation are just optimism.
Where things stand
- Now
- Platform architecture for multi-cloud engagements — landing zones, Kubernetes runtime standards, and delivery golden paths.
- Next
- Architecture-led work spanning cloud strategy, platform design, and reliability practice.
- Open to
- Cloud architecture, platform engineering, and SRE roles where scale, governance, and reliability are the hard part.