Hiring guide
How to Hire a Game Developer
Hire a game developer on evidence: engine fit, a playable prototype work sample, gameplay and performance criteria, red flags and onboarding.

The short answer
Hiring a Game Developer comes down to verifying deep fluency in your engine: c# and the unity component model, or c++ and blueprints in unreal engine, or your in-house engine, gameplay systems: character controllers, cameras, input, state machines and ai behaviour and profiling and optimisation on target platforms, including cpu and gpu frame budgets and memory before you commit interview time. The process below runs 5 stages, screens on evidence rather than résumé claims, and scores every candidate against the same criteria.
- Watch for: Portfolio is only videos and screenshots with no playable build
- Watch for: Cannot say which systems in a team project they wrote themselves
- Score on: How the mechanic feels to play and how easily a designer can tune it
- Score on: Clear separation of systems and readable engine code
Paste your Game Developer job description; Cohesyve finds, contacts and tests candidates on the real work and ranks them. 14-day free trial for 10 candidates, not charged until it ends.
Applying for a role like this? Practise the assessment free →Before you hire a game developer, be specific about the job: gameplay programmer, engine or tools programmer, technical artist, or a generalist who builds a whole small game. Each needs different evidence. Playable builds tell you far more than screenshots or trailers, so ask to play their work and ask exactly what they built in it.
Why this role matters
Games are judged by how they feel to play, and that feel comes from code: input response, camera behaviour, physics tuning and frame pacing. A developer who cannot profile or structure systems leaves you with a project that runs badly on target hardware and becomes harder to change late in production. A strong game developer works closely with designers and artists, builds tools that speed them up, and protects performance from the start.
Where to find candidates
- itch.io and game jam entries, including the Global Game Jam, where you can play finished small games and see who built them
- Games industry job boards such as Hitmarker and Work With Indies
- International Game Developers Association (IGDA) chapters and the Game Developers Conference (GDC) community
- Unity and Unreal Engine community forums, Discord servers and marketplaces, where developers publish tools and plugins
- Credits on shipped games similar to yours, then approaching the programmers directly
- Game development degree programmes and their end-of-year showcases for junior hires
Skills to look for
Red flags
- Portfolio is only videos and screenshots with no playable build
- Cannot say which systems in a team project they wrote themselves
- Has never profiled a build or talks about performance only in general terms
- Dismisses designer feedback on feel as subjective rather than something to tune
- Large single scripts with all game logic in one place and no separation of systems
- No experience finishing anything, only prototypes abandoned at the fun part
The interview process
- 1
Play their work
Play two or three of their builds before any interview. Note how controls feel, how the game performs and whether it is finished. Shortlist people whose games are complete and polished at their scale.
- 2
Technical conversation
Walk through one system they built: how it is structured, what they would change, and a bug that took them a long time. For engine roles, ask how they would find the cause of a frame-time spike.
- 3
Prototype work sample
Give a small project in your engine with a brief, such as adding a mechanic like a grappling hook or a dash with cooldown, with tunable values exposed for a designer. A job simulation of the real work is one option for this step. Judge feel, code structure, designer-facing parameters and whether it holds frame rate.
- 4
Designer and art collaboration
Have a designer give feedback on their prototype and ask for a change. See whether they ask good questions, make the change cleanly and explain any technical limits.
- 5
Team interview and references
Meet the lead programmer and producer. Ask references about crunch periods, shipping, and how they handled late changes from design.
Start the Game Developer interviews from a ranked shortlist
Cohesyve takes your Game Developer job description, finds and contacts candidates and tests each one on an AI job simulation of the job, so the stages above start with people who have already done the work. 14-day free trial for 10 candidates, not charged until it ends.
How to evaluate
- How the mechanic feels to play and how easily a designer can tune it
- Clear separation of systems and readable engine code
- Performance awareness on target hardware
- Evidence of finishing and shipping, even small projects
- Communication with non-programmers about constraints
- Sensible use of version control on binary-heavy projects
Onboarding
- 1Give them a build of the current game and time to play it before touching code
- 2Document your engine version, coding conventions and the project's folder and prefab structure
- 3Start with a contained task in one system, such as a bug in a known feature, before larger mechanics
- 4Introduce them to the designers and artists whose work their code will support
- 5Share your target hardware list and performance budgets from day one
Common questions
Should I hire for Unity or Unreal experience specifically?
Prefer experience in your engine for anyone who needs to be productive quickly, since project structure and tooling differ a lot. Strong programmers can switch, but expect ramp-up time.
Do engine certifications matter?
Credentials such as Unity Certified Professional: Programmer show structured knowledge of the engine, but a playable build and a work sample tell you more about how someone builds games.
How do I assess game feel fairly?
Use the same brief for every candidate, have the same designer play each result, and write down specific observations about input response, feedback and tuning rather than an overall impression.
Is a generalist or a specialist better for a small studio?
Small studios usually benefit from a generalist who can build gameplay, UI and tools. Specialists in rendering, networking or engine work pay off once the project has a clear need for that depth.
Hiring a Game Developer? Start with a ranked shortlist
Cohesyve takes your Game Developer job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then ranks them for you.
1,500+
assessments completed
50%
faster time-to-hire
5 min
from JD to assessment
14-day free trial · 10 candidates · Not charged until the trial ends
From the blog