We’re looking for an SRE Platform Engineer to join our team, who will help build internal product and platform capabilities to unify Audiense’s overall experience. The team works with a strong product mindset, Extreme Programming practices (pairing, TDD), and a focus on long-term, systemic impact, even when results are not immediate. If you enjoy working collaboratively, and are open to learning, and bringing your own perspective and experience to the team, then maybe this post is for you! You should also feel comfortable operating a dual space that: Builds platforms and infrastructures with clear ownership and intent Designs solutions that other teams can realistically adopt Make technical decisions with systemic impact This is not a pure execution role, and not a detached infrastructure role either. It’s a role for someone who enjoys thinking about why something should exist as much as how to build it. The Team You'd be joining a well-established team, with around 10 years of active collaboration across product and engineering. The SRE Platform team exists to reduce the cognitive load of other engineering teams, so they can produce more value without needing deep knowledge of our cloud infrastructure, SOC2 inventory requirements, and base security. They do this by unifying the Audiense engineering experience through simplicity, consistency, and intelligent guidance. The SRE Team builds their own roadmap, while carrying cross-team responsibility. They treat what is built as internal product, designed for reuse. Some tools serve the team, but others that matter most are used by other engineering teams — real products, with real users. Most take the SRE team out of the loop of application changes (beyond deployments or testing), covering secrets, configs, rightsizing, and first provisioning, so others move with less friction and lower cognitive load. Their impact is not always immediately visible to end users, but when it works well, the entire platform moves faster, safer, and more coherently. They continue to evolve the platform for security, reliability, and cost-efficiency, balanced with close collaboration so what we build is adopted sustainably. The relationship with other teams is genuinely fluid and healthy: their constructive feedback regularly helps us improve our tools and surface new projects. How they work The team works with a strong product mindset , even when building internal platforms. Their day-to-day work is grounded in real agile practices, not just ceremonies: Extreme Programming as a reference framework Pair programming as a regular practice Test-Driven Development Incremental delivery and early feedback A constant focus on understanding why we build something, not just what These practices are not optional add-ons; they are a fundamental part of how they work. We’re looking for someone who is already comfortable in this kind of environment, or who is genuinely motivated to work this way. The team aims for an environment where it is safe to ask questions, to say “I don’t know yet”, and to learn in the open. We care more about how we work together and how we learn than about heroic individual performances. The Challenge Over the next phase, the team is focused on several strategic initiatives: Democratise deep cost analysis for other engineering teams — beyond AWS Cost Explorer. Embrace Kubernetes: level up the team on standards and migrate suitable ECS workloads. Improve KTLO management by automating the mechanical work, leaving only decisions and prioritisation to humans. This role lives in a constant, and healthy, tension between advancing the team’s own roadmap and ensuring that what we build truly enables the rest of the organisation. So far, one of the biggest challenges has not been purely technical. It has been finding the right balance between moving forward with their own product roadmap and ensuring that the tools and solutions we propose are adopted organically and sustainably by other teams. Each team has its own roadmap, priorities, technical constraints, and organisational realities, so changes are rolled out gradually and on purpose. As an SRE team, a well-paced adoption is what makes an entry safe and stable, and keeps it from feeling like an imposition — the exception being anything that touches the security or reliability of the system, where we move more firmly. To be fully transparent: today, a significant part of the team's non-maintenance work still comes from other teams' roadmaps, and maintenance takes a large share of their capacities. Building a clearer product roadmap of their own is an ongoing effort, and helping shape it is part of what this role can contribute — something we’re very open about. What you’ll do Design, build, and evolve the platform and infrastructure, helping shape the SRE Platform roadmap as it takes form. Build internal tools and automation, often with AI (Claude Code), to improve the developer experience across teams. Reduce the cognitive load of KTLO by automating manual, human-run steps so maintenance takes less and less of the team's time. Provide infrastructure support to developer teams, helping to ship faster, more safely, and more autonomously. Operate and improve containerised workloads on AWS ECS and Kubernetes (AWS EKS) in production. Manage and evolve cloud infrastructure as code (Terraform). Improve reliability, observability, performance, and cost-efficiency across the platform. Make technical decisions that balance local and global impact. Participate actively in architecture, design, and prioritisation discussions. Work closely with product, design, and engineering teams, delivering incrementally and learning continuously. Raise the bar through mentoring, feedback, and example. Help keep us SOC2-compliant: join the recurring ceremonies, keep monitoring on green, and ensure new platforms comply from day one. Are interested in joining our paid on-call rotation once you’ve built up enough experience with t