Senior Configuration Management Engineer, Lalpur, Ranchi
There's a senior Configuration Management Engineer role open in Lalpur, full-time and on-site, paying up to ₹1,20,000 a month. If you've spent years keeping server fleets and application configs consistent using Ansible or Puppet, and you actually enjoy the discipline of making sure environments don't quietly drift apart from each other, this is worth a real look.
Five and a half years of hands-on experience is the expectation. That's roughly the point where someone's usually seen enough configuration drift disasters, an environment that "worked on staging" but failed in production because of some untracked manual change, to build real instincts around preventing them.
The company runs a mix of legacy systems configured years ago and newer services built with more discipline from the start. Bridging that gap, bringing the older environments up to a consistent standard without breaking whatever fragile thing is currently keeping them running, is a real and ongoing part of the work.
What the work looks like
- Write, maintain, and extend Ansible or Puppet playbooks that keep server and application configurations consistent across environments
- Automate repetitive configuration tasks that would otherwise get done manually, inconsistently, and eventually badly
- Investigate configuration drift when it shows up, tracing it back to its actual source rather than just patching the symptom
- Build scripts and tooling that make it harder for environments to fall out of sync in the first place
- Work with development and operations teams to define configuration standards that both sides can actually live with
A good chunk of the value in this role is invisible when it's done well. Nobody notices consistent, well-managed configuration; they only notice when it breaks. That tradeoff, doing careful, unglamorous work that mostly shows up as an absence of problems, suits some engineers far better than others.
When something does go wrong, it's rarely dramatic on its own; more often, it's a small inconsistency that snowballs. A package version that got pinned differently on one server during a rushed fix months ago, forgotten, then causes a deployment to fail in a way that takes real digging to trace back. That kind of patient troubleshooting is a constant undercurrent of the job.
Who fits this role
A bachelor's degree is the baseline, and the specific major matters less than a demonstrated track record of real project work in production environments. What the hiring team weighs most heavily is genuine hands-on time managing configuration at scale, not certifications or coursework alone.
A candidate transitioning from a general DevOps or systems administration background, without the exact "configuration management" title on a previous resume, is still worth considering here. What matters is the substance of the work, not whether the job title happened to match this one exactly.
Naukri Mitra has seen configuration management roles pop up more frequently across Jharkhand's tech scene lately, as companies that used to handle this informally are building it out as a dedicated function once their infrastructure outgrows what ad hoc scripts can reliably handle.
Core skills
- Strong working knowledge of Ansible or Puppet, comfortable writing and debugging playbooks rather than just running existing ones
- Scripting ability, Python or Bash both count, for building automation beyond what the config management tool handles natively
- Real experience automating infrastructure and application configuration at a meaningful scale
Extra points
Familiarity with both Ansible and Puppet, rather than deep expertise in just one, gives an edge since environments here have historically used a mix depending on which team set them up. Exposure to version-controlled infrastructure workflows and CI integration for configuration changes is a genuine plus too.
None of these extras substitute for the core skill, though. A candidate who's rock solid in one tool and has genuinely automated meaningful infrastructure with it will always be evaluated ahead of someone with surface-level exposure to several tools but no real production depth in any of them.
Pay and what's included
The role tops out at ₹1,20,000 monthly. Alongside the salary, medical coverage and standard paid leave are included in the offer, and there's a bonus tied to actual performance rather than a flat annual figure. For candidates relocating to Ranchi specifically for this role, the employer helps cover the move and assists with finding a place to live during the transition.
Lalpur is a fairly central, well-connected part of Ranchi, so the daily commute stays manageable for most people already based in the city, and settling in doesn't take long for anyone moving in from elsewhere.
The team you'd join
This role sits within a small platform engineering group that supports development teams across several products rather than one single application. Requests come in regularly for new environments, updated configuration standards, or help debugging something that behaves differently between two supposedly identical servers.
Communication with the teams this role supports happens mostly through documented requests and scheduled syncs rather than constant interruptions, which helps protect focus time for the deeper debugging work that configuration issues often demand.
Ownership here tends to be real rather than nominal. Whoever fills this role ends up being the person others check with before making a configuration change that could ripple across environments, which means both real influence and real accountability when something goes sideways.
That level of trust builds up over the first few months rather than existing from day one. Early on, new hires mostly work alongside the current team on established playbooks before getting handed anything that touches the more fragile, older parts of the infrastructure.
Applying
Send a resume that specifies which configuration management tools you've actually run in production, along with the approximate scale and the number of servers or environments managed, where relevant. The interview includes a practical round that works through a real configuration scenario, since it tests the actual skills this role needs far more directly than a general scripting quiz would.
Candidates strong in one tool, Ansible specifically for instance, but light on the other shouldn't rule themselves out. Deep expertise in a single platform that transfers well matters more than shallow familiarity with both, and the second tool tends to come quickly once the underlying configuration management concepts are solid.
