Genpact
Website:
genpact.com
Job details:
Azure Cloud Infra Operations Engineer
Locations: Hyderabad, Noida, Delhi, Pune, Bangalore, Chennai
Experience: 3-5 years
Immediate joiners
If you are immediate joiner, Kindly share resume to nsenthil.kumar@genpact.com with Sub of "Azure Cloud Infra" along with notice period.
Job Description
- Background & Objective
Honeywell operates business‑critical SaaS and platform workloads on Azure that have evolved organically over time. While effective, the current model presents operational risk, scalability limitations, and inconsistent automation.
The objective of this RFP is to engage a qualified partner to:
• Automate, build, and operate Azure cloud infrastructure
• Reduce reliance on individual SMEs through standardization, automation, and documentation
• Accelerate onboarding of new workloads using Azure‑native services and repeatable patterns
- Scope of Services
2.1 Automate – Azure Infrastructure Automation
The vendor shall design and implement automation to eliminate manual SME intervention and ensure repeatable, compliant infrastructure delivery.
Responsibilities include:
- Infrastructure‑as‑Code (Terraform and/or Bicep)
- CI/CD pipelines for provisioning and configuration management
- Automated setup of:
- Subscriptions, resource groups
- Networking (VNets, subnets, routing, NSGs)
- Identity and access (RBAC, managed identities)
- Policy‑as‑Code using Azure Policy
- Integration with enterprise tooling (e.g., ServiceNow for intake and approvals)
- Automation of logging, monitoring, diagnostics, backup, and recovery
- Reusable modules and templates for new customer and platform workloads
2.2 Build – Azure Platform & Workload Enablement
The vendor shall build Azure environments using cloud‑native and enterprise‑aligned design principles.
Responsibilities include:
- Build and configure Azure subscriptions aligned to enterprise standards
- Implement approved network topologies (e.g., hub‑and‑spoke)
- Deploy core Azure services:
- Compute (VMs, scale sets)
- PaaS (App Services, Azure SQL, Storage)
- AKS where applicable
- Implement high availability, resiliency, and environment separation (Dev/Test/Prod)
- Ensure alignment with security, network, and identity standards
- Deliver architecture diagrams and build documentation
2.3 Operate – Run, Support & Optimize
The vendor shall provide Day‑2 Azure operations under defined SLAs.
Responsibilities include:
- Incident, problem, and change management
- Operational support for Azure compute, networking, storage, and PaaS
- Patch and vulnerability management
- Backup and disaster recovery operations
- Performance tuning and capacity planning
- Proactive operational improvements and risk reduction
- Required Skills & Experience
Azure & Platform Expertise:
- Azure IaaS and PaaS services
- Azure networking and security
- AKS experience (preferred)
Automation & DevOps:
- Terraform
- Azure DevOps and/or GitHub Actions
- PowerShell and Python
Operations & Governance:
- ITIL‑aligned cloud operations
- Monitoring and observability
- Security and compliance alignment
Collaboration & Delivery:
- Strong documentation practices
- Experience working with enterprise security and network teams
- Skillsets & Responsibilities (Effort Allocation estimates)
The following allocation summarizes typical cloud infrastructure operations responsibilities (run/support/optimize) and the expected effort distribution across Infra Operations post-deployment. Effort categories, typical activities, and Percentages are indicative and may vary by workload criticality, release cadence, and incident volume and changing business priorities time to time.
- Outcomes/Deliverables
- Automated IaC repositories and pipelines
- Azure build, architecture and operating workbook documentation for new builds & onboarded customer environments.
- Operational runbooks
- SLA‑based support and operating model
- Vendor Response Requirements
Vendors must provide:
- Company overview and onboarding team member Azure experience and practice
- Relevant enterprise Azure engagements & initiatives in maturing the platform.
- Proposed Azure operating model (ABO) efficacy and framework to build address 80% work through automation by the end of 1 year.
- Key assumptions, risks, and dependencies and mitigation strategies. Achieve maximum outcome with less dependency on stakeholders and other internal teams.
6. Evaluation Criteria
- Azure technical depth
- Automation maturity
- Operational excellence
- Security and governance alignment
Click on Apply to know more.