Pune, Maharashtra
Job Summary
Role Summary As a Mid-Level Cloud Automation & Integration Engineer, your primary focus is supporting new requirements, enhancements, and code development for cloud operations automation using Terraform, Ansible, and DevOps pipelines, plus operational engineering support for Microsoft Azure Services (1st Priority). You will not be involved in daily operational tasks and routine ticket execution, except during critical situations (major incidents, high-severity escalations, production-impacting failures), or when engineering changes are required to restore service. Key Responsibilities 1) Engineering Support for New Requirements & Enhancements (Primary Focus) Translate enhancement requests into actionable technical changes (within defined scope). Implement and maintain automation-as-code: Terraform: develop/enhance modules, enforce reusable patterns, manage safe change practices. Ansible: develop/enhance playbooks for repeatable operations (e.g., patch orchestration, configuration updates). DevOps pipelines: implement improvements to CI/CD workflows, validations, approvals & safe deployments. (optional) Improve reliability of automation by introducing: validation checks, testing practices (where applicable), linting, consistent environments, and rollback guidance. 2) Azure Services Support (Operational Engineering) Provide technical support & enhancements for Microsoft Azure Integration Services (as used by the customer), such as: integration runtime reliability, deployment automation, configuration consistency, monitoring and alerting improvements. Perform troubleshooting for integration-related production issues when escalated (not daily ticket handling). Improve observability and operational readiness of integration components: actionable dashboards, alert tuning, and runbooks for common failure patterns. Note: Exact services (e.g., Logic Apps, API Management, Service Bus, Event Grid, Functions) can be listed in the final JD if you confirm what WACKER uses. Our Service List: AKS, Integration Services, Cognitive Services, WebApp, API Mgmt. AI, KeyVault, Storage, Virtual Machine, IoT, AVD 3) Critical Incident Support (Escalation Only) Participate in critical situations and high-severity incidents as an escalation engineer: deep troubleshooting related to automation/IaC/pipelines/integration services. drive structured RCA inputs for the engineering part (automation or integration root causes). Provide corrective fixes that prevent recurrence (guardrails, automation improvements, better monitoring). 4) Governance, Documentation & Knowledge Transfer Produce high-quality engineering documentation for: new modules/playbooks/pipeline changes, operational runbooks, and handover notes to the ops team. Review/mentor juniors on: safe IaC practices, PR quality, documentation standards, and troubleshooting approach. Ensure changes are traceable through DevOps work items and aligned to change governance. Explicit Role Boundaries (Important) Not responsible for daily operations (routine monitoring, standard ticket processing, repetitive MAC tasks). Engaged when: new enhancement/requirement is raised, automation or pipeline development is needed, Azure Integration Services require engineering support, a critical incident requires escalation. Required Technical Skills Strong hands-on engineering with Terraform (module development, reusable patterns, safe rollout practices), HashiCorp Certified Strong hands-on engineering with Ansible (roles/playbooks development, idempotency, patch orchestration). CI/CD expertise (Azure DevOps or GitHub pipelines): pipeline design, approvals, safe deployments, artifact/version controls; policy compliance understanding. Working knowledge of Microsoft Azure Services operations and troubleshooting (customer-specific stack). Soft Skills (Must Have) Engineering ownership: drives enhancements from requirement design implementatio
Key Responsibilities
Role Summary As a Mid-Level Cloud Automation & Integration Engineer, your primary focus is supporting new requirements, enhancements, and code development for cloud operations automation using Terraform, Ansible, and DevOps pipelines, plus operational engineering support for Microsoft Azure Services (1st Priority). You will not be involved in daily operational tasks and routine ticket execution, except during critical situations (major incidents, high-severity escalations, production-impacting failures), or when engineering changes are required to restore service. Key Responsibilities 1) Engineering Support for New Requirements & Enhancements (Primary Focus) Translate enhancement requests into actionable technical changes (within defined scope). Implement and maintain automation-as-code: Terraform: develop/enhance modules, enforce reusable patterns, manage safe change practices. Ansible: develop/enhance playbooks for repeatable operations (e.g., patch orchestration, configuration updates). DevOps pipelines: implement improvements to CI/CD workflows, validations, approvals & safe deployments. (optional) Improve reliability of automation by introducing: validation checks, testing practices (where applicable), linting, consistent environments, and rollback guidance. 2) Azure Services Support (Operational Engineering) Provide technical support & enhancements for Microsoft Azure Integration Services (as used by the customer), such as: integration runtime reliability, deployment automation, configuration consistency, monitoring and alerting improvements. Perform troubleshooting for integration-related production issues when escalated (not daily ticket handling). Improve observability and operational readiness of integration components: actionable dashboards, alert tuning, and runbooks for common failure patterns. Note: Exact services (e.g., Logic Apps, API Management, Service Bus, Event Grid, Functions) can be listed in the final JD if you confirm what WACKER uses. Our Service List: AKS, Integration Services, Cognitive Services, WebApp, API Mgmt. AI, KeyVault, Storage, Virtual Machine, IoT, AVD 3) Critical Incident Support (Escalation Only) Participate in critical situations and high-severity incidents as an escalation engineer: deep troubleshooting related to automation/IaC/pipelines/integration services. drive structured RCA inputs for the engineering part (automation or integration root causes). Provide corrective fixes that prevent recurrence (guardrails, automation improvements, better monitoring). 4) Governance, Documentation & Knowledge Transfer Produce high-quality engineering documentation for: new modules/playbooks/pipeline changes, operational runbooks, and handover notes to the ops team. Review/mentor juniors on: safe IaC practices, PR quality, documentation standards, and troubleshooting approach. Ensure changes are traceable through DevOps work items and aligned to change governance. Explicit Role Boundaries (Important) Not responsible for daily operations (routine monitoring, standard ticket processing, repetitive MAC tasks). Engaged when: new enhancement/requirement is raised, automation or pipeline development is needed, Azure Integration Services require engineering support, a critical incident requires escalation. Required Technical Skills Strong hands-on engineering with Terraform (module development, reusable patterns, safe rollout practices), HashiCorp Certified Strong hands-on engineering with Ansible (roles/playbooks development, idempotency, patch orchestration). CI/CD expertise (Azure DevOps or GitHub pipelines): pipeline design, approvals, safe deployments, artifact/version controls; policy compliance understanding. Working knowledge of Microsoft Azure Services operations and troubleshooting (customer-specific stack). Soft Skills (Must Have) Engineering ownership: drives enhancements from requirement design implementatio
Skill Requirements
"Role Summary As a Mid-Level Cloud Automation & Integration Engineer, your primary focus is supporting new requirements, enhancements, and code development for cloud operations automation using Terraform, Ansible, and DevOps pipelines, plus operational engineering support for Microsoft Azure Services (1st Priority). You will not be involved in daily operational tasks and routine ticket execution, except during critical situations (major incidents, high-severity escalations, production-impacting failures), or when engineering changes are required to restore service. Key Responsibilities 1) Engineering Support for New Requirements & Enhancements (Primary Focus) Translate enhancement requests into actionable technical changes (within defined scope). Implement and maintain automation-as-code: Terraform: develop/enhance modules, enforce reusable patterns, manage safe change practices. Ansible: develop/enhance playbooks for repeatable operations (e.g., patch orchestration, configuration updates). DevOps pipelines: implement improvements to CI/CD workflows, validations, approvals & safe deployments. (optional) Improve reliability of automation by introducing: validation checks, testing practices (where applicable), linting, consistent environments, and rollback guidance. 2) Azure Services Support (Operational Engineering) Provide technical support & enhancements for Microsoft Azure Integration Services (as used by the customer), such as: integration runtime reliability, deployment automation, configuration consistency, monitoring and alerting improvements. Perform troubleshooting for integration-related production issues when escalated (not daily ticket handling). Improve observability and operational readiness of integration components: actionable dashboards, alert tuning, and runbooks for common failure patterns. Note: Exact services (e.g., Logic Apps, API Management, Service Bus, Event Grid, Functions) can be listed in the final JD if you confirm what WACKER uses. Our Service List: AKS, Integration Services, Cognitive Services, WebApp, API Mgmt. AI, KeyVault, Storage, Virtual Machine, IoT, AVD 3) Critical Incident Support (Escalation Only) Participate in critical situations and high-severity incidents as an escalation engineer: deep troubleshooting related to automation/IaC/pipelines/integration services. drive structured RCA inputs for the engineering part (automation or integration root causes). Provide corrective fixes that prevent recurrence (guardrails, automation improvements, better monitoring). 4) Governance, Documentation & Knowledge Transfer Produce high-quality engineering documentation for: new modules/playbooks/pipeline changes, operational runbooks, and handover notes to the ops team. Review/mentor juniors on: safe IaC practices, PR quality, documentation standards, and troubleshooting approach. Ensure changes are traceable through DevOps work items and aligned to change governance. Explicit Role Boundaries (Important) Not responsible for daily operations (routine monitoring, standard ticket processing, repetitive MAC tasks). Engaged when: new enhancement/requirement is raised, automation or pipeline development is needed, Azure Integration Services require engineering support, a critical incident requires escalation. Required Technical Skills Strong hands-on engineering with Terraform (module development, reusable patterns, safe rollout practices), HashiCorp Certified Strong hands-on engineering with Ansible (roles/playbooks development, idempotency, patch orchestration). CI/CD expertise (Azure DevOps or GitHub pipelines): pipeline design, approvals, safe deployments, artifact/version controls; policy compliance understanding. Working knowledge of Microsoft Azure Services operations and troubleshooting (customer-specific stack). Soft Skills (Must Have) Engineerin
Other Requirements
"Role Summary As a Mid-Level Cloud Automation & Integration Engineer, your primary focus is supporting new requirements, enhancements, and code development for cloud operations automation using Terraform, Ansible, and DevOps pipelines, plus operational engineering support for Microsoft Azure Services (1st Priority). You will not be involved in daily operational tasks and routine ticket execution, except during critical situations (major incidents, high-severity escalations, production-impacting failures), or when engineering changes are required to restore service. Key Responsibilities 1) Engineering Support for New Requirements & Enhancements (Primary Focus) Translate enhancement requests into actionable technical changes (within defined scope). Implement and maintain automation-as-code: Terraform: develop/enhance modules, enforce reusable patterns, manage safe change practices. Ansible: develop/enhance playbooks for repeatable operations (e.g., patch orchestration, configuration updates). DevOps pipelines: implement improvements to CI/CD workflows, validations, approvals & safe deployments. (optional) Improve reliability of automation by introducing: validation checks, testing practices (where applicable), linting, consistent environments, and rollback guidance. 2) Azure Services Support (Operational Engineering) Provide technical support & enhancements for Microsoft Azure Integration Services (as used by the customer), such as: integration runtime reliability, deployment automation, configuration consistency, monitoring and alerting improvements. Perform troubleshooting for integration-related production issues when escalated (not daily ticket handling). Improve observability and operational readiness of integration components: actionable dashboards, ale
#body.unify div.unify-button-container .unify-apply-now: focus, #body.unify div.unify-button-container .unify-apply-#body.unify div.unify-button-container .unify-apply-now: focus, #body.unify div.unify-button-container .unify-apply-
