Senior Software Engineer - Developer Experience

As a Senior Software Engineer, you will play a crucial role on the Blueprint - one of our developer platform teams. Your role will be to help make the platform the natural way to build and ship software here, one engineers choose to use.

Blueprint builds the golden path that lets engineers ship services quickly and safely: service templates, a software catalogue and developer portal, build pipelines, code quality gates, API discovery and more. As AI means each engineer now runs more services than before, this platform is how Epidemic Sound keeps ownership, quality and cost visible, and you will help build the infrastructure and tooling that let AI coding agents build services correctly by default. You will work closely with our other platform and infrastructure teams, and directly with engineers across the business whose needs we serve.

Your key responsibilities include

• Design, build and maintain the golden path: service templates, scaffolding, code quality gates and upgrade paths.
• Build the software catalogue and developer portal, so engineers can see what they own, how far it sits from the standard, and how to close the gap.
• Shape the context and tooling that let coding agents build services correctly by default.
• Design and build the solutions that address what product teams need.
• Partner with other platform and infrastructure teams on shared build pipelines, routing and web tooling.
• Participate in setting the technical direction for the developer experience domains and mentor more junior engineers on the team.

Requirements

Several years of experience building internal developer platforms, tooling or infrastructure, with other engineers adopting what you built.

It would also be music to our ears if you have

• Strong backend engineering in Go or a comparable language.
• Hands-on experience with Kubernetes, Helm and CI/CD pipelines in a cloud environment; we run on GCP with GitHub Actions.
• Practical experience with AI-assisted or agentic coding workflows, and a view on how to make them safe by default.
• Experience in working as a product team, including interacting with engineering teams as clients, using bets as organising principle, and experiments as tools for validating hypotheses and assumptions.
• The ability to say no when it’s the right call.