How to Accidentally Become a Platform Engineer
I did not set out to become a platform engineer. Here’s how it happened anyway.
Your developers need a database, a storage bucket or a test environment, so they open a ticket and wait. I build internal developer platforms that let them request it in Git and have it running in minutes, with the guardrails your platform and security teams need.
I’ve written software since 2005 and moved into platform engineering in 2016. At Mendix, I drove the design direction of our internal developer platform, built on Argo CD and Crossplane, which dozens of engineering teams use to manage their own AWS infrastructure. We’re now applying what we learned there to Mendix customers. I’m building a multi-tenant Crossplane platform that manages databases and storage for thousands of them.
Before that, I built cloud messaging on Google Cloud and Kubernetes at bol.com, developed clustered payment systems at Entersekt, and ran my own software consultancy.
I have about 10% vision and work with text-to-speech and magnification. Living with that has made me a problem solver and an innovator at heart. I’ve learned to find a way through any problem, and to see solutions where others might lack the vision. As I like to say: I literally do Kubernetes with my eyes closed.
I work with Kubernetes, GitOps, Argo CD, Crossplane, AWS, Go and Terraform. If your developers wait days for infrastructure, or your Kubernetes setup has outgrown the people who look after it, I’m happy to talk.
I did not set out to become a platform engineer. Here’s how it happened anyway.
I believe developers should provision and manage their own infrastructure through simple APIs, with the guardrails built into the API itself. My platforms use Git as the front door. Developers declare what they need, Argo CD applies it to Kubernetes, and Crossplane turns the platform team’s standards into APIs that create the cloud resources behind it. Teams get a database or a bucket without learning AWS, and the platform team keeps control of cost, security and compliance.
At Mendix, I design and evolve a GitOps-based internal developer platform that enables engineering teams to deploy and manage applications seamlessly in the cloud.
I drove the design direction of the platform, built on Argo CD and Crossplane. Dozens of engineering teams use it to manage their own AWS infrastructure, with guardrails that keep it consistent and secure.
We’re now applying what we learned there to Mendix customers. I’m building a multi-tenant Crossplane platform that manages databases and storage for thousands of Mendix customers.
At bol.com, I was responsible for developing and maintaining the organisation’s cloud messaging infrastructure, built on GCP Pub/Sub and Kubernetes.
At Entersekt, I was responsible for designing and developing highly available, clustered applications in the online banking and payments space.
At Netelek, I was responsible for developing rich, responsive Java-based business applications for the utilities industry.
At SixThirty, my own freelance software consultancy, I developed rich, web-based Java business applications for various clients.
At Memorphic, I was responsible for developing rich internet applications with a Java backend.
At Prezence, I developed online marketing, customer relations, and profiling tools in the entertainment and advertising sectors.
At Silicon Overdrive, where I started my career, I focused on software development, database design, and web application development.