This Associate Business Continuity IT Analyst position, on-site at Infocity in Chandrasekharpur, Bhubaneswar, pays up to ₹60,000 per month and sits at the intersection of software development and disaster planning. It falls under the Software Development category, though the actual focus is on making sure critical systems keep running or recover quickly when something breaks.
What the role covers
The job blends hands-on technical work with the planning side of business continuity. Day-to-day, that involves:
- Building and maintaining internal tools that track continuity plans, recovery procedures, and incident response steps
- Coordinating with the teams building new systems so failover and recovery paths get designed in from the start, not bolted on afterward
- Reviewing continuity documentation and runbooks to catch gaps before a real incident exposes them
- Conducting risk assessments across departments to identify which systems would hurt the business most if they went offline
- Troubleshooting issues that surface during continuity drills or, occasionally, during an actual failover event
Most of this work happens quietly, updating a runbook here, flagging a single point of failure there. Then a scheduled continuity drill exposes something nobody noticed, like a backup system that technically exists but hasn't been tested in eighteen months and fails to spin up correctly under simulated load. Finding that kind of gap before it becomes a real outage is the entire point of the job.
Not every week involves a drill or a crisis. A fair chunk of the calendar goes toward quieter work: interviewing a department about how they'd actually keep functioning if their main system went down for a day, then writing that up in a way someone unfamiliar with the department could follow during an actual emergency. It's unglamorous work most of the time, right up until the one week it isn't.
Skills
Business continuity planning experience, solid risk assessment ability, and genuinely thorough documentation habits form the core of what this role needs. A continuity plan that only lives in someone's head is functionally useless during an actual crisis, so writing things down clearly matters as much as the planning itself. A well-written runbook should let someone unfamiliar with a system follow the recovery steps without needing to call the person who wrote it.
A few additional skills would strengthen an application. Some scripting ability- Python works well for this- helps when automating the tools used to track and test continuity procedures. Familiarity with ISO 22301, the international standard for business continuity management, signals someone who understands the formal side of the discipline. Prior exposure to disaster recovery testing specifically, rather than just planning on paper, matters a great deal once an employer needs someone who's actually run a failover drill before. Experience with a specific incident management platform is a plus but rarely a dealbreaker, since most of these tools work similarly once someone understands the underlying process they're meant to support.
Education and background needed
A bachelor's degree is required, typically in computer science, information technology, or a related field, which aligns with the software side of this hybrid role. The listed experience requirement is twelve months, positioning this as an associate role for someone with a first year of relevant work already behind them rather than a completely fresh graduate. That year doesn't need to have been spent specifically on business continuity; a year of general software development experience, paired with a genuine interest in risk and resilience work, is a realistic path into this role.
Compensation and benefits
Pay for this position runs up to ₹60,000 a month. Health insurance, paid time off, and provident fund contributions are included, and since the role is on-site, relocation assistance and accommodation support are available for candidates moving to Bhubaneswar from elsewhere. Those last two matter more than they might elsewhere in the country, since the specific mix of software and risk-management background this role wants isn't always easy to find locally.
Naukri Mitra has noticed more employers in Odisha building out formal risk and continuity functions rather than leaving disaster recovery as an unwritten responsibility that someone picks up during an actual outage, and this role reflects that shift toward treating resilience planning as a dedicated job.
Where it's based
Infocity, Chandrasekharpur, has pincode 751024 in Bhubaneswar, Odisha, and the office there operates entirely in person for this role. No hybrid schedule, no remote option. Department heads don't always have time for a scheduled video call between meetings, but they'll often make five minutes for someone who walks over to their desk, which is a big part of why risk assessment work here stays tied to physical presence.
Why this role exists
A lot of companies only take business continuity seriously after a bad outage costs them real money or a client relationship. This role exists partly because that lesson has already been learned once here, and the employer would rather catch the next gap during a planned drill than during an actual crisis. That context shapes the day-to-day work more than a generic job description usually conveys: this isn't a checkbox compliance role; it's meant to actually prevent a repeat.
The person in this seat works across departments that don't normally talk to each other much- engineering, operations, sometimes finance- which means explaining technical risk in terms each group actually cares about is a real part of the job. A finance team doesn't need to hear about milliseconds of failover latency; they need to know how many hours a payment system could be down before it actually becomes their problem, too.
Applying
The application goes through the usual channel listed on this posting. A resume that calls out risk assessment, disaster recovery, or continuity documentation specifically will stand out more than one that buries those under a general software development history, even if they were only part of a broader role before. Expect the interview to spend real time on a hypothetical: given a system description, where would this candidate look first for a single point of failure? That question tends to say more about fit than any certification listed on a resume.
