
To hire a game developer for a startup in 2026, first decide whether you actually need one. Most founders saying "game developer" are building interactive content (Three.js demos, WebGL marketing experiences, mobile creator tools) where a strong full-stack web engineer ships faster. If you really are shipping a Unity, Unreal, or Godot title, expect $40 to $100 per hour freelance, $85k to $175k full-time, and a 4 to 14 week sourcing window depending on platform and shipped-title evidence.
This is the first cut, and it saves more money than any rate negotiation. We see roughly three founders show up looking for a "game developer":
Only the first group needs a real game developer. The second and third groups are better served by a full-stack TypeScript engineer who knows Three.js or React Three Fiber, plus Stripe and Supabase. Those engineers cost half as much, ship four times faster, and don't need a 6-month asset pipeline.
If you're in groups 2 or 3, stop reading hiring guides for Unity devs. Read our full-stack hiring guide instead.
If you're in group 1, the bar is specific and not negotiable.
Unity and Unreal are the two real options, with Godot growing fast for indie 2D. The job description should name the engine, the rendering pipeline (URP vs HDRP for Unity, Lumen/Nanite for Unreal 5), and the target platform. "Unity developer" is too broad. "Unity URP mobile dev with shipped App Store title" is the actual shape of the role.
Ask for a public link to a shipped title. Steam, App Store, Google Play, itch.io, Epic Games Store. If they only have GitHub repos and game-jam entries, they're a hobbyist. Hobbyists can be great hires; they just cost less and need more direction.
The skills that matter depend on what you're shipping:
Game development hasn't escaped the AI-native shift, and the engine vendors built the tooling in. Unity's Muse, Unreal's animation and asset assistants, Cursor and Claude Code for editor scripting and gameplay code, Copilot inside Rider. A 2026 Unity dev who isn't using Cursor or Claude for editor extensions, asset processing scripts, and gameplay scaffolding is leaving four hours a day on the table.
Ask: "Walk me through your last shader or gameplay system. What did you write yourself, what did Claude or Cursor draft, and how did you verify the output?" The honest answer is detailed; the cargo-culted answer is generic.
Ranked by signal-to-noise for actual startup founders, not AAA studio recruiters.
The interview structure that works:
Open the candidate's shipped title together. Ask them to walk you through one specific feature they owned. The good ones get specific fast: "I rewrote the save system from JSON to MessagePack, cut load time by 600ms, here's the commit." The mediocre ones stay abstract.
No whiteboard. Have them open their actual editor (Rider, Visual Studio, VS Code), with their actual AI tooling (Cursor, Claude Code, Copilot), and prototype something small. A Unity scene with a moving cube and a working input system. An Unreal blueprint that responds to a UE event. A Three.js scene with a custom shader. 45 minutes is enough.
What you're watching for: do they reach for Claude or Cursor immediately, or do they treat AI as a nice-to-have? Do they verify the AI output, or do they paste and pray? AI-native engineers in 2026 are obvious within 10 minutes of watching them work.
Reference checks usually ask "would you hire them again." That's polite-checkbox territory. Ask instead: "What did they ship, what shipped late, and what was the failure mode when they got stuck?" The answers tell you whether the person actually ships under pressure.
Real day rates we see across the market, freelance and contract. Game-dev rates are typically lower than equivalent SaaS engineering rates, partly because the talent supply is wider and partly because game studios train developers to lower rate expectations.
| Engagement | Profile | 2026 rate |
|---|---|---|
| Junior Unity / Unreal contractor | 0 to 2 yrs, no shipped title | $20 to $35 / hr |
| Mid-level Unity / Unreal | shipped 1+ title, owns features | $50 to $80 / hr |
| Senior with AAA shipped credit | 5+ yrs, shipped console or top-grossing mobile | $90 to $150 / hr |
| Three.js / WebGL specialist | strong web + GLSL | $60 to $120 / hr |
| Multiplayer netcode specialist | shipped real-time multiplayer | $120 to $200 / hr |
| Full-time mobile Unity (US) | mid to senior | $85k to $145k / yr |
| Full-time PC/console (US) | senior | $125k to $175k / yr |
Cadence's weekly tiers anchor against the same market. We pay engineers a flat weekly rate and bill founders weekly:
| Tier | Weekly rate | Fits |
|---|---|---|
| Junior | $500 | Cleanup, asset processing scripts, Unity editor extensions, integration of well-documented SDKs |
| Mid | $1,000 | End-to-end feature work in Unity URP / Three.js / R3F, standard gameplay systems, Stripe + IAP plumbing |
| Senior | $1,500 | Owns a feature area unprompted, complex shader work, performance tuning, multiplayer architecture for small lobbies |
| Lead | $2,000 | Architecture for a multi-team title, fractional CTO for game-tech startups, complex netcode, anti-cheat |
For most founders building interactive content (group 2) or creator tools (group 3), Cadence Mid or Senior covers the work at $1,000 to $1,500 per week, billed weekly, with no notice period. That's roughly $5k to $7.5k per month versus $9k to $14k per month for an equivalent freelance Unity dev at $60 to $100 per hour, 25 hours a week. Worth comparing for your scope. Our hiring guide for full-stack engineers explains the full-stack profile in more detail; if you genuinely need shipped-AAA Unity console work, a specialist boutique is still the right fit.
If your scope is "ship a 3-week WebGL marketing experience" or "prototype a creator-economy MVP in 6 weeks," recruiting full-time is the wrong tool. Recruiting takes 6 to 14 weeks just to source. The work is over before the offer letter is signed.
For sub-12-week scopes, booking wins. How to hire a developer for an MVP fast covers the full booking-vs-hiring decision in detail. The short version: book for 2 to 12 week scopes when the role is unvalidated; recruit full-time when you've validated the role and need 6+ months. Both are valid; the mistake is using one model for the other shape of work.
If you're hiring for a long-term studio build (year-plus runway, full-time team of 4+), recruit traditional. If you're testing a hypothesis, book.
Try Cadence: if your "game" is closer to interactive content (Three.js, WebGL, R3F, mobile creator tools), book a Mid or Senior engineer and start the 48-hour free trial. If you decide it isn't a fit, you don't pay. For real Unity AAA console work, talk to Toptal Games or a specialist boutique instead. We won't be offended.
Through traditional recruiting, 4 to 14 weeks depending on platform specialization (mobile is faster, PC/console with shipped AAA credit is slower). Through specialist freelance platforms like Toptal Games, 2 to 3 weeks. Through a booking marketplace like Cadence, hours for web/interactive content, days for Unity mid-tier.
$50 to $80 per hour for a mid-level developer with a shipped title, $90 to $150 for senior with AAA credit. Eastern Europe and LATAM rates run 30 to 50 percent lower for equivalent skill. Rates under $30 per hour usually mean unshipped portfolios.
If your idea runs in a browser without a download, a Three.js or React Three Fiber engineer is faster and cheaper than a Unity dev exporting to WebGL. If your idea needs an App Store install, native performance, or controller input, you need Unity (or Unreal). The "browser playable" question is the cleanest cut.
Full-time when you've validated the product and need 6+ months of work. Contract or booked when you're testing, prototyping, or shipping a defined scope under 12 weeks. Most pre-PMF game-tech startups are in the second bucket and over-hire too early.
Ask for a link to a shipped title. Play it for 10 minutes. Ask the candidate which specific systems they owned and how they'd improve them now. Their level of specificity will tell you more than any technical interview. For deeper screening, Cadence's voice-interview vetting handles the technical bar so you don't have to.