Applying to Game Dev Internships: Projects Inspired by Tim Cain’s Quest Types

Still struggling to get a game dev internship because your portfolio feels thin or unfocused?

Hiring managers in 2026 are flooded with resumes. They look for concise proof that you understand systems, scope work responsibly, and can ship playable content that teaches them something about your role fit. That’s why short, sharp mini-projects — each demonstrating one design skill — beat giant, unfocused prototypes. This guide gives you portfolio-ready prompts inspired by Tim Cain’s quest types so you can build targeted projects for game dev internships, student showcases, and game jam entries.

The value of Cain’s quest taxonomy in 2026

Tim Cain’s breakdown of nine quest types is a practical shorthand for thinking about game systems: each quest type foregrounds a different design problem (narrative, economy, navigation, morality, puzzles). In 2026, studios want interns who can ship a clear iteration: a polished fetch quest that teaches AI-scripting, a moral dilemma that shows narrative branching, or a tight puzzle sequence that proves level design chops.

"More of one thing means less of another." — Tim Cain

That warning is especially relevant now: modern tools (AI-assisted level design, procedural content pipelines) let you iterate fast, but scope control remains the decisive skill. Each mini-project below is scoped for 1–4 weeks and designed to be demonstrable to hiring managers.

How hiring managers evaluate mini-projects (what to show)

• Playable build: WebGL/HTML5, PC executable, or mobile APK — one-button entry for playtesters.
• 2–3 minute video: Quick walkthrough showing objectives, controls, and the player’s decision points.
• Design doc + README: One-page design goals, constraints, and what you learned.
• Source + dev log: GitHub/itch.io project with commit history, art attributions, and a reflective postmortem.
• Metrics: Simple playtest results (completion rate, average time) and a bullet list of tweaks.

Mini-project templates inspired by Cain — build these for your portfolio

Below are five complete mini-project prompts. Each includes scope, tech stack suggestions, core mechanics, level design tips, acceptance criteria, and how to present the finished piece to hiring managers.

1) Fetch Quest: "The Missing Compass" — teach economy & navigation

Goal: Design a short fetch quest that demonstrates item economy, navigation clues, and optional side interactions. Ideal for applicants targeting quest design or level design roles.

• One hub area, two sub-areas, 3–4 interactable NPCs, one unique quest item.
• Playable in 8–12 minutes or less.

1. Player receives a simple objective from an NPC to recover a lost item (the Compass).
2. Sub-areas include a guarded cache (combat/stealth optional) and a locked chest requiring a key found in the other area.
3. Optional mini-reward for returning other found objects (encourages exploration).

• Use clear landmarks and a breadcrumb trail: sound cues, a distinct skyline object, or a short journal hint.
• Place one optional risk-reward choice: shortcut guarded by enemies vs. safe but longer path.
• Keep art simple: reuse a tile set or modular environment to maximize polish.

• Playable build that completes the quest end-to-end.
• Clear onboarding (one-screen tutorial or tooltip).
• Metrics: 60–80% completion in blind playtest (shows reasonable challenge).

2) Moral Dilemma: "The Last Light" — branching narrative & player choice

Goal: Craft a short narrative quest where a single decision leads to meaningful trade-offs. Great for narrative designers and writers.

• Two main branches, each with distinct outcomes and a short epilogue scene.
• One moral lever (e.g., save one of two NPCs, sacrifice resources, or reveal a truth).

1. Introduce stakes in first 3 minutes with a simple interactive scene.
2. Give the player a choice tied to a visible resource (e.g., energy, reputation).
3. Show consequences quickly — changes in NPC behavior, access to later areas, or alternate dialogue.

• Use environmental storytelling to foreshadow consequences (graffiti, photos, short logs).
• Keep dialogue short and punchy; use audio logs for flavor if you can.
• Ensure both branches are satisfying; even a "worse" choice should reveal new information.

• Playable branching build with two distinct endings.
• Design doc that explains player intent, consequences, and replay value.
• Playtest notes showing players understood stakes and felt agency.

3) Puzzle Sequence: "The Lightworks" — show logic and spatial reasoning

Goal: Build a sequence of 4–6 interconnected puzzles that escalate in complexity and rely on a single core mechanic (reflection, switches, wiring).

• One puzzle hub with progressive rooms and a final meta-puzzle that uses all prior skills.
• Simple visual language: consistent symbols, audio cues for correct/wrong actions.

1. Establish the rule set in puzzle 1 (teaching moment).
2. Introduce a modifier in puzzle 2, a constraint in puzzle 3, and combine them in puzzle 4+.
3. Final meta-puzzle requires chaining mechanics from earlier rooms.

• Use minimal UI: puzzles should be solvable with in-world cues, not menus.
• Provide non-verbal feedback for success/failure (lights, sounds).
• Allow hint tiers: a minor hint available if player is stuck, to keep testers engaged.

• All puzzles solveable without external knowledge.
• Average solve time logged (target 3–7 minutes for the full sequence).
• Refinement: remove ambiguous solutions and add dampening for brute-force attempts.

4) Investigation Quest: "Echoes in the Archives" — systems & clue design

Goal: Create a short detective-style quest that encourages players to collect and synthesize clues. This demonstrates systems thinking and player guidance.

• 3–5 clues, one culprit reveal, and one puzzle requiring clue combination.
• Optional branching depending on which clues the player finds.

1. Clue items with short descriptions and an inventory view to combine clues.
2. A simple inference system: matching two clues opens a door or unlocks a memory.

• Use a visual board (in-game notebook) where players can pin clues and see connections.
• Space clues so players must explore multiple areas but not wander aimlessly.

• Players can reach the solution with at least 60% of clues found.
• Clues are meaningful (not red herrings unless labeled as such).

5) Time-limited Escort / Survival Objective: "Last Runner" — pacing & tension

Goal: Build a short escort or timed survival segment where pacing and AI behavior are central. Useful for applicants to systems or AI roles.

• Single map with a moving NPC or timed objective, obstacles, and one mechanic to protect/assist the NPC.

1. Simple AI for the escorted NPC with failure states (slowed, staggered).
2. Player tools: temporary barriers, healing, or distractors.

• Design safe checkpoints so the segment doesn't feel punishingly long.
• Balance challenge via enemy spawn timing or difficulty scaling.

• Playable run where player influence meaningfully changes success probability.
• Telemetry: success rate and common failure points to discuss in the postmortem.

Polish, packaging, and what hiring managers actually click

Finish each project with the same checklist — hiring managers skim, so make their life easy.

• 1-line elevator pitch under the project title: "A 10-minute puzzle sequence teaching reflective mechanics."
• Play button first: Put the playable build and video at the top of the page.
• Design highlights: Bullet points (mechanics showcased, systems solved, scope).
• What you learned: Two-sentence reflection showing growth and trade-offs.
• Links: GitHub repo, itch.io build, and a short credit list.

Game jams, student showcases, and timeline hacks

Use game jams to accelerate iteration. In 2026, many studios use jam entries as signals of hustle and teamwork — especially hybrid and remote-first teams. If you can, enter a jam and ship one of the above prompts as a jam theme. Keep these timelines in mind:

• 48-hour jam: Make a vertical slice (one teach + one solve loop) — perfect for a puzzle or fetch quest.
• 7-day jam: Add polish, audio, and an alternative ending — ideal for moral dilemmas and investigations.
• 2–4 week student showcase: Build the full mini-project with playtest data and a polished video.

Advanced 2026 strategies — AI, procedural tools, and remote playtests

Late 2025–early 2026 saw wider adoption of AI-assisted design tools. Use these strategically:

• AI for drafts: Generate placeholder dialogue or puzzle text with an LLM, then edit for tone — show the before/after in your dev log to highlight authorship.
• Procedural plugins: Use modular procedural tools to speed level blocking, but always hand-tune the player flow to demonstrate craftsmanship.
• Cloud playtesting: Use cloud-builds (itch.io, GitHub Pages, Steam Remote Play) and gather telemetry — attach simple analytics (times, success rates) in your postmortem.

Studios in 2026 value candidates who can combine automated workflows with thoughtful iteration. Emphasize where you used automation (and why you overrode it).

Example portfolio entry layout (copy-paste ready)

1. Title + 1-line pitch
2. 2-minute video (playthrough + designer commentary)
3. Play button (WebGL/Windows build)
4. What I solved (bullets: mechanics, scope, tech)
5. Design doc (one-page link)
6. Dev log highlights (3 commits/changes)
7. Playtest metrics & what I’d change next

How to tailor mini-projects to specific internships

Match the project to the role:

• Quest designer internships: Prioritize branching and player choice (moral dilemma, investigation).
• Level design roles: Emphasize spatial flow (fetch quest, puzzle sequence) with clear maps.
• Systems & AI internships: Show telemetry and AI behavior logs (escort/survival projects).
• Generalist student showcases: Ship two complementary mini-projects showcasing narrative and systems.

Real-world example (how to present one mini-project to hiring managers)

Fast sample pitch you could paste into an application:

"The Missing Compass — a 10-minute navigation-first fetch quest (Unity). I designed a two-route level with a risk/reward shortcut, implemented breadcrumb cues, and collected blind-playtest data (n=12). Completion rate: 67%. Key takeaways: players preferred risk for a shorter path when the hint frequency increased. GitHub + build: [link]."

Common mistakes and how to avoid them

• Over-scoping: Keep to one teachable mechanic per project.
• Poor onboarding: First two minutes must teach the core loop.
• Hidden fail states: Make failure transparent and fair.
• No postmortem: Hiring managers read your reflection; it shows maturity.

Quick checklist before you submit to a game dev internship

• Playable build: yes
• 2-min video: yes
• One-page design doc: yes
• Dev log with iterations: yes
• Playtest metrics: at least one simple stat
• Elevator pitch under project title: yes

Final thoughts — why focused mini-projects beat grand prototypes

In 2026, studios prioritize predictable, iterative contributors. A small, well-executed quest demonstrates the right habits: scoping, iteration, player empathy, and the ability to document learning. Use Cain’s quest types as a roadmap: pick one challenge, ship a tight loop, and show why your choice matters to players.

Call to action

Ready to build a portfolio piece that hiring managers actually open? Pick one mini-project above, ship within two weeks, and publish it to itch.io and GitHub. If you want a ready-made checklist and a 7-day sprint template, download our free Student Showcase Sprint — or submit your finished build to our next student showcase to get recruiter feedback and real playtesters.

Related Reading

• From Workers’ Comp to Retirement: Why Local Insurance Market Changes Matter to Older Home-Based Business Owners
• From Stove to Store: How DIY Cocktail Brands Inspire Fashion Collaboration Gift Sets
• Game Night Snacks on a Budget: Recipes for Magic & Pokémon Booster Box Parties
• Scent Layering 101: Use Your Skincare Launches as Base Notes
• CES Finds to Actually Use in Your Kitchen: From Smart Sensors to Durable Appliances