Tech Lead - Cloud Technologies S 4C

Job description

Tech Lead - Cloud Technologies S Ready to turn bold ideas into real-world impact? At Genpact, we don’t just adapt to change, we lead it. AI and digital innovation are transforming the way businesses work, and we’re at the forefront of it. Genpact’s AI Gigafactory, our industry-first accelerator, exemplifies how we scale advanced technology solutions to help global enterprises work smarter, grow faster, and transform at scale. Whether tackling complex challenges through large-scale models or agentic AI, our breakthrough solutions tackle companies’ most complex challenges. If you thrive in a fast-moving, innovation-driven environment, love building and deploying cutting-edge AI solutions, and want to push the boundaries of what’s possible, this is your moment.  Genpact (NYSE: G) is an agentic and advanced technology solutions company. We leverage process intelligence and artificial intelligence to deliver measurable outcomes. With a strong partner ecosystem and decades of client trust, we provide innovative solutions that transform how businesses run. Powered by a team with an active learning mindset and client centricity at its core, we deliver lasting value for the world’s leading enterprises. Get to know us at genpact.com and on LinkedIn, YouTube, X, and Facebook. Job Description CLOUD OPERATIONS  |  AZURE · AWS · GCP Manager — Cloud Service Delivery, Process & Customer Experience Band 4C - Manager Location NCR / Bangalore / Hyderabad (hybrid) Function Cloud Operations Experience 8–12 years, incl. 3+ in cloud service delivery The role We are looking for a Manager to drive service delivery and process for our public cloud estate across Azure, AWS and GCP. You will be responsible for how cloud services are delivered, governed and experienced by the application and business teams who depend on them. This is a hands-on technical role as much as a service role. You are expected to operate at L3 — the highest technical escalation tier — in cloud infrastructure administration: the point at which issues are resolved rather than routed. On that foundation, the role adds service management, process improvement and stakeholder engagement, working closely with cloud engineering, network, identity, security and solution teams. On-premise compute, backup and storage sit with a separate team. Key responsibilities Cloud infrastructure administration (L3) ·       Highest-tier escalation — act as the L3 escalation point for cloud infrastructure issues: complex troubleshooting, root-cause analysis and permanent fix, engaging hyperscaler support only where genuinely required. ·       Core platform administration — hands-on administration across Azure and AWS — compute and virtual machine lifecycle, virtual networks, subnets, security groups and load balancers, storage accounts and object storage, snapshots and cloud-native recovery. ·       Automation and infrastructure-as-code — Terraform, ARM/Bicep or CloudFormation, with PowerShell or Python scripting, to automate administration tasks rather than repeat them. ·       Capacity, performance and cost — quota and service-limit management, rightsizing, performance troubleshooting, and removal of idle or orphaned resources. Cloud process and service delivery ·       Process improvement — document and improve the flow for each cloud service — provisioning, change, access, patching, cost approval, decommission — working towards a simpler, more standardised and more proactive version of it. ·       Cross-functional coordination — map the actors across cloud, network, identity, solution and security teams and keep each handoff clear and accountable, whether between people, between people and automation, or between automated steps. ·       Service management — run incident, problem, change and request practice for the cloud estate, with clean governance and reliable follow-through. ·       Self-service and automation — support the shift from request-driven to policy-driven: guardrailed provisioning, drift detection and automated remediation, in partnership with engineering. ·       Onboarding — help move new clients and workloads towards a blueprint-driven, low-touch onboarding model, with sign-off on the configuration itself. Customer and stakeholder experience ·       Experience measures — track and improve request-to-running time, clarity of communication around change, and the effort a team spends to get something done. ·       Stakeholder engagement — run regular feedback loops with application and business stakeholders and turn what you hear into specific improvement actions with named owners. ·       Change communication — keep the right stakeholders informed ahead of cloud change activity, with impact, timing and fallback stated up front. ·       Cost transparency — help make cloud spend understandable to the people