Lead Cloud Infrastructure Engineer – Jaipur (Mahindra World City)
An on-site, full-time Lead Cloud Infrastructure Engineer position has opened up at Mahindra World City in Jaipur, paying up to ₹2,24,500 a month. This sits at the senior end of the Cloud & DevOps track, running infrastructure and deployment work for teams that depend on it staying up.
What the role covers
- Design, build, and maintain CI/CD pipelines that development teams rely on to ship code safely
- Automate infrastructure provisioning so environments can be spun up or torn down without manual intervention
- Troubleshoot issues across development and production, often under time pressure when something in production breaks
- Set technical direction for infrastructure decisions and review the work of other engineers on the team
- Own on-call rotation planning and act as the escalation point when junior engineers hit something they can't resolve alone
The leadership piece isn't a side responsibility bolted onto an individual-contributor job description. It's a real part of the role: someone in this seat is expected to make calls on architecture direction, not just execute someone else's design.
Requirements
A bachelor's degree is the baseline education requirement here, and most people in this seat studied computer science or a similarly technical program before moving into infrastructure work. Beyond the degree, employers hiring for this level also want a recognized cloud certification, whether that's AWS, Azure, or GCP, since it signals a certain depth of platform knowledge that a resume alone doesn't always prove.
This seat expects nine years of hands-on infrastructure experience. That's a meaningful stretch of career, and it typically shows up as the ability to look at a misbehaving system and know where to start, rather than guessing. Candidates coming in with exactly nine years on paper but limited exposure to production incidents at scale may still be asked to walk through specific outage scenarios during the interview, since the number alone doesn't tell the whole story.
Core skills
- Deep working knowledge of at least one major cloud platform (AWS, Azure, or GCP), ideally with exposure to more than one
- Solid networking fundamentals, including VPC design, load balancing, and DNS troubleshooting
- Terraform, for defining and versioning infrastructure rather than configuring it by hand
- Comfort administering Linux systems at a level beyond basic command-line familiarity
Networking knowledge on this team gets tested in practice more than most candidates expect. A misconfigured route table or an overly broad security group rule tends to surface during an incident, not during a calm afternoon of documentation, so we expect a candidate to reason through network behavior under some pressure, not just describe it in an interview.
Good to have
Container orchestration experience, particularly Kubernetes, will strengthen an application meaningfully, since a growing share of the infrastructure this team manages runs on it. Familiarity with cost optimization work across cloud spend is useful too, and prior experience mentoring engineers directly, rather than just working alongside them, tends to translate well into this lead-level seat.
Compensation and benefits
Pay for this cloud infrastructure engineer role in Jaipur runs up to ₹2,24,500 per month, reflecting both the seniority and the on-site, full-time nature of the position. Along with that:
- Health insurance coverage for the employee
- Paid time off, applied on a standard full-time schedule
- Performance-linked bonuses tied to team and infrastructure outcomes
- Relocation assistance and accommodation support for anyone moving to Jaipur to take the job
That last point matters more here than it might elsewhere, since the role is on-site and won't work as a remote or hybrid arrangement.
Working at Mahindra World City
Mahindra World City in Jaipur has become a fairly established base for tech and engineering operations over the past several years, and this employer's cloud infrastructure team sits within that cluster. Naukri Mitra has carried a handful of similar Cloud & DevOps postings from employers in this same zone, and the working pattern here tracks closely with those: standard business hours, an office-based team rather than a distributed one, and infrastructure work that's shared across a handful of engineers rather than owned by one person in isolation.
A lead in this seat spends real time in meetings, whether that's planning sessions with product teams or postmortems after an incident. Anyone expecting to spend the entire week heads-down writing Terraform without interruption will find the actual mix of the job different from that picture. Roughly a third of a typical week goes toward direct hands-on work, with the rest split between reviewing other engineers' infrastructure changes, coordinating with product and platform teams on upcoming projects, and handling whatever incident happens to be active that week.
The team currently runs a mixed environment split across two cloud providers, which came about after an earlier migration project rather than by original design. Newer hires sometimes find the resulting setup inconsistent between the two platforms, and part of the lead's job is smoothing over that inconsistency where it causes problems, rather than pushing for a full re-architecture that isn't currently on the roadmap.
Who this suits
This role fits someone who's already spent years as a senior individual contributor and is ready to take on decisions that affect a whole team's infrastructure, not just their own piece of it. It also suits someone coming from a smaller company where they've already been doing lead-adjacent work informally, without the title, and wants that responsibility formally recognized. Candidates who prefer staying purely hands-on with code and infrastructure, without the mentoring and escalation duties, may find this particular seat asks for more people-facing work than they're looking for.
How to apply
Send a resume that spells out which cloud platforms you've actually run in production, along with your certification if you hold one. The hiring team reads for specifics here, not general cloud experience claims. Candidates who move forward will hear from a recruiter directly to set up a first conversation, and the process from there typically runs through a technical discussion focused on real infrastructure decisions rather than abstract theory. Openings for experienced professionals in Jaipur like this one tend to move at a steady pace rather than an urgent one, so candidates shouldn't expect same-week turnaround at every stage.
