SRE Tools Engineer

Role & responsibilities

DevOps Engineer Azure, Automation, Splunk & Dynatrace

Role Overview

We are seeking a hands-on DevOps Engineer with strong experience in CI/CD, Azure infrastructure, automation, and containerized environments, complemented by administrative knowledge of Splunk and Dynatrace.
The role will focus on automating deployments, infrastructure, and observability setupensuring applications and services can be quickly onboarded, validated, and ready for production monitoring.

Key Responsibilities

1. CI/CD & Release Automation
Design and maintain pipelines using Jenkins, GitHub Actions, Azure DevOps, or equivalent tools. Automate builds, testing, deployments, and post-deployment validation, incorporating approval controls, rollback mechanisms, and secure release practices.
2. Azure Infrastructure & Infrastructure as Code
Provision and manage Azure services, including AKS, App Services, Azure Functions, networking, and storage. Use Terraform, Bicep, or equivalent tools to automate provisioning, standardize configurations, and improve scalability and cost efficiency.
3. Containerization & Kubernetes
Build and maintain Docker images and Kubernetes deployment configurations. Manage AKS workloads, scaling, resource allocation, and health checks; troubleshoot container, connectivity, and deployment issues.
4. Automation & Security
Develop reusable scripts using Python, PowerShell, or Bash to reduce manual effort across infrastructure, deployments, and operational workflows. Automate configuration management and integrate security scanning, secrets management, and access controls into delivery processes.
5. Splunk & Dynatrace Administration, Automation & Production Readiness
Automate platform setup, agent/forwarder deployment, configuration, and application onboarding to accelerate production-monitoring readiness. Support access management, platform health, and troubleshooting. Integrate reusable automation and readiness checks into CI/CD pipelines to validate log ingestion, telemetry collection, and monitoring coverage before go-live.
6. SRE & Production Reliability
Apply SRE principles, including SLIs, SLOs, error budgets, incident management, and post-incident reviews. Partner with SRE L2/L3 teams to resolve production issues, reduce MTTR, and automate recurring operational and recovery activities.
7. Collaboration & Enablement

Provide reusable automation templates, operational runbooks, and engineering standards. Enable self-service provisioning and monitoring onboarding, integrate workflows with ServiceNow or Jira, and guide teams on deployment and operational readiness.

Required Qualifications

5+ years of hands-on DevOps or platform engineering experience, including CI/CD ownership, infrastructure automation, and production troubleshooting.
Strong experience with Jenkins, GitHub Actions, Azure DevOps, or equivalent tools, along with Git-based workflows.
Hands-on expertise in Microsoft Azure, Infrastructure as Code, Docker, Kubernetes/AKS, and Linux.
Strong scripting skills in Python, PowerShell, or Bash, including API-based automation and tool integration.
Working administrative knowledge of both Splunk and Dynatrace, including access management, forwarder/agent configuration, data onboarding, platform health, and troubleshooting.
Ability to automate monitoring setup, streamline application onboarding, and validate production-monitoring readiness.
Understanding of SRE fundamentals, with strong analytical, communication, and cross-functional collaboration skills.

Preferred Qualifications

Experience supporting retail/e-commerce platforms, microservices, and distributed systems. Familiarity with Helm, GitOps/Argo CD, Prometheus, and Grafana.
Certifications in Azure, Kubernetes, Terraform, Splunk, or Dynatrace are good to have, but not mandatory.
Success Measures
Reduced time to onboard applications into production monitoring; increased automation and self-service adoption; validated monitoring coverage before go-live; fewer manual configuration errors; and improved deployment reliability and incident resolution time.