I build for scale: the services, the pipelines, the cloud, and the tests that guard them.

Eight years across backend engineering, cloud infrastructure, and test automation. Most engineers own one of those. Owning the chain is what removes the handoffs that slow delivery down, and it is why I end up on the problems that sit between teams.

Software. At Contentsquare I built an engineering insights platform: a data pipeline ingesting AWS, Prometheus, Jira, GitHub, and TestRail, per-merge coverage shipped through a CI CLI, and 30+ database views behind a dashboard teams actually used. Outside work I ship in Go and Python: an async certificate issuance gateway with a worker pool, atomic idempotency, and built-in fault injection; a real-time French autocorrect daemon for Linux; a full-stack spaced-repetition app on FastAPI.

Infrastructure. At ORIS I cut AWS costs 30-50% through multi-account consolidation, EKS/Karpenter reconfiguration, NAT Gateway replacement (~90% egress reduction), and off-hours shutdown, and moved a microservice fleet to Helm/ArgoCD GitOps with automated drift detection. At Contentsquare, Terraform-based Kubernetes deployments for 15+ microservices to a 99.95% availability target, absorbing traffic spikes up to 300%.

Delivery. I re-architected CI/CD into reusable GitLab templates with automatic project detection across Node.js, Python, Java, and Go, and moved runners from EC2 to an autoscaling EKS spot nodegroup so suites run in parallel under load.

Testing. I came up through test automation and it still shapes how I build: quality gates (SonarQube, Trivy) wired into the pipeline rather than bolted on, contract tests that let a microservice fleet deploy independently, end-to-end suites parallelized to cut execution time ~60%.

Most of what I learn doing this ends up in the posts on this site.