Vetted DevOps Engineers

“AWS Cloud DevOps Engineer focused on production Linux environments, building secure CI/CD pipelines (Jenkins/GitHub) to deploy Dockerized services to AWS ECS and automating infrastructure with Terraform/CloudFormation. Strong in operational troubleshooting and scaling (CloudWatch-driven performance remediation, Auto Scaling/ELB, multi-AZ HA patterns), but explicitly does not have IBM Power/AIX or PowerHA/HACMP experience.”

“Cloud/SRE-style engineer at TDS supporting revenue-critical transportation SaaS platforms on AWS/GCP with Kubernetes. Has hands-on experience leading high-impact production work including DDoS mitigation, zero-downtime MSSQL→PostgreSQL migration using CDC, and building secure GitHub Actions + ArgoCD delivery pipelines and Terraform-based GKE infrastructure.”

“Cloud/Linux infrastructure engineer focused on high-availability AWS platforms (EKS/EC2) with strong observability and incident response ownership. Has hands-on experience building secure CI/CD (GitHub Actions/Jenkins) and Terraform-based IaC at scale, including resolving real production issues like peak-traffic latency and Terraform remote state locking; transparent about not having direct IBM Power/AIX/PowerHA production ownership.”

“Cloud/infrastructure engineer with strong production operations background across AWS, Azure, and Kubernetes, supporting 30+ enterprise workloads for ~40,000 users. Demonstrated incident leadership (hybrid AKS-to-AWS routing outage) with a reported 60% MTTR reduction, plus hands-on CI/CD (Jenkins) and Terraform-based IaC for AWS (VPC/EC2/EKS). Lacks direct IBM Power/AIX/PowerHA experience but emphasizes transferable ops and troubleshooting skills.”

“Backend engineer experienced in evolving high-scale legacy on-prem systems into cloud-native, event-driven microservices on AWS/Kubernetes (noted peak traffic ~1.5M QPS). Strong focus on reliability engineering and operational excellence—SLO-driven observability, GitOps/canary rollouts, chaos testing, and preventing cascading failures (e.g., retry-storm mitigation).”