Digital Engineering Lead

Role Summary The Senior Digital Engineering Lead is a senior hands-on technical leader accountable for two things: keeping the partner delivery engine running at the standard the business demands, and executing the platform and technical capability uplift that makes that engine faster and more reliable over time. The technical roadmap and major architecture calls are set jointly with the Head of Digital Enablement APAC; this role owns turning that roadmap into a working plan, and is accountable for the quality and pace of execution against it. The most significant near-term body of work is the rollout of the group’s policy administration and claims management platforms across APAC — this role leads the technical execution of that rollout, within the migration sequencing and priorities agreed with the Head of Digital Enablement APAC and the global platform team. This is a working technical leadership role, not a strategy-setting one: the expectation is day-to-day command of the platform layer, direct engagement with the four platform and architecture leads, and readiness to get into technical detail when the situation demands it. Key Accountabilities 1. Technical Execution Against the APAC Digital Roadmap ● Translate the technical roadmap (stack, architecture patterns, platform choices) agreed with the Head of Digital Enablement APAC into an executable plan ● Flag where sequencing, resourcing, or technical risk require a strategic decision — escalate rather than decide unilaterally ● Provide the technical detail that supports the Head of Digital Enablement APAC’s input into the monthly steerco cycle and quarterly capacity rebalancing 2. Policy Administration and Claims Platform Rollout — Technical Execution ● Lead the technical execution of the policy administration and claims management platform rollout across APAC, within the migration sequencing agreed with the stakeholders and the global platform technical team ● Identify and chase synergies — shared integrations, reusable configuration, avoided duplication across the partner portfolio ● Act as the day-to-day technical point of contact with the global platform technical team 3. Cross-Cutting Engineering Programmes ● Run engineering programmes that span all squads and partners — infrastructure upgrades, platform modernisation, security and compliance uplift, AI-assisted development tooling adoption ● Sequence these against delivery squad bandwidth, balancing platform investment against live partner commitments; escalate trade-offs that affect partner delivery commitments ● Ensure programmes have clear outcomes, owners, and timelines 4. Platform and Architecture Team Leadership ● Lead the four platform and architecture leads day-to-day ● Execute the platform agenda agreed with stakeholders: what gets built, what gets standardised, what gets retired ● Ensure architectural decisions are documented, reusable, and followed across delivery squads 5. Technical Standards and Engineering Quality ● Enforce APAC Digital’s technical standards — security posture, API design, deployment practices, production readiness ● Own the technical governance layer day-to-day: build and release compliance, CI/CD pipeline quality, alignment to enterprise production requirements ● Ensure delivery squads have the guardrails and tooling they need to build well at pace 6. Engineering Capability Development ● Identify capability gaps within the platform and architecture team and close them — through coaching, tooling, or training ● Drive adoption of AI-assisted development tooling across the engineering organisation ● Develop the platform leads’ day-to-day technical leadership skills Experience and Skills Essential ● Strong hands-on background in modern cloud-native engineering — Azure, C#/.NET, TypeScript, and CI/CD pipelines at production scale ● Experience leading platform or architecture teams —comfortable managing leads and equally comfortable in the technical detail ● Demonstrated experience executing platform modernisation in a brownfield environment: migrating live systems without breaking them ● Able to translate technical trade-offs into terms anon-technical stakeholder can act on ● Experience in financial services, insurance, or a regulated B2B digital environment (or comparable regulated context) Preferred ● Direct experience with policy administration systems, claims management systems, or comparable insurance distribution/digital platform products ● Familiarity with AI-assisted …