If your system works for 400 users and now needs to work for 4 million, that’s where I come in.

Moving 2K+ TB off IBM Content Manager across regulated Asset & Wealth Management infrastructure, on a plan of roughly twelve months.

Role

VP, Site Reliability Engineering (Principal Engineer) — JPMorgan Chase

Timeframe

Nov 2024 – Present

Led the migration and built an AI-powered migration application that handled the end-to-end work: legacy metadata and schema mapping, migration code generation, automated validation and reconciliation, cutover runbooks and monitoring. Delivered in 5 months against a ~12-month plan, with zero downtime, zero performance issues and 99.999% data integrity.

employer work — public metrics

Every developer already had an AI assistant; none of those assistants knew how the team actually runs services.

Role

VP, Site Reliability Engineering (Principal Engineer) — JPMorgan Chase

Timeframe

Nov 2024 – Present

An IDE toolkit of skills, MCP servers and agents for GitHub Copilot and Claude Code: single-prompt workflows for service-health checks, live-incident investigation, CI/CD build-failure diagnosis, ticket-to-PR delivery, pre-PR review, vulnerability scanning and remediation, and load testing. In my own assessment it made engineers' AI assistants roughly 10x more effective for coding and operational work. That is a qualitative judgement, not a measured metric.

employer work

Instrumenting a service with OpenTelemetry took weeks of manual work per team.

Role

VP, Site Reliability Engineering (Principal Engineer) — JPMorgan Chase

Timeframe

Nov 2024 – Present

Reusable skills that run inside developers' own AI coding assistants to adopt OpenTelemetry and manage observability events and resources. With a champion in every team, the portfolio was onboarded in under a week, and per-service instrumentation dropped from weeks to hours.

employer work — public metrics

Chronic queue misrouting had stretched mean incident resolution to around 50 days.

Role

VP, Site Reliability Engineering (Principal Engineer) — JPMorgan Chase

Timeframe

Nov 2024 – Present

Redesigned triage and routing and layered SLO and error-budget governance on top. MTTR fell from ~50 days to ~60 hours (~95%), and P1/P2 incidents were nearly eliminated.

employer work — public metrics

Launch-day traffic across three regions is not a load test you can rerun.

Role

Staff Site Reliability Engineer, Streaming Platform — Warner Bros. Discovery

Timeframe

Mar 2023 – Oct 2024

A self-service load-testing platform validated Max at 3M concurrent users across US, LATAM and EMEA, with 0 P0 incidents on global launch day. I also owned Olympics 2024 readiness: 25 services pre-scaled, 100% uptime through peak traffic.

employer work — public metrics

Observability coverage grew by hand, team by team.

Role

Senior Site Reliability Engineer — Smarsh

Timeframe

Jul 2021 – Mar 2023

A Terraform-based Monitoring-as-Code approach that doubled observability coverage and improved time-to-alert by 80%, tracked against DORA metrics.

employer work — public metrics

Every client account needed observability, and dashboards and monitors were created by hand.

Role

SRE / DevOps Engineer (New Relic SME) — Mindtree

Timeframe

Dec 2018 – Jul 2021

Integration tooling that monitored 95% of infrastructure, plus Terraform-automated dashboards and monitors that cut deploy time by 75%.

employer work — public metrics