What you will do
•    Design and maintain AWS infrastructure using services like EC2, S3, VPC, Lambda, CloudFormation, and ECS/EKS.
•    Build and manage CI/CD pipelines using tools like Jenkins, GitLab CI, or AWS Code Pipeline.
•    Automate infrastructure provisioning and configuration using Terraform, Ansible, or CloudFormation.
•    Monitor system performance and troubleshoot issues using CloudWatch, ELK, or Prometheus.
•    Implement security best practices and ensure compliance with cloud governance policies.
•    Collaborate with developers to streamline code integration and deployment.
•    Maintain documentation for infrastructure and processes.

What skills you need
•    Strong hands-on experience with AWS services.
•    Proficiency in scripting languages like Python, Bash, or PowerShell.
•    Experience with containerization (Docker) and orchestration (Kubernetes or ECS).
•    Familiarity with Git, version control, and branching strategies.
•    Knowledge of networking, security, and cloud cost optimization.
•    Experience with tools like Jenkins, GitHub Actions, GitLab CI/CD.
•    Knowledge of tools like Terraform or AWS CloudFormation.
•    Basic scripting for provisioning environments.
•    Git basics: branching, merging, conflict resolution.
•    Familiarity with Prometheus, Grafana, ELK Stack, or similar.
•    Understanding DNS, load balancers, firewalls.
•    Proficiency in Bash, PowerShell, or Python for routine tasks.

What skills you will learn
•    Hands-on with AWS, Azure, or GCP environments.
•    Creating and maintaining virtual machines, storage, etc.
•    Basic Docker knowledge (creating images, running containers).
•    Exposure to Kubernetes or OpenShift preferred, but not mandatory.
•    Regular patching, config updates, version management.
•    Handling access controls and secrets rotation.
•    Quickly responding to failures in lower environments.
•    Documenting steps taken and contributing to RCA.
•    Automating common routines and jobs (e.g., backups, cleanups).
•    Working closely with developers and QA teams.
•    Clear communication of environment changes or issues.
•    Writing SOPs, playbooks, environment details.
•    Diagnosing issues independently or with cross-team input.