Lead AWS Cloud Engineer, IT Park — Chandigarh
An on-site, full-time Lead AWS Cloud Engineer position has opened at a company based in IT Park, Chandigarh, on the Rajiv Gandhi Technology Park stretch. This is a senior spot, not an entry point into cloud work. The company is looking for someone who's already run production infrastructure and is ready to own it, not learn it on the job.
The team runs a fairly standard DevOps stack, but at a scale where a bad deployment script doesn't just fail quietly; it takes something down that people notice. Pipelines get touched daily, and the lead engineer is expected to catch a broken build before it reaches production, not after a support ticket comes in about it. Nine years of hands-on experience is the baseline the company is asking for, and that number reflects how much judgment this role assumes someone already has, not just familiarity with the tools.
Day-to-day, the work covers:
- Building and maintaining CI/CD pipelines across development and production environments
- Automating infrastructure provisioning so environments can be stood up and torn down without manual intervention
- Troubleshooting issues that surface in either the pipeline itself or the systems it deploys to
- Reviewing and approving infrastructure changes proposed by other engineers on the team
A three-in-the-morning outage a few months ago got traced back to a Terraform state file that two engineers had edited within minutes of each other without realizing it. That's the kind of failure this role exists to prevent going forward, less through a rulebook and more through someone senior enough to spot the risk before it becomes an incident.
Required technical skills include AWS services such as EC2, S3, and Lambda; working knowledge of Terraform or CloudFormation for infrastructure as code; comfort operating in Linux environments; and scripting ability to automate repetitive parts of the job. Naukri Mitra has seen a steady rise in postings for roles like this one across Chandigarh's IT Park over the past year, and this listing sits toward the senior end of that range in both scope and pay.
Beyond the required list, a few skills would strengthen an application without being mandatory: exposure to Kubernetes or Docker for container orchestration, familiarity with monitoring tools like CloudWatch or Prometheus, and any prior work spanning more than one cloud provider. None of these are screened out if missing, but they do tend to matter once the person actually starts handling incidents.
On-call rotation is part of the deal at this level, roughly one week in four, and outages during that window take priority over anything else on the calendar. Most weeks pass without an incident worth waking up for, but when something does break at an odd hour, it's this engineer who gets the call first, not a general support line. The company treats that expectation as a normal part of the seniority the role carries, not something dressed up as extra dedication.
Career progression from here usually points toward a platform architecture role or, for someone who prefers staying closer to hands-on work, a principal engineer track that skips people management entirely. A couple of the company's current architects came up through a role fairly similar to this one, so it's not a dead end for someone aiming higher within the same organization rather than jumping elsewhere for the next step.
The minimum education requirement is a bachelor's degree, with computing or a technical discipline being the closest fit given the work involved. On top of that, companies filling lead-level cloud positions generally expect a recognized certification from AWS, Azure, or GCP, plus real, demonstrated time spent with containerized systems and automated deployment pipelines. The certification isn't strictly required on its own, but candidates without one usually need a noticeably stronger track record to make up for it in the interview.
Pay for this role runs up to ₹223,000 a month, on-site, full-time, positioning it well above typical mid-level cloud engineering pay in the city. Since relocation is common for a role at this seniority, the company also provides a set of benefits aimed at people moving into Chandigarh for the job:
- Health insurance
- Paid time off
- Performance-linked bonuses tied to uptime and delivery targets
- Relocation assistance and accommodation support for candidates coming from outside Chandigarh
IT Park itself has grown into one of the densest tech clusters in the region, and Rajiv Gandhi Technology Park in particular hosts a mix of larger IT services firms alongside smaller product teams, with this company among the latter. That mix means the pool of candidates already familiar with the area's pace and expectations is fairly deep, which raises the bar somewhat for anyone applying from further afield. Most of the engineering team commutes from within the tricity area, though a few have relocated from Delhi NCR specifically for roles at this level, drawn partly by the lower cost of living without much drop in pay for senior cloud work.
Interviews for this role typically run in two stages: a technical screen focused on real infrastructure scenarios rather than whiteboard algorithms, followed by a conversation with the engineering lead about how the candidate has handled past incidents. Anyone who's dealt with a genuinely bad production failure and can walk through what went wrong and what changed afterward tends to do well in that second conversation. It says more about how someone will handle the job than a list of certifications ever could.
Reporting lines for this position go directly to the engineering lead, and the role carries real authority over infrastructure decisions rather than sitting purely in an advisory capacity. Junior engineers on the team will bring changes to this person for review before anything touches production, so the day-to-day includes a fair amount of mentoring alongside the hands-on infrastructure work itself.
Applications are accepted on a rolling basis, and shortlisted candidates should expect the process to move within a couple of weeks given how specific the role's requirements are. Anyone outside Chandigarh who's serious about the move should mention it upfront, since the relocation package is discussed early rather than left for the final offer stage.
