Platform Technical Lead (OpenShift)

Job Description

The Platform Technical Lead is the technical owner of the platform product. Reporting directly into the Head Of System Engineering (HoSE) and whilst specific responsibilities will be dependent upon the changing needs of the Tesco business, the following provides an overview of the role’s key responsibilities and measures They own how the platform is designed, built, operated and evolved, and are accountable for its technical integrity in production. They partner with the Platform Product Lead, who owns product direction and stakeholder outcomes; the Platform Technical Lead owns the engineering that delivers them. Technical authority and design Act as design authority for the platform: own the technical roadmap, author and ratify Architecture Decision Records, run design review, and hold the line on standards. Decisions are documented, evidenced and reversible-by-design where possible. Own the target architecture for the platform across its full stack: OpenShift (HCP / Virtualization), GitOps delivery (Argo CD), multi-cluster management and policy (ACM, Gatekeeper/OPA), observability, networking and storage integration, and infrastructure-as-code. Set and enforce the paved-road patterns the team builds to. Evaluate new technologies against product outcomes, not novelty: run structured spikes with defined success criteria, and make adopt/hold/reject calls with written rationale. Platform as a Product. Treat the consuming product teams as customers. Own the platform's service interface to those products: API and interface contracts, versioning and deprecation discipline, capacity and performance guarantees, and the documentation that lets product teams consume the platform without needing to understand its internals. Measure the experience (integration lead time, breaking-change incidents, ticket deflection) and improve it deliberately. Understand how infrastructure product teams expose the platform to application engineering teams, and factor that end-to-end developer experience into platform design decisions - the platform is only as good as what the products can build on it. Own the technical content of the platform product roadmap jointly with the Platform Lead: they prioritise the what, the Platform Technical Lead defines the how, effort, sequencing and technical risk. Eliminate toil systematically: everything operated more than twice is a candidate for automation; anything manual in the production path is a defect on the backlog. Develop and maintain DevOps practices within the Platform Team. The team owns and supports what they build. Production ownership Accountable for the platform's operational integrity: SLOs, error budgets, capacity and performance. Lead technical response on novel or high-severity incidents, own the post-incident review, and convert findings into engineering change, not just runbook entries. Ensure everything the team ships is production-grade: designed, documented, tested, observable and handoff-ready, with no single person as the sole holder of any critical capability. People and capability Own the technical development of engineers to validate skill assessments against production evidence, set stretch assignments against capability gaps, and coach seniors towards design ownership. Represent the platform with authority in cross-team and architecture forums; translate architectural strategy into designs that can actually deliver, and push back with evidence where strategy and practicality conflict. Skills / Experience Required Proven technical leadership of a platform or product engineering team: sets direction, owns design decisions, and is accountable for what ships to production. Acts as design authority: authors and maintains high-quality design records (ADRs or equivalent), runs design review, and holds standards without becoming a bottleneck. Treats the platform as a product: understands consuming teams as customers, designs and versions interfaces deliberately, and measures the consumption experience rather than assuming it. Structured, analytical approach to complex troubleshooting: forms hypotheses, isolates variables, resolves incidents not previously seen, and converts findings into engineering change. Communicates technical design and risk with authority to mixed audiences, from engineers to senior non-technical stakeholders, and can defend or revise a position based on evidence. Translates Tesco Technology and business strategy into a credible technical roadmap: sequencing, effort and risk, not just ambition. Coaches and develops engineers with evidence: validates skill assessments against production work, sets stretch assignments against capability gaps, and builds succession so no critical capability rests on one person. Works product-first within agile delivery: outcomes over outputs, incremental delivery, honest reporting of technical risk. Systematically eliminates toil: treats anything manual in the production path as a defect and automates as a default b