Principal Engineer, Product Engineering - Claims

prudential; Kuala Lumpur; On-site; MYR 180,000 - 260,000; Full time

Job summary

Prudential Principal Engineer, Product Engineering - Claims will support the Tech Product Owner in delivering the Claims technology roadmap. The role turns prioritised requirements into clear delivery plans, coordinates engineering execution across squads, tracks dependencies and ensures releases are delivered with quality and operational readiness.

The successful candidate will manage delivery planning, backlog readiness and cross-team coordination across QA, DevSecOps, architecture, data and

Qualifications

• Experience delivering complex engineering programs across multiple squads.
• Strong collaboration with product, QA and operations.

Responsibilities

• Translate prioritized roadmap items into executable delivery plans.
• Coordinate sprint, release and implementation planning across squads.
• Monitor progress, risks and actions to ensure timely delivery.
• Ensure release readiness, testing and operational readiness.
• Manage dependencies and cross-team handoffs.
• Provide structured status updates for stakeholders.

Job description

Prudential's purpose is to be partners for every life and protectors for every future. Our purpose encourages everything we do by creating a culture in which diversity is celebrated and inclusion assured, for our people, customers, and partners. We provide a platform for our people to do their best work and make an impact to the business, and we support our people's career ambitions. We pledge to make Prudential a place where you can Connect, Grow, and Succeed.

The Principal Engineer, Product Engineering - Claims sits within the Engineering team and supports the Tech Product Owner in delivering the Claims technology roadmap agreed with the Business Product Owner. The role is responsible for turning prioritised product and technology requirements into clear delivery plans, coordinating engineering execution across squads, tracking dependencies, maintaining delivery discipline, and ensuring releases are delivered with appropriate quality, evidence and operational readiness.

Key Accountabilities

1. Delivery planning and execution support
   • - Support the Tech Product Owner in converting prioritised roadmap items, product backlog priorities and technical requirements into executable delivery plans.
   • - Coordinate sprint, release and implementation planning across engineering squads, ensuring scope, milestones, owners, dependencies and timelines are clear.
   • - Track progress against committed delivery outcomes and maintain visibility of delivery status, blockers, risks and actions.
   • - Ensure delivery plans are realistic, sequenced and aligned with engineering capacity, technical dependencies and release windows.
   • - Follow through on delivery actions across squads, ensuring issues are closed, decisions are recorded and commitments are met.
2. Backlog readiness and requirements coordination
   • - Work with the Tech Product Owner, Business Analysts, engineers, QA and relevant business stakeholders to ensure backlog items are clear, refined and ready for delivery.
   • - Help maintain traceability between agreed business priorities, technical requirements, user stories, acceptance criteria, testing scope and release outcomes.
   • - Identify gaps in requirements, acceptance criteria or delivery assumptions and escalation them to the Tech Product Owner for prioritisation or decision.
   • - Support backlog grooming, sprint planning and refinement sessions by ensuring inputs, dependencies and open questions are prepared in advance.
   • - Ensure AI-supported or automation-related requirements have clear human review, testing and control expectations where relevant.
3. Engineering delivery coordination
   • - Coordinate day-to-day delivery activities across engineering, QA, DevSecOps, architecture, data, AI and platform teams.
   • - Help the Tech Product Owner manage delivery dependencies, sequencing, blockers and cross-team handoffs.
   • - Ensure squads have the required inputs, decisions and technical support to progress delivery efficiently.
   • - Monitor sprint readiness, delivery velocity, defect trends, testing progress and release confidence indicators.
   • - Escalate delivery risks, unresolved dependencies and capacity constraints to the Tech Product Owner, Product Tech Lead, Engineering Lead or relevant accountable owner.
4. Release readiness and implementation assurance
   • - Coordinate release readiness activities, including testing completion, defect closure, control evidence, operational readiness, deployment plans and go/no-go preparation.
   • - Ensure release checklists, implementation evidence and decision records are maintained and available for review.
   • - Work with QA, DevSecOps, Operations, Service Management and Technology teams to confirm that releases are supportable, resilient and ready for deployment.
   • - Track post-release issues, hypercare actions and lessons learned, ensuring feedback is reflected in future delivery cycles.
   • - Support the Tech Product Owner in preparing clear release updates and delivery confidence assessments for stakeholders.
5. Risk, dependency and issue management
   • - Maintain a clear view of delivery risks, issues, assumptions and dependencies across the Claims technology delivery scope.
   • - Proactively identify blockers and follow up with accountable owners to drive timely resolution.
   • - Ensure risks and issues are clearly documented, impact-assessed and escalated through the appropriate delivery or governance forums.
   • - Support dependency management across engineering, business, operations, data, AI, architecture, security and external partners.
   • - Provide structured status updates that distinguish between items requiring action, decision, escalation or monitoring.
6. Delivery reporting and stakeholder communication
   • - Prepare concise delivery updates for the Tech Product Owner, engineering leadership and relevant governance forums.
   • - Provide clear reporting on progress, risks, dependencies, release readiness, quality indicators and decisions required.
   • - Translate delivery complexity into simple, actionable messages for stakeholders.
   • - Maint