Identify and lead the adoption of new technology or architectural approaches that meaningfully improve our platform — owning multi-month initiatives end to end, from strategy through delivery.

Design and build resilient, easy-to-use foundational infrastructure that scales with a growing customer base.

Evolve the Internal Developer Platform, making it the primary way engineering teams interact with infrastructure — reducing the need for teams to come to Platform directly.

Take on scope and problems from engineering teams across the business, translating what they need into delivered outcomes.

Contribute to solution design early, helping prevent operational problems before they ship.

Facilitate discussions that bring the right people together to reach the right technical outcomes, across teams you don't manage.

Provide technical leadership to a small team, setting standards and coaching engineers across the organisation on platform and delivery practices.

Use quality and AI-assisted tools to produce effective code that's right the first time.

Strong proficiency in Go — this is our primary language for platform and infrastructure work (Kubernetes controllers, core routing systems), and you're expected to be productive in it from day one.

Deep, hands-on experience with Kubernetes — our platform runs on it, and it's the single most important technical skill for this role.

AWS as your predominant cloud platform. Experience with GCP or other clouds is a plus but not a substitute for strong AWS depth.

Working proficiency in Python and Terraform.

Strong familiarity with GitOps and CI/CD practices.

Linux and networking experience, including troubleshooting.

A track record of working across codebases and domains you didn't build — diagnosing issues, contributing improvements, and establishing patterns others can follow.

Experience with architecture and system design in SaaS environments operating at scale.

A demonstrated instinct for build vs. buy — knowing when to bring in a strategic partner or existing tool versus building in-house, so you can move on multiple fronts at once.

You bring in new ideas rather than just improving what's already there — you've changed the trajectory of a platform, not just iterated on it.

You lead through influence, not authority. You build consensus quickly and help teams make good decisions without creating bottlenecks.

You simplify complexity — whether explaining a cross-domain issue to leadership or replacing an ad-hoc pattern with something teams can rely on.

You multiply the people around you through coaching, pairing, code review, and tools/documentation that raise the bar for everyone.

You think about who your work helps — customers, teams, and the business — not just the system in isolation.

You're genuinely curious about problems: when something's described to you, you ask follow-up questions that reveal what's really going on, rather than taking it at face value.

You push yourself and others to do better, and you're comfortable operating with people across the business, not just engineering.

You use AI tools to move faster through implementation and problem-solving, while still being able to write and reason about production code yourself — AI accelerates your work, it doesn't replace your technical depth.

You apply the same build vs. buy thinking to AI: knowing when an AI-assisted or automated solution is the right tool for a problem.

You've owned and delivered a significant multi-month initiative — such as a new geographic region, a major platform migration, or a technology change that shifted how the platform operates.

Our Internal Developer Platform is genuinely adopted — engineering teams increasingly self-serve through it rather than coming to Platform directly.

Reliability and delivery patterns you've introduced are adopted as defaults across teams, reducing the effort required to build on our platform.

Platform Experience is seen as a partner that takes on scope and delivers, not a gatekeeper — teams actively want to work with you.

Engineering teams across groups — the primary consumers of the platform, working with you daily on infrastructure, tooling, and delivery.

Product managers & group leads — partnering on what teams and customers need from the platform.

Observability team — close partnership in a ready-to-use, well-instrumented environment.

Engineering and product leadership — providing foundational architecture that lets other teams build with minimal friction.