Associate Ansible Automation Engineer, Ranjit Avenue — Amritsar
A company based in Ranjit Avenue is hiring an Associate Ansible Automation Engineer for a full-time, on-site role. This is an early-career DevOps role, aimed at someone who's already written real Ansible playbooks rather than someone who's only read about configuration management in a course.
Most of the infrastructure here is managed through playbooks rather than manual server changes, which means a mistake in one file can ripple across an entire fleet of machines at once. A playbook that isn't idempotent can restart a service every time it runs, even when nothing changed, quietly wasting cycles and occasionally causing unexpected outages. One recent case involved a playbook that reset a load balancer's configuration on every single run, silently dropping a handful of connections each time it fired overnight. Catching that kind of subtle bug before it reaches production is a real part of what this role is for.
The role covers the following on a day-to-day basis:
- Building and maintaining CI/CD pipelines that incorporate configuration management
- Automating infrastructure provisioning through Ansible playbooks and roles
- Troubleshooting issues that appear across both development and production environments
- Testing playbook changes in a staging environment before they reach live systems
Ansible experience is required, along with a working understanding of broader configuration management practices, strong scripting skills, and genuine comfort operating in Linux environments day-to-day. Someone who's built playbooks for a real environment, even a small personal lab setup, tends to have an easier time in this role than someone who's only used Ansible in a guided tutorial. A few extra skills would help without being mandatory: exposure to Terraform for infrastructure provisioning outside configuration management, basic Docker knowledge, and familiarity with Git-based workflows for tracking playbook changes over time.
The company asks for a bachelor's degree as the minimum education requirement, without tying that to a single specific major, since the practical automation skills demonstrated through past work tend to matter more here than the exact subject studied. On the experience side, they're looking for 21 months in a similar role, which for most candidates means at least one prior job or a substantial internship involving hands-on configuration management rather than purely theoretical exposure.
Pay for this position goes up to ₹63,500 a month, on-site, full-time. Benefits include:
- Health insurance
- Paid time off
- Provident fund contributions
- Relocation assistance and accommodation support for candidates moving to Amritsar
Ranjit Avenue is one of Amritsar's more commercially developed areas, and the office sits close enough to the main market stretch that lunch options and everyday errands aren't a hassle for people relocating here. Naukri Mitra has seen more DevOps and automation roles in Amritsar over the past year or two as smaller IT firms take on more infrastructure work for outside clients, and this listing fits that broader pattern.
The DevOps team here is small, four people total including this hire, so an associate-level engineer ends up with more direct exposure to production systems than they might get on a larger, more layered team elsewhere. That comes with more responsibility earlier than some candidates expect from an associate title, though a senior engineer reviews playbook changes before anything significant reaches production.
Interviews for this role typically include a short hands-on exercise involving writing or debugging an Ansible playbook against a sample scenario, followed by a conversation about how the candidate has approached automating a manual process in a past role. People who can talk through a specific automation project they built, including what broke the first time they ran it, tend to do better in that conversation than someone who can only describe Ansible concepts in the abstract.
Applications get reviewed as they come in rather than on a fixed schedule. Anyone currently living outside Amritsar who's willing to relocate should mention that clearly in their application, since the relocation and accommodation support gets worked out early in the process rather than left for a final offer stage.
The environment spans a mix of on-premise servers and a handful of cloud instances, so playbooks need to work reliably across both rather than assuming one consistent setup everywhere. Differences in package availability or default configurations between environments show up more often than newer engineers expect, and learning to write playbooks that handle those differences gracefully, rather than failing halfway through a run, is one of the harder early skills to pick up.
Testing changes before they touch production matters as much as writing the playbook itself. A change that looks correct in a code review can still behave unpredictably the first time it runs against a real server with an unexpected package version or a slightly different filesystem layout than the test environment had. Part of this role's mandate is catching that gap in staging, since a rollback after a bad production run costs far more time than a thorough test cycle beforehand.
New hires generally spend their first couple of weeks reviewing existing playbooks and shadowing a senior engineer on smaller changes before taking on anything independently. The team treats that ramp-up period as standard onboarding rather than a trial phase, and most associates start owning smaller automation tasks on their own within a month.
Growth from this role usually points toward a mid-level DevOps engineer position with broader ownership of infrastructure decisions, not just configuration management. A couple of engineers who started in a similar associate role here have moved into that next tier within roughly a year and a half, which lines up reasonably well with the experience level this posting is asking for from new applicants.
Amritsar's IT sector remains smaller than the bigger metro hubs, which means fewer competing employers for a role like this one but also a smaller pool of engineers already experienced with configuration management tools specifically. That combination tends to favor candidates with solid, demonstrable Ansible experience, since companies here compete harder to retain people who clear that bar.
