A company on Boring Road in Patna is hiring a Senior OpenShift Administrator for a full-time, on-site role. This person will own infrastructure running several production workloads on OpenShift, and the team needs someone who can keep those clusters healthy without constant hand-holding from above.
A recent push to move more internal applications onto the platform has left the environment growing faster than its documentation, and part of this role involves closing that gap while keeping day-to-day operations running smoothly. It's not a from-scratch build, but it isn't a fully mature, settled system either.
Core responsibilities
- Provision and manage cloud infrastructure across OpenShift clusters
- Automate deployment pipelines so releases go out consistently and with fewer manual steps
- Monitor system performance and reliability across the environment on an ongoing basis
- Respond to infrastructure incidents as they come up, from initial triage through resolution
Most weeks settle into a mix of proactive maintenance and reactive troubleshooting, with the balance shifting depending on what's currently deploying. A quiet week still means keeping monitoring dashboards, alert thresholds, and backup routines in shape rather than treating the calm as time off from the underlying work. Nothing here runs on autopilot for long, even when nothing is visibly broken.
Technical background required
Hands-on depth with OpenShift itself is the anchor skill here, paired with solid Kubernetes knowledge since OpenShift builds directly on top of it. Container orchestration experience beyond the basics matters, especially around scaling, pod networking, and troubleshooting resource contention under load. Comfortable, day-to-day Linux administration rounds out the technical core, since almost everything running underneath the container layer eventually traces back to the OS. Candidates who've only worked with managed Kubernetes offerings and haven't touched OpenShift's specific tooling, such as its build and image streams, should expect that gap to come up directly in the technical interview.
The company is asking for 90 months of hands-on experience in this kind of role. On the academic side, a four-year degree is expected, and the coursework should reasonably connect to computing or IT rather than being unrelated. A recognized cloud certification from AWS, Azure, or GCP is also required, reflecting how much of this infrastructure likely touches a public cloud provider even though OpenShift is the primary platform.
Additional skills worth having
Experience with CI/CD tooling such as Jenkins, GitLab CI, or Tekton speeds up the pipeline automation side of the job considerably. Infrastructure as Code experience, particularly with Terraform or Ansible, is genuinely useful for anyone expected to provision environments repeatably rather than by hand each time. Familiarity with a monitoring stack like Prometheus and Grafana helps too, since that's likely already in place and someone new will need to read it fluently within the first few weeks. A Red Hat certification tied specifically to OpenShift administration, such as the EX280, isn't required but carries weight with this employer.
Pay and benefits
This role pays up to ₹1,26,000 a month, reflecting the expected seniority and the relatively specialized skill set OpenShift administration requires. Health coverage, paid time off, and performance-linked bonuses come standard, alongside a couple of additions specific to relocating for an on-site role in this city.
- Health insurance coverage
- Paid time off
- Performance-linked bonuses
- Relocation assistance for candidates moving to Patna for this role
- Accommodation support during the initial settling-in period
Naukri Mitra notes that Patna's pool of OpenShift-specific talent is smaller than in larger metro hubs, which is part of why relocation and accommodation support show up more generously here than they might for the same role in a city like Bangalore or Hyderabad. Boring Road itself sits fairly centrally within the city, so once someone's settled, daily commuting from most residential areas isn't a major concern.
The team and how it operates
This position reports to a DevOps lead who currently manages the platform's infrastructure alongside two other engineers with adjacent specialties. The team runs a loose on-call rotation for production incidents, weighted more heavily toward whoever has the deepest familiarity with the piece of infrastructure that's acting up rather than a strict fixed schedule. That arrangement puts more responsibility on a senior OpenShift specialist during rotations, since cluster-level issues tend to land on this role by default. It also means this hire will become the informal point of escalation for anything OpenShift-related, even outside their assigned shifts.
Change management here follows a fairly standard review process. Routine configuration updates go through peer review before deployment, while anything touching production networking or cluster upgrades requires sign-off from the DevOps lead. It's not a heavily bureaucratic process, mostly a safeguard against changes that are hard to reverse quickly if something goes wrong.
Knowledge sharing happens informally rather than through scheduled training sessions. Whoever handles an incident is expected to write a short internal note afterward covering what happened and how it was resolved, which has become a reasonably useful internal archive over time for recurring issues.
The office itself runs a fairly normal schedule, with the understanding that infrastructure incidents don't always respect business hours. Anyone taking this role should expect the occasional evening or weekend interruption tied to an active incident, though the team has generally kept those manageable rather than constant. A handful of scheduled maintenance windows also happen outside business hours each quarter, planned well in advance rather than sprung on short notice.
Applying
Send a resume detailing the scale and complexity of the OpenShift or Kubernetes environments you've administered, along with specifics on any automated pipelines you've built or maintained. The interview process includes a technical discussion centered on a real infrastructure scenario, typically something involving a failing deployment or a resource bottleneck that needs to be diagnosed under time pressure. A short follow-up conversation usually covers past incident response experience in more depth, since that's a large part of the day-to-day role. Since this role is on-site at Boring Road, applicants should already live in Patna or be prepared to relocate before applying.
