How to write a game dev job post (template)

Updated November 6, 2026

The short answer: a good game dev job post says, in this order: what the game is (one line plus a screenshot or trailer), the exact role and what they'll make, the pay (paid with a budget, rev share with how the split works, or hobby), the timeline and hours, what to send (portfolio, rate, one relevant piece), and how to apply. Saying the pay up front is the biggest single thing that gets you better replies.

The same role can get five great replies or fifty bad ones depending on how it's written. Here's the order that works, a template to copy, and an example.

The template

Title: pay tag + role + game type + engine. Example: "[PAID] Composer for a horror game (Unity)".
The game: one line on what it is, plus a screenshot, GIF or trailer.
What they'll make: a real list with numbers: how many tracks, sprites, voice lines or systems.
Pay: paid with a budget or rate, rev share with the split and when it pays, or hobby. Say it plainly.
Timeline and hours: start date, deadline, and hours a week.
How you work: timezone, where you talk (Discord, email), and any must-haves like "human-made work only".
How to apply: what to send (portfolio, rate, one relevant piece) and where.

An example

[PAID] Pixel artist for a cozy farming game (Godot)

The game: Moss & Clover, a cozy farming sim about a frog running a tea shop. Trailer: [link]

What you'll make: 12 character sprites (32x32, 4-direction walk, 6 frames each) and one tileset to match our style guide.

Pay: $1,200 total, paid in two milestones (half after the first 4 sprites).

Timeline: about 6 weeks, part-time is fine. We're in UTC-5 and talk on Discord.

To apply: send your portfolio, your rate, and one piece closest to our style. Human-made work only.

For a rev share role

Say "rev share" in the title, then explain the split (gross or net, what %), when it pays out, and that it's in writing before work starts. Show what already exists, like a playable build or a trailer, because that's what convinces people to work for a share. The rev share agreement checklist has what to agree.

Mistakes that cost you applicants

No pay info, or "pay discussed later".
No numbers for the work, so nobody can quote.
A wall of lore before the role.
No picture of the game.
Asking for big free test tasks. Keep tests small, or pay for them.

Not sure what to budget? The price guides have sourced ranges for music, art, voice, programmers, trailers and more. And when it's written, here's where to post a game dev job.

Frequently asked questions

How do I write a game dev job post?

A good game dev job post says, in this order: what the game is (one line plus a screenshot or trailer), the exact role and what they'll make, the pay (paid with a budget, rev share with how the split works, or hobby), the timeline and hours, what to send (portfolio, rate, one relevant piece), and how to apply. Saying the pay up front is the biggest single thing that gets you better replies.

What should I put in a game job post title?

The pay tag, the role, the game type and the engine, for example "[PAID] Composer for a horror game (Unity)". People scan titles, so the pay and role should be readable at a glance.

Should I put the budget in a job post?

Yes. Posts that state the pay get more relevant replies and save everyone time. If you're unsure what to budget, check sourced price ranges first.

How do I write a rev share job post?

Say rev share in the title, explain the split and when it pays, show what already exists (a build or trailer), and promise a written agreement before work starts.

Where should I post it?

For indie roles: IndieGuild (free, no cut, people who fit get it in their inbox), r/gameDevClassifieds for paid gigs and r/INAT for rev share, Work With Indies for studio roles, and Discord hiring channels.

Post it on IndieGuild, free

The post form walks you through these same fields in about a minute, and creators who fit get it in their inbox. No cut taken.

Post a role