Cloud provisioning as a product, for five hundred engineers
A multi-year engagement embedded with a fintech’s developer-experience platform team, spanning its transition to a public company. The mandate was to stop product teams from having to become infrastructure engineers: cloud resources declared in a simplified YAML schema, processed during CI/CD by a distributed internal-developer-platform backend, and surfaced through a React portal exposing every pipeline, status, metric, log and best-practice guide for each system provisioned through it.
Architected and shipped the abstractions engineers actually consumed — S3 with bucket policy grants, object eventing to SNS, SQS and Lambda, and lifecycle rules; ElastiCache Redis and Memcached with flexible cache types, master/replica topologies, IAM users and controlled version upgrades; and managed OpenSearch with domain security, index specification and master/replica configuration, which turned the company’s help-desk search from a bespoke backend into a highly available multi-index platform with a step change in performance for customers and support staff.
Also led the distributed architecture design and cross-team engagement that let SME platform teams — machine learning, networking, security — own provisioning of their own resources against published specifications while remaining components inside the core platform.