We're looking for someone who can't stop thinking about what AI makes possible and who'd rather spend a week building a tool that saves the team three hours a week than watching someone else do it.

This isn't a typical junior dev role. You'll work directly with our COO to find the friction points in how Creed operates, then build the tools and automations that eliminate them. You'll ship fast, learn faster, and leave your mark on how a fast-growing media company runs.

About Creed

Creed is the number one music marketing agency in the world. We didn't get there by playing it safe. We got there by understanding culture faster than anyone else, building campaigns that actually work, and being honest with clients when something won't. We operate across Music and Brands, we move fast, and we have the results to back up every word of this.

What you'll be doing

You'll spend your time somewhere between building new things and keeping existing things from breaking. Concretely:

You'll build internal tools, automations, workflows, and small applications that eliminate the manual, repetitive work that slows teams down. You'll own them once they're live: updates, fixes, documentation, the lot.

You'll be first in line when something breaks. Bugs from the team land with you. You figure out what happened, fix it, and make sure it doesn't happen again.

And you'll keep one eye on what's happening in AI. Not to stay informed in a general way, but because something useful drops every few weeks and we'd rather hear about it from you than stumble across it ourselves.

What we're looking for

The main thing is interest. Genuine, slightly-embarrassing-in-a-good-way interest in AI and what it can do, what it can't yet and where it's going. Experience matters less than the ability to pick things up fast and apply them.

Beyond that:

• You're comfortable across different AI tools and models. Not because you've memorised them, but because you understand enough about how they work that a new one doesn't throw you.

• You care about the problem more than the solution. Before you build anything, you want to know what's actually broken and why.

• You can explain technical work to non-technical people without being patronising about it.

• When something breaks, and things break, you stay calm, diagnose it, and fix it. You don't wait for someone to tell you what to do next.

We are looking forward to your application!