Back
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Strong employer brand, mid-level role, and Hyderabad metro increase applicant competition despite niche DR specialization.
DR and resilience engineering skills are moderately transferable, though biotech regulatory context increases domain specificity.
Explicit 5–9 years requirement and mandated DR/AI resilience expertise enforce stricter shortlisting.
Lead modernization and continuous improvement of the Disaster Recovery (DR) program, including planning, strategy, dependency management, AI-enabled workflow integration, testing, governance, and operational resilience.
Collaborate with business clients and IT stakeholders to align technology recovery strategies with Business Continuity requirements and ensure enterprise-wide DR readiness.
Drive AI-enabled Disaster Recovery plan generation, dependency mapping, recovery validation, governance, and continuous improvement activities to enhance technology resilience and operational preparedness.
Master's degree OR Bachelor's degree with 5 to 9 years of relevant experience in Risk Management, Information Systems, Computer Science, Business, or related field.
Familiarity with automation concepts, AI-enabled workflows, and Agentic AI principles, with willingness to learn and apply emerging technologies in DR and Business Continuity.
Experience leading Disaster Recovery planning, recovery testing, dependency mapping, governance, and operational resilience initiatives.
Work Experience Required: 5 to 9 years in relevant fields as specified; Notice period: Not explicitly mentioned in the JD.
Experienced in leading and influencing cross-functional teams in Disaster Recovery and Business Continuity within complex, global, virtual environments.
Demonstrated ability to integrate AI and automation technologies into DR workflows to improve recovery planning, orchestration, and governance.
Strong project management skills with a systems and automation mindset, able to communicate effectively with both technical and non-technical stakeholders.