ORIGINAL: "Responsible for migrating legacy services to new infrastructure." VERSION A — IMPACT-FIRST Reduced infrastructure costs by 34 percent and improved p99 latency from 850ms to 210ms by migrating 7 legacy services from on-prem to AWS ECS Fargate. VERSION B — SCALE AND COMPLEXITY Led migration of 7 production services handling 12M daily requests from on-prem VMs to AWS ECS Fargate, coordinating across 4 teams with zero downtime. VERSION C — INITIATIVE AND OWNERSHIP Identified $180K annual savings opportunity in legacy hosting; proposed and owned migration of 7 services to AWS ECS Fargate, delivered in 5 months under budget. ATS KEYWORDS USED: AWS, ECS, Fargate, migration, infrastructure, latency, production, services KEYWORDS TO ADD: Terraform, CI/CD, observability, cost optimization, SRE WHAT WAS WEAK: "Responsible for" is passive and signals duty, not result. No metric. No specific technology — ATS scanners need exact tool names. "Legacy" and "new" are vague. PICK GUIDE: - Use A for FAANG, fintech, or any data-driven culture — they want results first. - Use B if the target role emphasizes scale — staff engineer, platform roles, high-traffic companies. - Use C for senior, principal, or staff roles where ownership is the bar.