- Architected and owned end-to-end CI/CD infrastructure for a production game studio, partnering directly with the CTO and platform teams
- Designed and maintained an enterprise Jenkins platform serving 50+ developers, authoring custom Groovy pipelines and Python automation
- Implemented a targeted failure-alerting system that identified responsible developers and surfaced relevant errors automatically
- Provisioned cloud-native AWS infrastructure including EC2 Auto Scaling and S3-based artifact storage, with a workload-aware instance-provisioning system
- Established artifact lifecycle management across S3 and Artifactory, including retention and archival strategy
- Maintained and extended a large-scale Python-based CI/CD platform across multiple simultaneous productions
- Designed automated infrastructure maintenance and resource segregation, improving reliability at scale
- Coordinated build and release workflows with engineers across multiple studios and time zones
- Supported the full production lifecycle for two AAA titles: Call of Duty Black Ops Cold War and Call of Duty Vanguard
- Delivered server-side tooling bridging QA and backend engineering workflows
- Built C# instrumentation for scene-change monitoring and load-time measurement
- Contributed to shipping War Commander: Rogue Assault
Hands-on infrastructure practice, ongoing. Building depth in the areas my production experience hasn't reached yet, deliberately and out loud rather than papering over the gap.
Writing VPC networking from scratch in Terraform (no modules): subnets, route tables, NAT gateway, IGW, wired and verified by hand rather than templated.
Working through EKS fundamentals: control plane responsibility boundaries, IRSA for pod-scoped IAM permissions, and how VPC CNI differs from overlay networking like flannel.
Practicing against LocalStack and a self-hosted homelab server rather than a production AWS account. This is real practice, not production experience, and I'd rather say that plainly than imply otherwise.