A narrative designer resume that just says "responsible for story" gets filtered out. When studios screen narrative designers, they look for one thing: can you write story that serves the gameplay and lands for the player. A resume that wins interviews leads with writing samples and speaks in narrative-meets-systems results. Here is how to write it.
In one line: your resume should answer "what did you write, did it serve the gameplay, and did it land for players."
A narrative resume without samples is an incomplete application:
Show, don't just describe — samples are the narrative designer's strongest evidence.
Use concrete outcomes and quantify them:
Things you can quantify: quests / words / dialogue, branching / choices, integration with systems, shipped titles. For methods, see how to quantify resume achievements.
Group your narrative skills so a reviewer can scan them:
For structure, see how to list skills on a resume.
These roles collaborate closely but differ, so make your focus clear:
If you do both, say so, but lead with the narrative and integration depth. Related role: how to write a level designer resume. Related role: character artist. Tailor to the target with how to tailor your resume to a job description.
Writing samples first, then narrative craft, gameplay integration, and delivery. Link to quests, dialogue, or scripts at the top, pick work relevant to the target, and show how your narrative served systems and player choice — proving it lands in-game, not just "responsible for story."
Game writing focuses on the prose — dialogue, lore, scripts; narrative design also owns how that story is delivered through quests, systems, branching, and player choice. Many roles blend both, but a narrative design resume should emphasize integration of story with gameplay, not only the writing.
A narrative designer owns the story in the game — quests, dialogue, branching, narrative-systems integration; a game designer owns systems and mechanics — rules, balance, gameplay. They collaborate closely, but position your resume by your direction and show matching samples.
Pick samples that show both craft and gameplay integration — a branching dialogue, a quest with player choice, environmental storytelling — matched to the studio's genre and tone. Quality and fit beat volume; a few strong, on-target pieces are better than a large unfocused folder.
The core of a narrative designer resume is proving you can write story that serves the gameplay and lands for the player. Lead with writing samples, tie narrative to systems and choice, and aim it at the studio's titles. When you're done, run it through Prism Resume's free check: prismresume.com/check.
Wondering how your own resume holds up?
Check it free — no sign-upAn environment artist resume that just says "responsible for environments" gets filtered out. Recruiters lead with your portfolio and want style match and performance. This guide shows what to prove, how to show a portfolio, how to write your skills section, and how an environment artist resume differs from a level designer's, with an FAQ. Run a free check at the end.
A character artist resume that just says "responsible for characters" gets filtered out. Recruiters lead with your portfolio and want style match and a clean pipeline. This guide shows what to prove, how to show a portfolio, how to write your skills section, and how a character artist resume differs from an environment artist's, with an FAQ. Run a free check at the end.
A game animator resume that just says "responsible for animation" gets filtered out. Recruiters lead with your demo reel and want game-feel and engine integration. This guide shows what to prove, how to show a reel, how to write your skills section, and how a game animator resume differs from a character artist's, with an FAQ. Run a free check at the end.
Loading…