When the primary data center serving this Ganeshguri, Guwahati office loses power for more than a couple of hours, the plan that gets tested is the one this Senior Disaster Recovery Engineer role is meant to own. It's a full-time, on-site position aimed at someone who's actually run a real failover before, not just written the runbook for one. The employer operates several regional data centers across the Northeast, and this hire would take primary ownership of recovery planning for the Guwahati site.
What the job covers
- Design and maintain disaster recovery plans across the company's critical systems, including defined recovery time and recovery point objectives for each one
- Own the backup infrastructure end to end, from scheduling and monitoring jobs to periodically restoring a sample backup just to confirm it actually works
- Run scheduled DR drills and failover tests, then document what broke and fix the plan accordingly
- Coordinate business continuity planning with other departments, translating vague requirements like "we can't be down for more than an hour" into a concrete technical plan
- Act as the point person during an actual incident, walking the recovery process while others handle communication with affected teams
- Keep DR documentation current enough that someone other than this engineer could execute the plan if needed
- Track and report on RTO and RPO compliance across systems to leadership on a quarterly basis
Real incidents rarely match the tabletop version. During one drill last year, a scheduled failover test uncovered that a third-party API the recovery site depended on had quietly changed its authentication method months earlier, which would have stalled the actual recovery process by hours. Catching that kind of drift before it matters is most of what makes this role worth the title. It also means the job involves a fair amount of quiet, unglamorous verification work between drills, since a DR plan that hasn't been checked in six months is really just a document at that point.
Skills required
- Practical experience building and maintaining disaster recovery plans for production systems, not just theoretical frameworks
- Deep familiarity with backup systems, including how to verify that backups are restorable rather than just assuming they are
- The ability to think through business continuity from both a technical and organizational angle, since a plan that only covers servers and ignores staffing or communication gaps isn't a complete plan
- Clear written communication, since a recovery plan is only useful if someone under pressure at 3 am can actually follow it
Nice to have
A Certified Business Continuity Professional (CBCP) credential, or an equivalent, signals a level of formal training that some candidates instead pick up through years on the job. Experience with specific backup platforms like Veeam, Zerto, or Commvault will shorten the learning curve here, since the team standardized on one of these a couple of years ago. Exposure to multi-region cloud failover on AWS or Azure is increasingly relevant as more of the infrastructure this role touches moves away from fully on-premises systems. None of these are hard requirements, but candidates who've worked with more than one of them tend to need less hand-holding with the specific tooling once they start.
Education and experience
A bachelor's degree is the baseline credential expected here, most often earned in a computer science or engineering program, though the team has hired people whose degrees came from less obviously technical fields when their hands-on DR background was strong enough to compensate. Eight years of relevant experience is expected, with a meaningful chunk of that time spent specifically on disaster recovery or business continuity work, rather than on general infrastructure administration that only occasionally touched DR. A candidate with a broader infrastructure or systems administration background is still worth considering, provided they can point to at least a couple of years in which DR planning was a primary responsibility rather than a side duty tacked onto another job.
Pay and benefits
The role pays ₹125,500 per month, which reflects the expected seniority and aligns with the monthly salary for disaster recovery engineers in Guwahati for similar roles at this level. Health insurance, paid time off, and performance-linked bonuses round out the base package. Since the position is on-site in Ganeshguri, relocation assistance and accommodation support are available for anyone moving to Guwahati from elsewhere in the country.
Working in Ganeshguri
This is a fully on-site role in Guwahati's Ganeshguri area, a part of the city with a decent concentration of IT and financial services offices. Naukri Mitra has a handful of other infrastructure and reliability roles listed from nearby employers, giving a reasonable sense of what similar senior technical positions in the region tend to pay. On-call responsibility comes with the territory here, though it's structured as a rotation across the small infrastructure team rather than resting on one person's shoulders every week. Actual incidents serious enough to trigger a real recovery effort occur maybe twice a year at this site, but the on-call phone rings far more often for smaller issues that don't require a full DR response.
The engineer in this role reports to the head of infrastructure and works closely with whoever owns each critical system, since DR planning only works when the people who understand a given application are involved in defining what "recovered" actually means for it. New hires typically spend the first month shadowing an existing DR drill before running one independently.
How to apply
Submit a resume along with specifics on any disaster recovery plans built or executed in past roles, including scale and what systems were covered. The interview process includes a scenario-based technical discussion that works through a hypothetical outage, followed by a conversation with the head of infrastructure covering on-call expectations and relocation logistics, where relevant. Candidates should be ready to walk through at least one real incident they helped recover from, including what didn't go as planned. Offers typically follow within a week or so of that final conversation, and the team is generally flexible on start dates for candidates working through a notice period elsewhere.
