How to Write a Narrative Designer Resume (2026 Guide With Examples)

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.

What a narrative designer must prove

Writing samples: a link to quests, dialogue, or scripts — the single most important part.
Narrative craft: story, characters, world-building, branching, dialogue.
Narrative-gameplay integration: weaving story into quests, systems, and player choice.
Delivery: scripting tools, collaboration with design/level/VO, iteration.

In one line: your resume should answer "what did you write, did it serve the gameplay, and did it land for players."

Lead with writing samples

A narrative resume without samples is an incomplete application:

Link to samples at the top (portfolio, quest/dialogue excerpts, scripts) — recruiters will read them.
Pick work relevant to the target: RPG quests, branching dialogue, environmental storytelling.
Show range and fit: voice, branching, and integration with gameplay, not just prose.

Show, don't just describe — samples are the narrative designer's strongest evidence.

Don't just list duties, show integration and impact

Use concrete outcomes and quantify them:

❌ "Responsible for story" — shows nothing.
✅ "Designed quests and branching dialogue for an RPG — wove narrative into systems and player choice, wrote and scripted the lines in the engine's tools, and iterated on playtest feedback, shipped at launch" — craft, integration, and delivery.

Things you can quantify: quests / words / dialogue, branching / choices, integration with systems, shipped titles. For methods, see how to quantify resume achievements.

How to write the skills section

Group your narrative skills so a reviewer can scan them:

Narrative craft: story, characters, world-building, branching, dialogue, voice
Integration: quest design, systems-driven narrative, player choice, pacing
Tools: narrative/scripting tools (Twine, ink, Yarn, engine dialogue systems)
Collaboration: design, level, VO, localization, iteration
Writing: scripts, barks, lore, documentation

For structure, see how to list skills on a resume.

Narrative designer vs game designer

These roles collaborate closely but differ, so make your focus clear:

Narrative designer: owns the story in the game — quests, dialogue, branching, and narrative-systems integration.
Game designer: see how to write a game designer resume, owns the systems and mechanics — rules, balance, and gameplay, not the story.

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.

Common mistakes

No writing samples: the most fatal flaw for a narrative resume.
Prose with no gameplay integration: narrative design is story that serves systems, not a novel.
Duties with no work: writing is shown, not told.
No branching or choice: for interactive titles, player choice is the craft — surface it.
Samples off the target genre or tone: work not aimed at the studio's titles.

Frequently Asked Questions

What should a narrative designer resume highlight?

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."

How is narrative design different from game writing?

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.

How is a narrative designer resume different from a game designer's?

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.

What writing samples should I include?

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.