EKS delivery
Docker Compose on a laptop→repeatable delivery on shared EKS
I owned the delivery path and reviewed and merged three platform cutover changes teammates wrote, covering IAM, ingress, and secrets.
New York, NY · Remote or hybrid · Open to platform roles
Platform & DevOps Engineer
I have operated AWS and Kubernetes platforms at scale for analytics and healthcare-data teams, with Terraform-managed infrastructure and GitOps delivery.

I’ve replaced manual provisioning and deployments with self-service infrastructure and repeatable pipelines. Availability and error-rate alerts give teams a clearer view of what’s happening in production.
That work also includes AI-assisted review workflows I built to surface potential issues in infrastructure changes. Engineers verify the findings and decide what gets merged.
EKS delivery
I owned the delivery path and reviewed and merged three platform cutover changes teammates wrote, covering IAM, ingress, and secrets.
Serverless
Separate IAM roles per function: the public path can read, never write.
AI tooling
It caught an RDS instance that never set publicly_accessible. It was also confidently wrong about an IAM policy, and I overrode it — both cases in full →.
Open to platform and infrastructure roles.