About the role
Responsibilities:
- Build a high-performing software engineering organization with end-to-end accountability for design, build, quality, release, and production operability across digital, core-adjacent, and enterprise technology.
- Own full-stack engineering: frontend, backend, mobile/web, microservices, and core/enterprise engineering.
- Own API, services, integration, and event platform engineering as reusable enterprise capabilities.
- Own quality engineering, automated testing, performance/resilience testing, and engineering quality standards.
- Own developer platform, CI/CD, and DevSecOps engineering in partnership with security and infrastructure.
- Own Release and Engineering Operations, progressively moving from central release coordination toward continuous/progressive delivery.
- Own Technology Service and Application Support: L2 application support, major incident/problem management, and engineering service experience; L3 stays with owning PODs.
- Build captive engineering depth while using partners selectively; establish engineering career paths, communities of practice, and productivity tooling, including AI-assisted engineering.
- Own technical delivery commitments within product PODs and production health of engineered products.
Key interfaces/boundaries:
- Business Technology/Product decides WHAT/WHY and owns business prioritization; Engineering owns HOW and engineering quality.
- Infrastructure owns foundational cloud/network/workplace/SRE platforms; engineering owns application operability and code-level production issues.
- Architecture sets enterprise guardrails; engineering selects implementation patterns within those guardrails.
- Strategic Missions borrow engineering capacity through agreed prioritization; they do not create a parallel engineering team.
Outcome Illustrative Measures:
- Flow and speed: Deployment frequency, lead time for change, release predictability, and developer cycle time.
- Quality: change failure rate, escaped defects, automated test coverage, performance/resilience defects.
- Reliability: application availability, MTTR, repeat incidents, and production defect aging.
- Platform leverage: API/service reuse, developer-platform adoption, and self-service environment/deployment %.
- Engineering health: Technical debt trend, code health, vulnerability remediation, and engineering productivity.
- Support experience: incident volume, FCR, MTTR, repeat-incident reduction, self-service %, and seller/ops downtime.
Requirements:
- Experience: Typically 20+ years in software/product engineering with significant scale leadership; modern cloud-native, API/microservices, DevSecOps, and platform engineering depth; preferably insurance/BFSI experience and demonstrated build+run ownership.
- Leadership attributes: Builder mindset, technically credible, high standards without bureaucracy, strong talent magnet, data-driven engineering leader, calm under production pressure.