PeopleOperations&TechnologyArchitect

## The Role 👋 This role is the engine of that build. Work is already underway — systems are being rationalised, workflows are being automated, and the data layer is taking shape. You are joining at a pivotal moment: enough has been built to move fast, and enough is still to be done that the decisions you make will define what this function becomes. ## What you’ll own 💼 This role has four distinct areas. Each has a different mode — some are direct ownership and build, some are co-ownership and continuous improvement, some are working alongside peers to raise the technical bar. The common thread is that you are building an intelligent function, not running an operational one. People Services — Know it well enough to make it smarter The day-to-day operation of People Services sits with the team. You are not an additional pair of hands in that layer. What we need is someone who understands these workflows deeply enough to redesign, automate, and globally align them — and who stays close enough to the systems to spot patterns, failures, and improvement opportunities before they become problems. The query management system — implement it and ensure it keeps evolving. This means SLA governance, ticket tiering and routing logic, escalation workflows, employee feedback loops, and dashboards. Day-to-day queries are handled by the team; you help ensure the system runs smoothly underneath them and continuously improves Map and understand the end-to-end employee lifecycle — offer acceptance through onboarding, role changes, performance cycles, and offboarding — as the substrate on which every system and workflow is built Identify inefficiencies, duplication, and manual steps across People Services workflows; design and implement improvements in partnership with the team Align People Services processes globally where possible — there is variation across geographies today; find the right level of standardisation and build the systems that make it stick Bring structure and consis