Senior Specialist: Delivery Quality and Stability at PPS

Job Advert Summary    

• To protect production stability by enforcing delivery quality, release readiness, and disciplined learning across DevSecOps. The role exists to prevent avoidable release failures, reduce repeat incidents, and ensure that ITIL practices, configuration discipline, and quality evidence translate into measurable operational improvement. The role operates across the full release lifecycle, validating readiness before release and ensuring learning after release, particularly when delivery pressure is high.

Minimum Requirements    
Education:

• Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related discipline (Master’s or advanced certifications preferred)

Experience:

• Minimum of 15 years of consulting experience in Business, Technology, or Operational Transformation
• Minimum of 5 years in IT operations, governance, service management, or reporting roles, with at least 2 years in a leadership or specialist capacity
• At least 2 years of direct experience in managing time solutions (for example ActiTime or equivalent) including configuration, governance, and reporting
• ITIL certification with demonstrated depth in Change, Incident, and Problem practices
• Formal training or applied experience in root cause analysis methodologies
• Demonstrated understanding of non-functional quality and operational risk aligned to recognised quality models such as ISO 25010
• Education and certifications must be supported by demonstrable impact on release outcomes, incident reduction, and operational stability

Competencies:

• Attention to Detail
• Problem Solving
• Results Orientation
• Relationship Building
• Root-Cause Analysis 
• ITIL Practice Proficiency
• Influence

Duties and Responsibilities    

• Define and maintain a small, mandatory set of delivery quality and readiness standards for all releases
• Verify reliability, performance, security, and maintainability using objective evidence appropriate to the service context
• Validate readiness before deployment, including rollback and recovery plans
• Ensure material incidents and recurring issues result in credible root-cause analyses and corrective actions
• Challenge superficial, opinion-based, or inconclusive analysis
• Drive post-incident and post-release reviews that result in concrete improvements to standards, controls, or ways of working
• Reduce repeat incidents over time through disciplined learning and follow-through
• Drive practical execution of priority ITIL practices: Incident, Problem, Change, Release, Service Configuration, and Service Level Management
• Intervene when process adherence increases without improvements in operational performance
• Maintain accurate and up-to-date CMDB, asset, and licence information to support change impact analysis, incident response, and operational decision-making
• Address poor configuration or asset discipline that introduces uncertainty, operational risk, or repeat failures.Maintain reliable effort data for cost allocation and efficiency analysis
• Use time data to identify rework and inefficiencies caused by poor quality or repeated failures
• Ensure time governance supports release planning, change safety, and stability — not replace or compete with them
• Translate incidents, release issues, and governance findings into sustainable improvements across delivery and operations
• Collaborate with development, testing, and operations teams to ensure lessons learned are embedded into stronger controls and improved readiness

Deadline:26th February,2026