How do you find indie game developers to work with?

The first wall I hit was not a developer saying no. It was Reddit telling me I did not have enough karma to post. I had set out to land my first indie composer job in under five hours, on camera, to prove to my students that getting hired is not luck. Reddit did not care about my deadline.

So I asked an AI how karma works, dropped six or seven jokes on an Ask Reddit thread, and twenty minutes later I could post in the classifieds where developers actually read. Three hours after my first message, I was talking with the lead developer of an indie game. Fifteen minutes of conversation later, I had the job.

The whole run took forty actions. Most were small and unglamorous: karma jokes, posts read, two replies in the classifieds, one direct pitch, one server joined, one demo played, a stack of short messages.

Here is the part nobody wants to hear.

You do not have a finding problem. So how do you find indie game developers to work with? You stop treating it as a search and start treating it as three smaller questions: where do they post, what can you show them, and what will you offer? Answer those three and finding a developer takes an afternoon. Skip them and you can send a hundred messages into the void.

The rooms developers post in every day

Developers looking for teammates are not hiding. They post in public rooms daily. Start with the r/INAT classifieds on Reddit. The name is short for I Need A Team: developers post what they are building and who they need, and the community runs a Discord where those same developers hang out.

Second room: game jams on itch.io. Jam teams assemble in a day and ship in a weekend. Post one loop that fits the theme the day a jam opens, and you are ahead of every composer waiting for a job post. Third: engine communities, like the Godot community and the Unreal Slackers Discord, where developers show builds long before any job post exists.

Notice what is not on the list: composer job boards. By the time a post says composer wanted, you are bidding against a crowd offering to work for free. Go where the games are being built, not where the composers are lining up.

The five-hour run, move by move

Move one: I went to the classifieds and answered two posts. Then I pitched one developer directly about their game. While Reddit made me earn posting rights, I did not wait. I found that developer’s Discord and joined. Two roads toward the same yes.

Move two: I played their demo before saying one word about music. Not the trailer. The playable build.

Move three, the opener. Lightly cleaned up, my first message was: “Played the demo. Super fun. Cool if I send over a rough demo track inspired by the gameplay in a bit?” No rate card. No budget questions. The only thing I asked permission for was to give them something.

The developer had a community vote system for picking artists. I did not fight it. I told them I respected the process, then added: “Here’s a wild thought. Would you be open to me creating just one track outside the vote process, where I document the full behind-the-scenes process on my YouTube channel? It wouldn’t cost you anything.”

I promised to treat it exactly like hired work. My payment was getting to tell their story to my audience, 114,000 subscribers who already love video game music. And I closed with one line that matters more than the rest: “Obviously, you’ll have total creative control and I’ll be here to serve your vision.”

The answer came back: “Yes, dude. Absolutely yes.”

The game was Minimalist Rally 2D. The developer goes by Z. The first sound Z ever heard from me was a rough track pointed at his own build. It shipped on the OST, and a second track followed. Repeat work is the quiet half of this business.

Now the honest part. You cannot make my exact offer. Neither could I, before the channel and the books existed. So build the offer you can make today, and become the person who can send a bigger one next year.

Why your message gets ignored

A developer is buying one outcome: music that fits their game, delivered on time, with zero drama. Your message saying you are passionate is a sentence every other applicant can paste. What raises their belief that you will actually deliver is proof they can click and hear in thirty seconds.

Working for free does not fix a proof problem. Unpaid with no proof still costs the developer time, risk, and headache. Fix the proof first.

The three-track reel that does the talking

You do not need a twenty-track cinematic opus. You need three finished pieces. One thematic track with a melody someone could hum back to you. One combat track that never sits still. One ambient track that stays out of the way of gameplay and still feels alive. Every track ends clean or loops seamlessly, and all three sound like they come from the same universe.

Steal structure, not notes. Map two real themes and notice they disagree: Tom Salta’s Battlegrounds main theme withholds its melody, riding drums and pulse before the theme lands, while Jeremy Soule’s Dragonborn theme states its melody in the opening seconds, choir first. Write down where every instrument type enters in each. Then draw your own map and fill it with your own music.

The thirty-day version: week one, pick the one game genre you want to be hired for and choose two or three reference tracks per piece. Week two, rough drafts, 45 to 90 minutes a day, melody all the way through before anything else. Week three, refine and mix one track every two to three days, to about -16 LUFS integrated: loud enough to compare against references, with headroom left for the game’s own mix. Week four, bounce, upload unlisted, and title each one like a job application: Roguelike, hire me.

Read the developer before you commit

I learned this one the expensive way. Early on, a developer gave me feedback like “it needs to feel more like a battle.” I asked for timestamps. I got “from two minutes to three minutes, it needs to feel more like a battle.” I sent revision after revision. Twenty-five rounds on one piece, and it still was not approved.

That failure became my intake filter. Before you commit to any project, check three switches: do they know what they want, can they explain it, and are they flexible? A developer with all three is a dream. Two, still great. One, proceed with structure. Zero, walk away.

The structure that protects you: no composing until they hand you reference tracks with timestamps for what they love. Then run direction checks: send rough work early and ask “is this headed in the right direction?” Never “is this done?” A developer who cannot pick three reference tracks usually cannot finish a game either.

Charge something real by the second gig

I took my first job unpaid on purpose. It guaranteed the yes, and I was buying a credit and a story, not a paycheck. Free as a one-time choice is a tool. Free as a lifestyle is a trap, because business is a separate skill tree and it only levels up when money changes hands.

The first dollar forces skills no tutorial teaches: saying a price out loud without apologizing, negotiating scope, hitting a deadline another human is waiting on, taking harsh feedback without melting down, and putting a deal in writing. Five years of practice with zero dollars is one year of business experience repeated five times.

A starter offer that works: a $2 non-exclusive music pack. The developer gets solid tracks for their game, you keep the rights and can sell the same pack again tomorrow. Put even that in a one-page agreement, or a written DM: what they get, what they pay, what rights stay yours.

Proof it is not just me

The same door stays open for composers who are not me. I put three members of the Gamer Music Creator Guild at Best Music Coach onto a real game: Symbiote, a high-speed 3D action platformer by the studio Trickster. Fourteen days to deliver, on top of their day jobs, composing with the 4M Video Game Music Composition Protocol they train with.

Lead developer Alex Donahue judged blind. To test fit, he muted his own game and played it with each track looping. The winner, “Fury” by Alex Nunes, took guaranteed placement in the game plus a shot at lead composer for the whole project. The studio put up $250 in prizes. Second place went to a composer submitting his third finished piece ever.

Third finished piece. Real game. Real developer. More names, released tracks, and streaming links sit on the results page.

In Dan’s own words

“How can I make this work for you right now? How can I solve your problem right now asking nothing in return?”

– Dan Spencer, Video Game Music Composer

“No reel equals no proof. No proof equals no belief you can deliver, and no belief equals no money.”

– Dan Spencer, Video Game Music Composer

“The people who are easy to get along with, they show up on time, they’re zero drama, they deliver on time, they ask a lot of questions, they get clear, they’re about service, they’re about contribution, they’re about showing up for the team, and they bring no ego to the table.”

– Dan Spencer, Video Game Music Composer

Start this week

Tonight: open the I Need A Team classifieds, sort by new, and read ten posts. You are not hunting the words composer wanted. You are hunting a playable build you can download. Grab two. Join one engine community while you are at it.

This week: play both builds. Send each developer one message that names one specific moment you loved and offers a rough track inspired by it, free, no strings. Then deliver like you were hired: on time, zero drama, their vision first.

In parallel, start the thirty-day reel. Week one is a single afternoon of decisions. And when a yes lands, run the checklist: reference tracks before composing, direction checks over guesswork, a one-page agreement, your rights kept.

The developer who says yes is not hiring the most talented composer in the thread. They are hiring the person who played their game, named one true thing about it, and made the next step easy. Forty actions bought me a shipped credit in five hours. Your forty are sitting in this week, waiting.

Frequently Asked Questions

Where do indie game developers post when they need music?

In public rooms, daily: the I Need A Team classifieds on Reddit (r/INAT) and its Discord, game jams on itch.io, and engine communities like the Godot forums and Unreal Slackers. Read new posts, download playable builds, and message the developer directly instead of waiting for a composer-wanted post.

Should you compose for free to get your first game credit?

Dan took his first job unpaid on purpose: it guaranteed the yes and bought a credit and a story. Free works once, as a deliberate choice with a written scope. Free with no reel still reads as risk to a developer. By the second gig, charge something real, even $2, and keep your rights.

How many finished tracks do you need before messaging developers?

Three: one thematic piece with a hummable melody, one combat track with relentless energy, and one ambient track that stays out of gameplay’s way. Each loops or ends clean, all three share one sonic universe, and one click plays them.

What do you say in the first message to a developer?

The shape that landed Dan’s first credit: play the build first, then send something like ‘Played the demo. Super fun. Cool if I send over a rough track inspired by the gameplay?’ Name one specific moment, offer the first track free, ask for nothing, and promise their vision stays in charge.