Senior Specialist - Change and Release (Inception42)

Inception42, a G42 company, is the region\u2019s leading innovator of AI-powered domain-specific as well as industry-agnostic products, built on a rich heritage of research and development. Within the G42 ecosystem, Inception functions as the core intelligence layer \u2013 transforming data and compute infrastructure into real-world, applied AI solutions. Beyond its commercial endeavors, Inception is committed to creating positive societal impact. For more information, please visit www.inception42.ai Inception42, a G42 company, is the region\u2019s leading innovator of AI-powered domain-specific as well as industry-agnostic products, built on a rich heritage of research and development. Within the G42 ecosystem, Inception42 functions as the core intelligence layer \u2013 transforming data and compute infrastructure into real-world, applied AI solutions. Beyond its commercial endeavors, Inception42 is committed to creating positive societal impact. For more information, please visit www.inceptionai.ai Enable Inception42 to introduce changes and releases safely, predictably and at the pace a product company needs. You will coordinate change risk, release readiness and communication across services supporting internal teams and external customers. This is a senior practitioner role with independent responsibility for assigned changes and releases. You will make controls practical, evidence-based and proportionate to risk, working closely with the teams building and operating the products. Works with the Lead Specialist, IT Service Management, Product Engineering, Quality Engineering, Application Support, Platform Reliability, Infrastructure and Information Security. \u2022 Operate and improve change enablement and release practices, applying agreed policies and escalating exceptions to the appropriate decision owner. \u2022 Review changes for customer impact, dependencies, risk, testing evidence, implementation steps and recovery readiness. Ensure the right owners make and record approval decisions. \u2022 Maintain standard, normal and emergency change paths. Develop pre-authorised change models with clear eligibility criteria and review their ongoing suitability. \u2022 Coordinate release plans and calendars across teams, identifying shared-service conflicts, business constraints and dependencies early. \u2022 Confirm release readiness with Engineering, Quality and Support, including acceptance evidence, known issues, configuration and data changes, runbooks and support handover. \u2022 Facilitate go/no-go decisions and targeted change reviews; record decisions and unresolved risks with accountable owners. \u2022 Agree deployment validation, rollback or recovery criteria, including situations where database or data changes cannot be simply reversed. \u2022 Work with engineering teams to capture change and release evidence from delivery pipelines and repositories, reducing manual duplication while preserving traceability. \u2022 Coordinate release notes, maintenance notices and stakeholder updates. Explain expected impact, timing and support arrangements in language users can understand. \u2022 Track post-release health and early-life support with operational teams. Coordinate recovery decisions and incident handover when changes cause service degradation. \u2022 Review failed and emergency changes, track corrective actions and report on change failure, approval delays, release predictability and recovery performance. \u2022 Within the first six months: Change paths, decision authorities and release readiness expectations are clear and in consistent use; Assigned releases have visible dependencies, communication plans and tested recovery arrangements; A baseline exists for change outcomes, approval delays and release-related incidents. \u2022 Within the first twelve months: Changes and releases demonstrate improved predictability and fewer avoidable failures against agreed baselines; Routine changes flow efficiently through approved models and automated evidence capture; Post-release learning results in visible improvements to testing, readiness and recovery. \u2022 Strong practical experience coordinating production changes and software releases across multiple technical teams. \u2022 Working knowledge of ITIL change enablement and release management, with evidence of applying controls proportionate to risk. \u2022 Understanding of software delivery lifecycles, version control, CI/CD pipelines, environment promotion, testing and deployment approaches. \u2022 Ability to challenge incomplete release plans, dependency assessments and rollback assumptions while working constructively with engineers. \u2022 Experience maintaining change records and release evidence in ITSM and engineering tools, with accurate reporting and follow-through. \u2022 Clear written and verbal communication, strong planning skills and sound judgement during incidents, conflicting priorities and time-sensitive decis

Strong practical experience coordinating production changes and software releases across multiple technical teams. Working knowledge of ITIL change enablement and release management, with evidence of applying controls proportionate to risk. Understanding of software delivery lifecycles, version control, CI/CD pipelines, environment promotion, testing and deployment approaches. Ability to challenge incomplete release plans, dependency assessments and rollback assumptions while working constructively with engineers. Experience maintaining change records and release evidence in ITSM and engineering tools, with accurate reporting and follow-through. Clear written and verbal communication, strong planning skills and sound judgement during incidents, conflicting priorities and time-sensitive decisions.

Operate and improve change enablement and release practices, applying agreed policies and escalating exceptions to the appropriate decision owner. Review changes for customer impact, dependencies, risk, testing evidence, implementation steps and recovery readiness. Ensure the right owners make and record approval decisions. Maintain standard, normal and emergency change paths. Develop pre-authorised change models with clear eligibility criteria and review their ongoing suitability. Coordinate release plans and calendars across teams, identifying shared-service conflicts, business constraints and dependencies early. Confirm release readiness with Engineering, Quality and Support, including acceptance evidence, known issues, configuration and data changes, runbooks and support handover. Facilitate go/no-go decisions and targeted change reviews; record decisions and unresolved risks with accountable owners. Agree deployment validation, rollback or recovery criteria, including situations where database or data changes cannot be simply reversed. Work with engineering teams to capture change and release evidence from delivery pipelines and repositories, reducing manual duplication while preserving traceability. Coordinate release notes, maintenance notices and stakeholder updates. Explain expected impact, timing and support arrangements in language users can understand. Track post-release health and early-life support with operational teams. Coordinate recovery decisions and incident handover when changes cause service degradation. Review failed and emergency changes, track corrective actions and report on change failure, approval delays, release predictability and recovery performance.