Senior Kubernetes Engineer, Ranjit Avenue, Amritsar
A company on Ranjit Avenue is hiring a Senior Kubernetes Engineer for a full-time, on-site position, with a salary of up to ₹1,74,000 per month. This is a senior seat on the infrastructure team, not a title bump for someone still building core Kubernetes fundamentals, and the compensation reflects that.
The role owns the container platform on which a growing set of production services runs. When deployments go smoothly and clusters scale without drama, that's this person's work showing up as an absence of problems rather than a headline achievement.
The infrastructure has grown rapidly over the past year, and the tooling hasn't fully caught up yet. Part of this role is closing that gap, standardizing deployment patterns that currently vary team to team, and building the kind of guardrails that let other engineers self-serve without needing a Kubernetes specialist for every change.
Responsibilities
- Design, operate, and scale Kubernetes clusters supporting multiple production and staging environments
- Build and maintain CI/CD pipelines that move code from commit to deployment with minimal manual intervention
- Automate infrastructure provisioning so environments can be stood up or torn down predictably, without hand-editing configs each time
- Author and maintain Helm charts for application deployments, keeping them versioned and reusable across services
- Troubleshoot cluster and container issues across development and production, from pod scheduling failures to networking problems between services
- Set and enforce resource limits, autoscaling policies, and node pool strategy as workloads grow
Incident response is part of the job, not an occasional exception. When a cluster misbehaves during a deploy window, this person is expected to diagnose it quickly and clearly communicate what's happening to anyone else affected, rather than going quiet while investigating.
A typical week mixes planned work, like migrating a service to a new node pool or tightening resource requests that have been set too loosely, with the occasional afternoon lost entirely to a networking issue nobody can explain until someone traces it through three layers of abstraction. Both kinds of work matter, and neither should surprise anyone taking this role.
Background the role expects
The company wants a four-year technical degree- engineering, information systems, or a similar program to clear the bar, plus a cloud certification through one of the major providers; AWS, Azure, or GCP all count. Neither the degree nor the certification substitutes for the other here. About five and a half years of hands-on infrastructure experience is expected, with a meaningful chunk of it spent specifically running Kubernetes in production rather than in a lab or a course.
Naukri Mitra has recently listed several Cloud and DevOps roles out of Amritsar, and this one stands out for how narrowly it's scoped to container orchestration rather than general cloud administration. Candidates coming from a broader DevOps background will need to show real Kubernetes depth specifically, not just adjacent cloud experience.
The certification requirement is worth a note on its own. It's not there to check a box during screening; it's there because the role involves real decisions about cloud provider services that directly affect how the clusters run, and someone without that background tends to need months to catch up on the context a certified candidate already has.
Must-have skills
- Strong hands-on Kubernetes experience, including cluster administration and troubleshooting
- Docker and container image management, including building and optimizing images for production
- Helm chart authoring and maintenance
- Solid Linux systems knowledge, since most of the debugging eventually lands at the OS level
Good to have
Experience with service mesh tools (Istio or Linkerd) will strengthen an application, though it isn't required for consideration. Familiarity with GitOps workflows using ArgoCD or Flux is a plus, as is prior exposure to a managed Kubernetes service such as EKS, AKS, or GKE, as well as self-managed clusters.
Compensation and what comes with it
Bonuses here are tied to concrete infrastructure metrics, uptime, deployment success rate, that kind of thing, rather than a subjective annual review score. Medical cover and standard paid leave come with the offer as well. Since the position requires relocating to Amritsar for anyone not already based there, the employer covers relocation costs and helps arrange accommodation during the transition.
Ranjit Avenue is a well-established commercial area in Amritsar, and the office is easy to reach whether someone's commuting locally or settling in after a move from elsewhere.
Amritsar isn't a typical hub for senior infrastructure roles at this pay level, and this employer has said openly that they're paying to compete with metro salaries specifically because the local talent pool for Kubernetes-depth engineers is thin. That's less a marketing point and more a practical reason the number is what it is.
Team context
This role reports to the infrastructure lead and works closely with a small group of backend engineers who regularly deploy to the platform. Decisions about cluster architecture and tooling largely rest with this person once they're ramped up, since there isn't a large committee structure slowing down infrastructure choices.
Given the role's seniority, there's an expectation to mentor junior engineers in Kubernetes concepts as the team grows, even though this isn't formally a people-management position. That mix of hands-on ownership and informal mentorship tends to suit engineers who want technical depth without giving up direct infrastructure work in favor of management responsibilities.
The infrastructure lead this role reports to has made it clear they're looking for someone who can push back on decisions when the technical reasoning supports it, not just implement whatever's requested. Strong opinions about cluster design, held loosely enough to update when new information comes in, tend to work well on this particular team.
How to apply
Submit a resume that specifies which Kubernetes distributions and cloud providers you've actually run in production, along with rough scale details like cluster size or request volume where relevant. The interview process includes a technical round centered on real troubleshooting scenarios, not whiteboard trivia, so recent hands-on work matters more than certifications alone.
Candidates moving from a metro city should factor in the cost-of-living difference: Amritsar is considerably cheaper than Bangalore or Gurgaon for most day-to-day expenses, which changes how the salary figure lands compared to a similar number in a larger city. It's worth weighing that alongside the relocation package rather than looking at the salary number in isolation.
