Senior platform engineer · SRE · MLOps

I take over infrastructure nobody has mapped end to end, make it safe and observable, and turn it into code teams can ship on.

Five years on production platforms where downtime costs money: a stock-exchange trading system, a crypto exchange, a multi-tenant retail platform and a global reinsurer. Today I own infrastructure workstreams on the AI platform of a global mobility company, where I migrated an ML estate off self-managed Kubeflow onto Databricks and built the private DNS behind PrivateLink-only access. On the retail platform I led the DevOps team, and one migration I planned and ran cut a tenant’s running cost by about 80%.

  1. ~80% lower running cost for a tenant I migrated Measured
  2. 1,500+ models moved off Kubeflow onto Databricks Shipped
  3. 8 regions on the hardened model-deploy path Shipped
  4. 3.19M audit-log events behind one access cleanup Shipped

What I work with

Everything here is on a project below.

Cloud
AWS (multi-account networking, PrivateLink, Route 53, Lambda, API Gateway, Step Functions, ECR), GCP, Azure
Infrastructure as code
Terraform, OpenTofu, Terragrunt, Atlantis, Ansible, CloudFormation
Containers
Kubernetes on EKS (clusters and workloads), GKE and AKS, Helm, Docker, Harbor
CI/CD
GitHub Actions, GitLab CI, Jenkins, Azure DevOps, release-please
Reliability
SLO and SLI design, Prometheus, Grafana, Alertmanager, CloudWatch, Datadog, PagerDuty, disaster-recovery design
Security
Cloud security audits, IAM and KMS, HashiCorp Vault, OIDC and workload identity federation, Keycloak, Trivy, distroless images
ML platforms
Databricks (Unity Catalog, Asset Bundles, cluster policies), MLflow, SageMaker, Kubeflow, Kafka, Spark Structured Streaming
Data
PostgreSQL (Patroni, HAProxy, Keepalived), MySQL, Delta Lake, BigQuery, Liquibase
Languages
Python, Bash, Go, TypeScript, Groovy
AI-assisted work
Claude Code with custom skills and sub-agents, MCP integrations with Jira, Slack and GitHub, automated pull-request and Terraform-plan review, local models through llama.cpp

Problems I take on

Evidence

  • Shipped built and in use
  • Measured counted or benchmarked
  • Found a risk discovered through evidence
  • Target a design objective
  • Plan proposed, not yet done
  1. 3.19M

    audit-log events checked to cut an account IP allowlist from 37 entries to 28, each with a named owner. Details for 3.19M

    Shipped
  2. p99 91 ms

    on a reproduced real-time feature path, with 99.4% of rows inside the 500 ms target. Production ran on the 8.1 s micro-batch path. Details for p99 91 ms

    Measured
  3. 4

    platform defects exposed by my first end-to-end deploy from the Unity Catalog model registry, including model settings the MLflow deploy path dropped without an error. Details for 4

    Found
  4. 141

    catalogs moved to a new data-governance group through reviewed Terragrunt changes, with import blocks bringing drifted resources under code. Details for 141

    Shipped
  5. 79

    repositories checked for access before a tenant launch step could run. Details for 79

    Shipped
  6. 1 h

    recovery time objective in the multi-region serving design. A design target, listed as one. Details for 1 h

    Target
  7. 1,500+

    registered MLflow models, most of them per-city variants of one family, moved to Unity Catalog aliases in the migration. Details for 1,500+

    Shipped
  8. 80+

    Dependabot vulnerability alerts closed across two ML monorepos. Details for 80+

    Shipped

Selected work

  1. Private DNS for a PrivateLink‑only data platform

    The platform rule said no public control-plane endpoints. I built the private DNS that makes the rule work in every region and account, traced a missing return route, and cut the account allowlist to entries with owners.

    Shipped AI platform of a global mobility company

  2. Reliability for multi‑region model serving

    A dual-registry image path forced by a platform limit, a deploy path for eight regions with no lost version commits, a recovery design with explicit targets, and the alerting chain behind it.

    Shipped AI platform of a global mobility company

  3. Retailer launches as plan‑first workflows

    Onboarding changes for three retailers across 24 service repositories, an access module that finds missing repository access before a launch step runs, and a tenant migration that cut its running cost by about 80%.

    Shipped Multi-tenant e-commerce platform

  4. A highly available PostgreSQL platform

    Patroni for failover, HAProxy and Keepalived for one stable address, Ansible for repeatable nodes, and alerts on replication lag and failover events.

    Shipped Self-managed PostgreSQL, a DataArt project

  5. A migration built from a full inventory

    A legacy Kubeflow estate, from 51 pipelines to more than 1,500 registered models, inventoried and scored before anything moved, then migrated to Databricks in waves.

    Shipped AI platform of a global mobility company

How I work

  1. Everything as code

    One OpenTofu and Terragrunt repository, applied through Atlantis after review. Private networking, Databricks governance and the serving path all live there.

  2. Read-only before write

    I start with an inventory and an audit: what exists, what is exposed, who has access, what is patched. That first pass found an allowlist of 37 entries with no owners, and 51 Kubeflow pipelines nobody had listed.

  3. Every change through review

    Plans are visible before they apply. I review the platform’s Terraform as a merge gate, and my own changes go through the same gate.

  4. Decisions in writing

    I write the team’s ADRs on security, recovery and platform limits. The recovery design with a one-hour RTO target is one of them, and it was approved.