About Me

I am genuinely passionate about software engineering.

Throughout my career, I’ve never forced a climb up the corporate ladder for the sake of a title. Instead, I’ve simply followed curiosity for my craft.
This approach hasn't turned me into someone who claims to know everything, but it has made me exceptionally resourceful - capable of breaking down and solving any complex system problem by turning over every stone and communicating openly with my peers.

With a Master’s Degree in Computer Science and over 12 years of hands-on engineering experience, I look at software with a broad perspective - clearly identifying the line between a reliable, isolated unit of functionality and an obscure, fragile area of logic.

When designing and writing code, I rely on two non-negotiable North Stars:

1. Absolute Certainty in Production
I am driven to be completely certain of what I ship. This pushes me to enforce rigorous automated testing and quality guardrails, leaving every codebase in a significantly better state than I found it.

2. Egoless Collaboration
Product quality relies entirely on how well a team collaborates. I have no desire or need to be the smartest person in the room; instead, I focus on the fact that I am in a room full of smart people. If I am mulling over a complex architectural boundary for too long, I talk to my peers.

What do I do and how do I do it

• What I Build & Architect: Distributed systems, robust microservice and serverless units, API gateways,
  and cloud/self-hosted deployments - extending into legacy desktop applications (WPF) when needed.
• The Languages I Write With: Python (FastAPI, Flask, Pylons), Go, and C#/.NET Core, with a proven track
  record in zero-downtime legacy modernizations.
• How I Manage State & Data: High-throughput PostgreSQL and MSSQL (relational tuning), Redis for
  caching, and MongoDB. This extends to cloud-native managed relational databases (AWS RDS, Azure
  SQL), distributed NoSQL/key-value stores (DynamoDB, Azure Cosmos DB), and scalable object storage.
• How I make the Components Talk to each other: Event-driven architectures (Kafka, RabbitMQ, AWS SNS/SQS, Azure Service
  Bus), gRPC, and GraphQL for high-concurrency, low-latency service communication.
• Where I Deploy, how do I Automate and Protect from future mistakes: Deploying across AWS, Azure, and DigitalOcean using Docker and
  Kubernetes. I actively enforce engineering guardrails by building automated CI/CD pipelines via GitHub
  Actions and GitLab.
• How I manage Access, Identity & Security: Implementing robust access boundaries using OAuth 2.0 / OIDC, JWT,
  corporate Okta integrations, and legacy Windows Identity / secure network proxies.
• What I can do pretty good but would rather avoid: Frontend. I have extensive experience in maintaining complex frontend applications utilizing modern JS frameworks (React, Angular) and doing it as safe as possible (TypeScript). But I really would rather not. So let's just frame it as "Deep Frontend awareness".

Verdict

I tried my best to paint you a clear picture of my professional portrait. Did something click with you while you checked the boxes for your current requirements? Just contact me - I will be more than glad to have a conversation about your current technical needs and see if I can help you resolve them.

I am available for permanent roles as well as high-velocity Freelance, ZZP, and Interim Contract engagements across the Netherlands.