Self-Service Platform @ project44

The problem: infrastructure as a bottleneck

When every team needs the platform team to hand-provision infrastructure and wire up deploys, the platform team becomes the bottleneck and every team reinvents the same wheel slightly differently. The fix isn't more tickets — it's paved roads: standardized, reusable building blocks teams can self-serve.

The golden path

I built the reusable layer that sits between raw AWS/Kubernetes and the product teams:

• Terraform modules — parameterized infrastructure primitives teams compose instead of writing from scratch.
• Helm charts — standardized service packaging with sane, safe defaults.
• Argo CD ApplicationSets — GitOps delivery that templates deployments across clusters and environments.
• GitHub Actions templates — reusable CI so every team's pipeline follows the same guardrails.

Observability I own

Availability doesn't come from hope — it comes from seeing problems before users do. I run the Prometheus + Grafana layer as dashboards-as-code with SLOs and tuned alerts, holding 99.95% service availability.

• SLO dashboards make error budgets visible, so teams know when they can ship fast and when to slow down.
• Alert tuning keeps the signal-to-noise high — pages mean something.
• Dashboards live in version control, reviewed like any other code.

AI-assisted operations

I work AI-first. Claude Code runs as a daily agent in the infrastructure repos — but on a strict plan → generate → review-every-diff discipline. The judgment stays human; the toil gets automated.

• Auto-generated runbooks from incident timelines, reviewed and adopted as the team template.
• Alert summarization and assisted root-cause analysis during incidents.
• Custom skills and MCP integrations for repetitive infrastructure tasks.