I help engineering teams get cloud infrastructure under control; reliable, cost-predictable, and out of the way so engineers can ship. Infrastructure that scales with the business, keeps costs predictable, and enables engineers to move fast without breaking production.
I typically work with companies of 10 to 1000’s employees where complexity has outgrown ad-hoc solutions, and infrastructure needs experienced ownership.
How I Add Value to Teams
I step into teams as a senior platform or infrastructure engineer and take responsibility for hard problems, including:
- Designing and owning cloud architecture for production workloads
- Teams I’ve worked with typically reduce cloud spend while removing surprise bills
- Turning cloud infrastructure into a self-service platform for engineers
- Leading complex migrations with minimal downtime and operational risk
- Improving reliability, observability, and operational maturity
- Mentoring engineers and raising the overall infrastructure bar
This is hands-on work. I work directly in accounts, repositories, Kubernetes clusters, and CI/CD pipelines. I review code, debug incidents, and help teams make better long-term decisions.
Typical Situations I’m Brought Into
Teams usually involve me when they are:
- Migrating and want to avoid costly architectural mistakes
- Already in Cloud environments but are struggling with cost, reliability, or complexity
- Scaling rapidly and feeling infrastructure becoming a bottleneck
- Inheriting legacy platforms that nobody fully understands anymore
- Building or maturing an internal developer platform
- Dealing with high-risk infrastructure projects that need senior ownership
Experience & Background
I have over a decade of experience building and operating large-scale infrastructure across startups, scale-ups, and enterprises.
Highlights include:
- Tech lead roles for platform and infrastructure teams
- Leading large container platform migrations (400+ services, minutes of downtime)
- Advising engineering leadership on strategy, architecture and cost management
- Owning cloud cost management, forecasting, and architectural decisions
- Designing and operating Kubernetes, data, and high-availability systems
- Deep experience with Cloud environments, Terraform, Kubernetes, networking, and security
- Background in high-scale data platforms and HPC environments
I’ve worked with organizations including the largest retailers, research institutions, and energy and sustainability companies.
How I Work
I optimize for impact and clarity.
I prefer short discovery conversations over long proposal cycles. After understanding the situation, I’ll give a direct recommendation on what would help most. Sometimes that means working together. Sometimes it means being upfront that I would not be a good fit.
For larger or higher-risk work, I usually start with a short assessment phase. The outcome is a concrete plan with clear priorities, risks, and next steps, so both sides know what success looks like before committing further.
How Engagements Work
I work on a project basis with clear scope and outcomes.
Every engagement starts with a paid scoping phase (typically 2-4 weeks). The deliverable is a project brief: scope, approach, success criteria, and timeline. You review it, we align on terms, then implementation begins.
This structure exists because it works:
- You get clarity before committing to larger investments
- I bring focused expertise to bounded problems
- We both know what success looks like upfront
It also means our working relationship is structured as project-based from day one — which matters given current Dutch labor regulations (WetDBA). I define how and when I work. You define what needs to be solved.
Discuss your cloud infrastructure
A short conversation to see how I can help your team.