Game Design Portfolio: Showcasing Mechanics, Not Just Art

Most rejected applications in Indian game studios share one flaw: the candidate sent a beautiful art folio for a design role. If you want a design seat at Ubisoft Mumbai, Sumo Pune, Lakshya, Rolocule or any indie team in Andheri, your portfolio has to prove you can design loops, balance numbers and ship playable levels. This game design portfolio guide walks through what to include, how to structure case studies, and how to talk about your work the way leads actually evaluate it.

Why mechanics beat art in a game designer portfolio

Studios hire artists from art portfolios. They hire designers from systems thinking. A common mistake from students in Mira Road, Borivali and Thane is to fill a game designer portfolio with character renders, environment paintings and concept boards. Beautiful work — but it answers the wrong question. The lead designer is asking: can you frame a problem, propose a rule set, prototype it, test it with humans, and iterate?

Your folio must answer that in three minutes of skim time. The recruiter will not read a 40-page PDF. They will scan headings, look at one GIF, read your "decision log" if you have one, and decide if a phone call is worth it.

A strong game design portfolio guide for 2025 hiring boils down to four pillars:

• Playable artefacts — even rough builds beat polished mockups.
• Decision logs — show why you cut feature X, not just that you shipped it.
• Numbers — playtest counts, retention deltas, balance spreadsheets.
• Range — at least one systems piece, one level, and one narrative or economy sample.

Project selection: three pieces is enough

Six average projects lose to three sharp ones. When mentors at Storyboard review student folios in Mira Road, the first cut is usually project count. If you cannot defend a project in a 15-minute interview, remove it.

A reliable structure:

1. One systems design piece — a combat loop, an economy, a progression curve, or an AI behaviour tree.
2. One level design sample — a single level documented from greybox to playtest, ideally in Unreal or Unity.
3. One "wildcard" — narrative branching in Twine, a board game prototype, a Roblox mini-game, or a mod for an existing title.

The wildcard matters. It tells the studio you design for fun, not only for marks. Many designers at Indian studios got their first interview off a Half-Life 2 mod, an Unreal jam build, or a paper prototype they ran at college.

What counts as a level design sample

A level design sample is not a screenshot of a pretty environment. It is a documented walk-through that shows intent. The minimum:

• Top-down map with pacing beats marked (combat, breather, set-piece, reward).
• Greybox screenshots or a 60-second video flythrough.
• A short paragraph on the player fantasy and the one new mechanic the level teaches.
• One thing you cut and why.

If the level was built for a game jam, say so — leads respect jam constraints.

How to present a case study

Every project page in your folio should follow the same skeleton. Consistency is a quiet signal of professional maturity.

1. One-line pitch — genre, platform, team size, your role, duration.
2. The design problem — what question were you solving? Example: "How do we make a stealth level that teaches line-of-sight without a tutorial pop-up?"
3. Your hypothesis — the rule or mechanic you proposed.
4. Prototype — GIF, video or playable WebGL link.
5. Playtest data — even five testers with a Google Form is data.
6. Iteration — what changed between v1 and v3.
7. Outcome and learnings — honest, not boastful.

The iteration section is where most student folios collapse. They show a final build and call it done. Show the ugly middle. Show the version that broke, the spreadsheet that proved the economy was inflationary, the level that testers got lost in. That story is what separates a hireable designer from a hopeful one.

Tools and artefacts recruiters expect

You do not need every tool. You do need fluency in a sensible stack. For Mumbai studios working on mobile, console and AR/VR projects, the common asks are:

• Engines: Unity (C#) or Unreal (Blueprints, ideally some C++). Pick one and go deep.
• Documentation: GDDs in Notion, Confluence or Google Docs. Keep them short — one-pagers beat 50-page bibles.
• Systems: Miro or FigJam for flow diagrams, Machinations for economy modelling.
• Spreadsheets: Google Sheets for balance tables. If your folio has no spreadsheet, add one.
• Version control: Git or Perforce basics. Mention which.
• Narrative: Twine, Ink or articy:draft for branching dialogue.

Drop one artefact from each bucket into your folio. A balance spreadsheet screenshot with annotations beats a paragraph claiming "I balanced the economy."

The decision log: your secret weapon

A decision log is a one-page document, kept per project, listing every meaningful design call and the reason behind it. Example entries:

• "Reduced shotgun spread from 12 to 8 degrees after v2 playtest — testers felt the weapon was unreliable inside 5m."
• "Cut the crafting subsystem in week 6 — scope risk, and the loop tested fine without it."
• "Moved the boss arena pillar two metres east so the player sees the health pickup before committing to the fight."

Five entries per project is plenty. This single artefact transforms a folio from "look what I made" to "look how I think." Senior designers in Pune and Mumbai who interview juniors will tell you the decision log is what they read first.

Local context: building a folio from Mira Road

The Mumbai game scene is small but growing — Andheri, Powai and Lower Parel host most studios, and indie teams are scattered across Thane and Navi Mumbai. Students from Mira Road, Bhayandar, Dahisar and Borivali have a real advantage: a Western Line train ride puts them inside ten studios for portfolio reviews and meet-ups.

At Storyboard VFX & Animation Institute, our gaming and design programmes push every student through three documented projects in the year — exactly the structure outlined above. Mentors run portfolio reviews against the same rubric used at hiring studios, and our showcase reel is built from student artefacts that have already landed interviews.

Salary expectations matter for parents reading along. A junior game designer in Mumbai typically starts between ₹3–5 LPA, with senior systems and level designers commanding ₹8–15 LPA depending on shipped titles. Portfolio quality, not college brand, is the single biggest lever on that first offer.

Common portfolio mistakes to fix this week

A quick checklist drawn from hundreds of mock interviews:

• Hosting your folio as a 30MB PDF. Use a simple website — Notion, Webflow, or a free Wix page. Recruiters open links, not attachments.
• Burying playable builds. Put the WebGL link or itch.io page above the fold on every project page.
• No role clarity. If it was a team project, list exactly what you owned. "Designed the dash mechanic and tuned its iframes" beats "worked on combat."
• Long write-ups, no visuals. Every project page needs at least one GIF or short video. Recruiters skim.
• Ignoring UI and UX. Game design and UI/UX design overlap heavily — menu flow, HUD readability and onboarding are design problems studios ask about constantly.
• Spelling and grammar. Indian English spellings throughout — programme, behaviour, colour. A sloppy folio reads as a sloppy designer.

A simple two-week sprint to upgrade your folio

If your current game designer portfolio is weak, here is a focused fortnight:

1. Day 1–2: Pick your three projects. Kill the rest.
2. Day 3–5: Build or rebuild one level design sample with a top-down pacing map and a 60-second video.
3. Day 6–8: Write the decision log for all three projects, five entries each.
4. Day 9–10: Record short Loom walk-throughs for each project — three minutes max.
5. Day 11–12: Move everything onto a clean Notion or Webflow site. One project per page, consistent layout.
6. Day 13: Show it to two designers you respect. Take notes.
7. Day 14: Fix the top three pieces of feedback. Ship.

That is genuinely all it takes to move from rejected to shortlisted.

Talk to Storyboard about your portfolio

If you want a senior eye on your game designer portfolio before you send it out, our admissions team at Storyboard in Mira Road East runs free folio reviews for prospective students. Call 091521 55527 or visit our contact page to book a slot — bring whatever you have, even rough builds, and we will tell you honestly what to cut, what to expand, and what to ship next.