Sector 62 in Noida has become one of the busier DevOps hiring hubs in NCR, and this opening sits right in the middle of it: a full-time, on-site Lead Jenkins Administrator role focused on keeping a growing team's build and release pipeline running without surprises.
The company manages its own cloud infrastructure rather than outsourcing it, so whoever takes this seat will be close to the actual machines and environments, not just the dashboards that describe them. Jenkins sits at the center of nearly every release the engineering group ships, which means the person running it has more visibility into what's about to go wrong than almost anyone else on the team, usually before it shows up anywhere else.
What the day-to-day looks like
The role centers on Jenkins, but it doesn't stop there. Whoever holds it provisions and manages cloud infrastructure, keeps deployment pipelines automated end to end, and watches system performance closely enough to catch drift before it turns into downtime.
- Provision and manage cloud infrastructure across the team's active environments
- Build, automate, and maintain deployment pipelines centered on Jenkins
- Monitor system performance and reliability across build and release cycles
- Respond to infrastructure incidents as they come up, including pipeline failures that happen close to a release window
That last point deserves a plain mention rather than a vague nod: incident response is part of the job description, not an occasional exception. If a build breaks the evening before a planned release, fixing it becomes the priority for whoever's carrying the pipeline that week. Some weeks that means a quiet stretch of maintenance work, tightening job configurations or clearing out stale plugins; other weeks, it means being the first call when a deployment stalls halfway through and nobody can yet tell whether it's a Jenkins problem or something further upstream. Figuring that out quickly is most of the job.
Day-to-day, this also means owning the pipeline's documentation as it changes, not just the pipeline itself. Configurations drift over time as new services get added, and a lead administrator who lets that documentation fall behind ends up spending more time explaining the setup to teammates than actually maintaining it.
Education and experience
This role requires a four-year undergraduate degree as a minimum, typically in a computing-adjacent field. It's a baseline requirement rather than a soft preference, and it holds regardless of how strong a candidate's hands-on track record looks otherwise.
On the experience side, this listing calls for ten years of hands-on work in infrastructure or DevOps roles. At that level, most candidates will have already carried a pipeline through more than one major incident, so the interview conversation tends to focus less on whether someone can do the job and more on how they've handled it when things go wrong.
A recognized cloud certification from AWS, Azure, or GCP generally strengthens an application at this level, even though the listing doesn't treat it as a strict cutoff on its own. Candidates without one but with strong Jenkins and pipeline experience shouldn't rule themselves out, since the interview process weighs demonstrated pipeline work over a certification badge alone.
Employers hiring for this kind of role in Noida are usually looking past the resume for signs of how someone actually behaves during an outage: whether they narrate what they're doing as they troubleshoot, whether they know when to escalate instead of digging in alone, and whether they write down what happened afterward so the next incident goes faster. None of that shows up neatly on a CV, so expect the interview to probe for it directly.
Skills this role needs
- Jenkins administration, including pipeline design, plugin management, and ongoing maintenance
- Broader CI/CD pipeline experience beyond Jenkins specifically
- Scripting ability for automation work, whether that's Groovy, Bash, or Python
- Comfort with version control systems, particularly Git-based workflows
None of these need to be perfect on day one. A lead-level hire is still expected to keep learning the specifics of this particular environment during the first few months, and the team builds time into onboarding for exactly that.
Pay and benefits
The role pays up to ₹159,000 per month and is based out of the Sector 62 office in Noida. Naukri Mitra tracks this alongside a handful of similar lead-level DevOps openings hiring across the same corridor right now, and the pay sits toward the higher end for administrators with a decade of relevant experience.
- Health insurance
- Paid time off
- Performance-linked bonuses
- On-site cafeteria access
- Cab or commute support for the daily trip in and out of Sector 62
These are fairly standard for lead-level cloud and DevOps hires in this part of Noida, but they're worth listing plainly rather than folding them into a single line about "competitive benefits."
Working on-site
This is an on-site position, not remote or hybrid, so anyone applying should plan for a daily commute to the Sector 62 office rather than negotiating for flexibility later. For candidates already living in or near Noida, particularly around Sector 62, it's a straightforward commute. For anyone considering a move, the company treats this as a firm expectation from the start rather than something that shifts after the offer stage.
Uttar Pradesh's NCR belt has enough infrastructure and DevOps hiring right now that a candidate weighing a Jenkins administrator role in Noida against similar postings elsewhere in the region has real options to compare, and this one is worth weighing on pay, on the on-site requirement, and on the actual scope of ownership over the pipeline rather than the title alone.
Category and reporting line
This role sits within the company's Cloud & DevOps function, working alongside the engineers who provision and maintain the underlying infrastructure on which the pipelines run. Lead-level administrators here are expected to work closely with that group rather than operate the pipeline in isolation, since a change on either side tends to affect the other fairly quickly.
How to apply
Candidates already based in or around Noida, or open to relocating for a full-time on-site role, can apply directly through this listing. Including a few concrete examples of past Jenkins pipeline work, even briefly described, tends to speed up the first screening call considerably.
