Terraform Engineer, Amritsar (Part-Time, On-site)
A logistics-heavy retailer's regional data center on Ranjit Avenue needs someone to keep its cloud footprint provisioned correctly and running without surprises. This is a part-time, on-site Terraform Engineer role based in Amritsar, Punjab, with a salary of up to ₹41,000 per month.
The environment this person is joining has grown past the point where anyone can safely make changes by hand. Servers get spun up through consoles, someone forgets to tear down a test resource, and by the time anyone notices, the monthly cloud bill has a line item nobody can explain. Getting that under control through code, reviewed and version-tracked, is the actual reason this seat exists.
What you'd hold a bachelor's degree in
The team looks for a bachelor's degree in computer science, information technology, or a comparably technical field as the baseline credential for this seat. What matters more day-to-day is whatever you've actually touched: provisioning cloud resources by hand or through code, working with containers, and building or maintaining pipelines that push code out without a human clicking deploy every time. If your degree is in a different discipline but your project history covers that ground, that history counts for a lot here.
Experience expected
The role calls for 48 months of hands-on experience in cloud or DevOps work. That's not a hard cutoff carved in stone, but candidates well under that mark typically find the pace of incident response and infrastructure changes harder to keep up with from day one. What the hiring team weighs more heavily than a raw number is whether that time was spent actually writing and applying infrastructure code rather than clicking through a cloud console, since the two build genuinely different instincts.
What you'll be doing
The day-to-day centers on infrastructure that must operate reliably and change safely. Specifically, you'll be responsible for:
- Provisioning and managing cloud infrastructure using Terraform and related infrastructure-as-code practices
- Building and maintaining automated deployment pipelines so releases move through environments consistently
- Monitoring system performance and reliability across the environments you manage
- Responding to infrastructure incidents as they come up, including after-hours situations when something breaks during a deployment window
Some weeks are routine, mostly maintenance and small provisioning requests. Other weeks bring a failed rollout or a capacity issue that needs fixing before the next shift starts, and that unevenness is part of what the role actually looks like rather than something glossed over here.
A typical ticket might start with a developer asking for a new staging environment that mirrors production networking rules. Writing that module, running a plan, catching the security group misconfiguration before it applies, and getting it merged is a normal Tuesday. A typical incident might start with a load balancer health check failing at 6pm on a deploy day, which means tracing recent state changes to figure out which apply introduced the problem, then rolling it back.
Skills you'll need
The core toolkit for this seat is fairly specific:
- Terraform, used regularly enough that you're comfortable writing and reviewing modules, not just running them
- Infrastructure as code practices more broadly, including version control for infrastructure changes
- Working knowledge of at least one major cloud platform
- Scripting ability, whether that's Bash, Python, or something similar, for the glue work Terraform alone won't cover
Beyond that baseline, a few things would strengthen an application without being required outright: exposure to a CI/CD tool such as Jenkins or GitLab CI, some familiarity with container orchestration through Kubernetes, and any hands-on time with monitoring stacks like Prometheus or Grafana. None of these are dealbreakers if you're missing one; Naukri Mitra has placed candidates in similar roles who picked up the monitoring piece on the job. Familiarity with state file management in a team setting, meaning remote backends and locking rather than a single local state file, tends to separate candidates who've worked solo from those who've worked on a shared infrastructure codebase.
Compensation and schedule
This is a part-time position paying up to ₹41,000 per month, on-site at the Ranjit Avenue office in Amritsar, rather than remote or hybrid. Hours are structured around a part-time schedule, and the on-site requirement is fixed given the nature of the infrastructure work and its alignment with the local team's on-call rotation.
Benefits
- Pro-rated paid leave in line with part-time employment terms
- Flexible in-office scheduling within the part-time structure
- Performance-based incentives tied to reliability and delivery outcomes
- Relocation assistance and accommodation support, since candidates relocating to Amritsar for an on-site role are common in this market
Who tends to do well here
People who like this kind of work usually enjoy the moment an infrastructure change finally applies cleanly after three failed plans. If troubleshooting a broken pipeline at an odd hour sounds like a reasonable trade for stable, well-scoped work the rest of the week, this fits. If you'd rather build application features than keep the plumbing running, it probably won't.
The wider engineering group here is small enough that this hire will end up talking directly to the developers whose environments they're provisioning, rather than filing tickets into a queue and waiting. That suits someone who doesn't mind explaining a decision out loud, and who's willing to say no to a request when the underlying reason for it doesn't hold up on inspection.
Career path from here
Terraform engineering in a market like Amritsar tends to open into either a senior DevOps or platform engineering track, or a move toward site reliability work as teams around here scale their cloud footprint further. Pay for the senior version of this work in Punjab has been climbing as more companies shift infrastructure from manual setup to code, so time spent here building a solid Terraform foundation tends to pay off later rather than being a dead end. This particular opening, a part-time Terraform engineer job in Amritsar that doesn't require relocation, is a reasonably direct route into that foundation for someone who wants to stay local while building it.
How to apply
Send your application through the listing, along with a resume that clearly states which cloud platforms and CI/CD tools you've actually used, not just a list of skills. If you've got a public repository with sample Terraform modules, link it. Candidates who make it past the initial screen should expect a follow-up call where they'll walk through how they'd handle a specific provisioning or rollback scenario, rather than a generic behavioral interview.
Given the part-time hours and the office location near Ranjit Avenue, candidates already based in or near Amritsar will have an easier commute, though the relocation support mentioned earlier is available to anyone coming from outside Punjab. Interviews are scheduled within a week or two of the application review, and the team aims to make a decision within a few days of the final conversation, rather than leaving candidates waiting.
