Cloud and DevOps engineers in the GCCs

A role across the GCC collection, all ten Parent Industries together.

The short answer

Cloud and DevOps engineers are the second-largest single role in the GCC world, after Java, a little above their weight at product companies. They build and run the platforms the parent's software lives on, such as the cloud accounts and Kubernetes clusters, the pipelines that take code to production, the monitoring that warns when something is failing, and the parent's own data centres where they remain. Most of them write code too. Python is required in nearly every posting and Java in most. The role follows the software. It sits where the GCCs build the parent's apps and platforms, so the banks hold most of it, with JPMorganChase, Societe Generale, NatWest Group and Commonwealth Bank the largest employers, and Walmart and Optum India beside them. It is an unusually large part of hiring at the telecom operators, like TMUS Global Solutions and BCE Global Tech, and the media groups, like Warner Bros. Discovery and Disney. Through 2026 the role held a steady share, shifted further towards cloud-native platform work, and took on more of the infrastructure for AI. It is a senior role. Staff-level openings take a larger share than across the GCCs, and juniors get in mainly at JPMorganChase, NatWest Group and Optum India.

Where the work sits

The banks hold most of it, a little above their weight.

Parent Industry 1, Inside the banks and financial institutions, posts more cloud and DevOps openings than all the other industries together, and the role is a slightly larger part of a bank's hiring than of the GCCs' as a whole. JPMorganChase posts the most of any centre, then Societe Generale, NatWest Group, Commonwealth Bank and Wells Fargo. (More on it in the banks' hiring, in Parent Industry 1.)

The retailers and the healthcare companies hire it at their usual weight. In retail, Walmart and Tesco post most of it, and at lululemon cloud work is a larger part of hiring than at any other centre in the GCC world. (More on it in the retailers' hiring, in Parent Industry 3.) In healthcare, Optum India posts most of it, and HCA Healthcare hires it as one of its main roles. (More on it in the healthcare companies' hiring, in Parent Industry 5.)

The telecom operators and the media groups hire it most, in proportion. In Parent Industry 8, Inside the telecom operators, cloud and DevOps is well above its GCC weight and mostly at TMUS Global Solutions, T-Mobile's centre. In Parent Industry 9, Inside the media, entertainment and publishing groups, it is also well above its weight, mostly at Warner Bros. Discovery.

Below their weight. The insurers, like MetLife and Principal Global Services, the hotels and airlines, like Southwest Airlines and Marriott, and the energy majors hire cloud engineers at well under their GCC weight, though at bp the role is one of the main things the centre posts. In Parent Industry 4, Inside the manufacturers and carmakers, Cargill hires the most, and the industry leans to running infrastructure. Parent Industry 6, Inside the logistics operators and distributors, hires almost none, because UPS's centre is a testing centre.

By mandate, the role follows the builders. The centres whose mandate is Building the parent's apps and platforms, like JPMorganChase, Walmart, Societe Generale and Commonwealth Bank, hold the large majority of the role, above their weight. The centres that took on The whole engineering function, like NatWest Group, Wells Fargo and American Express, hold most of the rest, a little under their weight. The centres with Products across many lines, like HCA Healthcare and BNP Paribas, hire it above their weight. A centre Running the parent's own systems, like Merck Group or Saint-Gobain, hardly hires it, and centres Engineering the thing itself, like Celestica and Tesla, almost never do.

What the work is

The role comes in four kinds. The largest by far is cloud-native platform work, building and running the parent's platforms on Kubernetes and the public clouds. The other three are site reliability engineering, keeping live systems fast and up and getting them back when they fail, pipeline engineering, building the path that takes code from a developer to production, and infrastructure administration, running the servers, networks and storage the parent still owns. A small group of network engineers sits mostly at Tesco and Walmart.

These are engineers who write code. Nearly every posting requires Python, most require Java, and a notable share require Go. AWS and Kubernetes each appear in about every other posting, with Terraform, Azure, Docker, Jenkins, Azure DevOps, GitHub Actions and Google Cloud behind them, and Grafana, Prometheus and Splunk for watching systems run. Many postings also require security and database work, and a growing share involve infrastructure for AI and machine learning.

The emphasis follows the industry.

The banks add security scanning to the pipeline, with Checkmarx and Black Duck, and deploy through Spinnaker, Harness and TeamCity.

The retailers lean most to site reliability and to Go, and Tesco's postings bring networking, OpenStack and the protocols that carry a store's traffic.

The healthcare companies lean to Azure, with its messaging services, and deploy with Argo CD.

The insurers lean to pipeline work and to AWS's own services, Lambda, its queues and managed containers.

The carmakers and manufacturers lean to infrastructure administration and to Go.

The media groups and the telecom operators lean to observability, the tools that show what a live system is doing, with OpenTelemetry, Grafana and Splunk, and the media groups to Kafka Streams and Go.

The platform centres lean a little more to site reliability. The whole-function centres lean more to infrastructure administration and to the security scanning and older platforms, such as OpenShift and IBM Db2, that a large estate carries.

Bengaluru has most of the work, a little more of cloud than of GCC hiring as a whole. Chennai and Mumbai hold a little less of it than of GCC hiring.

What is changing

These readings follow the record quarter by quarter, from October to December 2025, the third quarter of the financial year 2025-26, to July to September 2026, the second quarter of 2026-27. A longer record will show whether they last.

Cloud kept a steady share as the GCCs grew and then shrank

GCC hiring climbed to April to June 2026 and fell back in July to September 2026. Cloud and DevOps openings followed it closely. The role's share dropped after October to December 2025 and then held steady for three quarters, much as at product companies.

The work moved further into cloud-native platforms

Platform work grew as a part of the role in every quarter, while site reliability shrank.

AI infrastructure grew

The share of cloud postings involving infrastructure for AI and machine learning rose from a small minority in October to December 2025 to a sizeable one by July to September 2026.

Go faded

Go was required in a larger share of cloud postings in October to December 2025 than in any later quarter.

The retailers pulled back

Retail's cloud openings fell in every quarter after January to March 2026, while the banks' peaked in April to June 2026.

Persistently open roles

Cloud jobs stay open about as often as GCC jobs overall. When one is posted again, its first and last postings are typically about three weeks apart, and nine in ten are within about ten weeks.

The retailers keep cloud jobs open longest by far, followed by the media groups. The healthcare companies, the insurers and the hotels and airlines rarely post one twice.

Tesco, Commonwealth Bank, Walmart and Cargill keep a large share of their cloud jobs open again and again.

Optum India, Barclays, MetLife, Wells Fargo and NatWest Group rarely do, and TMUS Global Solutions never did.

Staff-level cloud jobs stay open longest, and mid-level jobs fill fastest.

The skills found most often in persistently open cloud jobs are networking and the private cloud, with OpenStack, DNS, VPCs and TCP/IP, secrets and service mesh tools such as HashiCorp Vault and Istio, and PowerShell, TeamCity and AWS's deployment tools.

The door

Cloud's door is more senior than the GCC door. Entry-level openings are very rare, junior openings are at about the GCC rate, and staff-level openings take a clearly larger share than across the GCCs.

The juniors are at the largest bank and healthcare centres.

JPMorganChase posts the most junior cloud openings, followed by NatWest Group, Optum India and Wells Fargo. In proportion, Optum India and NatWest Group take juniors most readily.

The healthcare companies take juniors more readily than any other large industry. The retailers take few, and the media groups and telecom operators post none.

The whole-function centres take juniors more readily than the platform centres, which are the most staff-heavy part of the role.

Commonwealth Bank and Barclays post no junior cloud openings, and Walmart and Tesco almost none.

In one line

If you can build and run cloud platforms with Kubernetes and Terraform and write Python or Java alongside, the GCCs hire you everywhere they build software, most of all at the banks, and increasingly to run the infrastructure for AI, though the door opens mainly to people with experience.

Terms used on this page

Mandate

The kind of work a parent company gives its engineering centre in India, such as building its apps and platforms, running its own systems, or testing software built elsewhere.

Back to the story

This page reads the openings. The story of the companies is on Global capability centres in India (GCCs).