Job Description

Key Responsibilities

• Design, implement, and maintain CI/CD pipelines for product platforms and microservices.
• Build and manage cloud infrastructure using Infrastructure as Code (IaC).
• Support and optimize containerized workloads and microservices platforms.
• Ensure high availability, scalability, and reliability of platform environments.
• Implement monitoring, logging, and alerting to ensure platform observability.
• Collaborate with backend and frontend engineering teams to improve developer experience.
• Automate operational workflows to reduce manual effort and improve system stability.
• Drive best practices around security, performance, and cost optimization.
• Participate in incident response, root cause analysis, and continuous improvement initiatives.

________________________________________

Core Technical Skills

• Strong experience with CI/CD tools (e.g., GitHub Actions, GitLab CI, Azure DevOps, Jenkins).
• Hands-on experience with cloud platforms (Azure and/or AWS).
• Experience with containerization and orchestration (Docker, Kubernetes).
• Proficiency in Infrastructure as Code tools (Terraform, ARM, CloudFormation, or equivalent).
• Solid understanding of Linux systems and networking fundamentals.
• Experience with monitoring and logging tools (Prometheus, Grafana, ELK, or cloud-native tools).
• Familiarity with microservices architectures and deployment strategies.
• Scripting experience using Bash, Python, or PowerShell.
• Knowledge of security best practices, secrets management, and access control.

________________________________________

Platform Engineering Mindset

• Strong ownership mindsetcomfortable owning environments end-to-end.
• Automation-first approach to infrastructure and operations.
• Product mindset focused on reliability, scalability, and long-term maintainability.
• Ability to identify bottlenecks and proactively improve platform resilience.
• Collaborative mindset, working closely with engineering and architecture teams.

________________________________________

What This Role Is NOT

• Not a client-facing or consulting role.
• Not a purely support or ticket-driven operations role.
• Not limited to manual deployments or ad-hoc infrastructure tasks.