The key to a great game designer job description is focusing on the specific project phase and game genre, not just listing generic skills. A vague description will attract hobbyists, while a precise one filters for the exact talent you need for your pipeline.
From my experience leading teams, the most effective descriptions start with a clear project context. For example, is this for a live-service mobile game, a single-player console RPG, or a VR prototype? The tools, workflows, and daily responsibilities differ drastically. I always include the engine and version (e.g., Unreal Engine 5.3, Unity 2022 LTS) and the target platform (PC, console, mobile). This immediately signals to senior candidates that you know what you are doing.
I also avoid the trap of listing "must have 5+ years of AAA experience" as the first requirement. Instead, I prioritize the core competencies of the role. A systems designer needs data analysis and balancing skills, while a narrative designer needs writing samples and branching dialogue experience. The best way to structure this is to separate "Required" from "Nice to Have" clearly. Here is a comparison of common mistakes vs. best practices:
| Common Pitfall | Best Practice |
|---|
| "Must be passionate about games" | "Must have shipped at least one title on Steam or console" |
| "Proficient in game design" | "Proficient in scripting with Blueprints or Lua for prototyping" |
| "Excellent communication skills" | "Experience writing design documentation for a team of 10+ engineers" |
Finally, I always include a practical test or portfolio requirement in the description. Asking for a specific design document or a playable prototype in the cover letter is the best way to filter candidates who can actually do the work. This reduces the time spent on the candidate screening process and ensures the salary range discussion happens with qualified individuals only.
