A company at Infopark, Kakkanad, in Kochi is hiring a Senior Site Reliability Engineer, full-time and on-site, with pay up to ₹1,78,000 a month. This seat requires 84 months of hands-on experience running production infrastructure, and the role carries direct responsibility for how reliably the company's systems stay up. The team supports a handful of customer-facing services with meaningful uptime commitments, so this isn't an internal-tools role where an outage mostly stays invisible to the business.
What the role covers
- Provision and manage cloud infrastructure across the environments this team supports
- Automate deployment pipelines so releases happen consistently rather than depending on manual steps someone might forget
- Monitor system performance and reliability continuously, catching drift before it becomes an outage
- Respond to infrastructure incidents as they arise, including the ones that happen outside standard working hours
A recent incident on a comparable team: a memory leak in a background job slowly degraded performance across an entire cluster over about ten days, with no single alert loud enough to flag it early. By the time anyone noticed, half the fleet needed a rolling restart under live traffic. Catching that kind of slow-building problem before it turns into an emergency is a core part of what this role is meant to prevent. It's rarely the dramatic outages that cause the most damage here. It's the slow, quiet ones that go unnoticed until they're already widespread. Good monitoring is what turns that second kind of problem back into something manageable.
Skills this role depends on
- Monitoring tools, comfortable setting up alerting that catches real problems without drowning the team in noise
- Incident response, including staying calm and methodical while a system is actively degraded
- Automation scripting, since manual intervention doesn't scale past a certain point
- Kubernetes, running and troubleshooting workloads in production rather than just deploying to a demo cluster
- Linux administration, deep enough to diagnose problems that Kubernetes itself won't surface
Beyond that core set, experience with Terraform or another infrastructure-as-code tool speeds up a lot of the provisioning work this role touches. Familiarity with Prometheus and Grafana specifically helps, since that's the stack this team already runs. Go or Python scripting is worth mentioning too, since much of the automation work here ends up being custom rather than off-the-shelf. Some exposure to on-call tooling like PagerDuty or Opsgenie is useful too, and if you've done any chaos engineering work, mention it, since this team wants to build out deliberate failure-mode testing further. None of these extras are required to get hired, but a candidate who brings two or three will spend less time getting oriented and more time contributing to the team's existing priorities.
Education, certification, and experience
A bachelor's degree is expected, and a recognized cloud certification AWS, Azure, or GCP) is required alongside it. 84 months of hands-on experience with cloud infrastructure and containerized deployments is the standard here, ideally with most of it spent carrying real on-call responsibility rather than only building systems someone else supported. Whichever cloud platform your certification covers, the team will expect you to translate that knowledge to whichever provider the current infrastructure actually runs on. A candidate who's mostly worked in a pure development role, even with strong infrastructure knowledge, will need to demonstrate genuine operational experience to be considered at this level. The certification requirement is checked early in the process, so make sure it's clearly listed rather than mentioned only in passing.
Team and on-call structure
This role reports to the head of platform engineering and joins a team of three other SREs who currently rotate on-call responsibility weekly. One current team member was hired through Naukri Mitra about a year ago and has since built much of the alerting logic the team relies on today. That alerting work is still evolving, and whoever takes this role will likely have real input into what gets refined next rather than inheriting a finished system with no room to improve it. Expect a genuine share of on-call weeks as part of the rotation, with compensation structured to reflect that responsibility rather than treating it as an unpaid extra. The rotation currently runs one week in four, though that ratio may shift slightly as the team grows.
Some weeks involve almost entirely proactive work, tightening monitoring or automating a manual process. Others go mostly to incident response when something in production misbehaves. Both are a normal part of the role, and the balance shifts depending on what's currently stable and what isn't. A quiet month usually means the previous few months of proactive work actually paid off, not that nothing needs attention.
Compensation and benefits
- Salary up to ₹1,78,000 per month
- Health insurance
- Paid time off
- Performance-linked bonuses tied to system reliability metrics
- Relocation assistance and accommodation support for candidates moving to Kochi
Anyone comparing site reliability engineer salary in Kochi per month figures across Infopark will find this one sits toward the top of the local range, reflecting both the seniority bar and the on-call responsibility built into the role. Bonus payouts here track uptime and mean time to recovery more closely than any subjective performance narrative.
Applying
The role is on-site at Infopark, Kakkanad, so relocation or a reliable local commute is expected. Send a resume that details specific incidents you've resolved, systems you've owned, and any reliability metrics you've directly influenced. Numbers help here: uptime percentages, incident counts, mean time to recovery, more than a general description of your responsibilities. Candidates exploring site reliability engineer jobs for experienced professionals in Kochi should expect a technical round covering a real incident scenario, followed by a conversation with the platform engineering lead about on-call expectations and team fit. Most candidates hear back within a week or so of the final round. If you're weighing this against another offer, mention it early, since the team has some flexibility on start dates for the right hire.
