Platform Engineer
Role details
Job location
Tech stack
Job description
(EKS, AKS, GKE) - deploying services, troubleshooting, and maintaining system health. Implement resilience and reliability features such as autoscaling, load balancing, observability, monitoring, and alerting. Drive incident response and prevention: participate in on-call rotations, run post-incident reviews, and continuously improve stability. Mentor teammates on cloud automation and platform engineering best practices. Collaborate across the engineering lifecycle: provide feedback in design/code reviews, document key decisions, and engage with stakeholders. Own and resolve complex cross-domain issues spanning infrastructure, networking, databases, and application code. Requirements (Must-Have) 7+ years in platform engineering, site reliability, or DevOps roles. AWS proficiency: IAM, EKS, Route53, S3, SQS, EC2, and related services. Kubernetes expertise: deploying, scaling, and troubleshooting workloads. Terraform expertise: infrastructure as code, reusable modules, workspaces, state
Requirements
migration, Strong experience implementing and maintaining CI/CD pipelines with GitHub Actions and ArgoCD. Proficiency with Linux, networking, and systems architecture. Hands-on experience with containerization (Docker, Kubernetes). Proficiency with Git and modern software development workflows. Preferred / Nice-to-Have Certifications: AWS Certified Solutions Architect Associate, Certified Kubernetes Administrator (CKA). Experience with Ansible (playbooks, roles). Multi-cloud exposure (Azure, GCP). Experience running self-hosted GitHub ARC runners in Kubernetes. Familiarity with platform-as-a-product practices. Personal Attributes / Soft Skills Excellent written and spoken English. Strong collaboration and teamwork skills. Comfortable mentoring and coaching less experienced engineers. Effective problem-solving, analysis, and reasoning abilities. Detail-oriented with strong time management and organizational skills. Comfortable working in Agile environments and with pair programming. Why