Game Designer interview questions

I define the vision as a testable player experience, not a summary of features.

• I write a one-sentence player promise naming the audience, the core action, and the intended feeling.
• I map that promise to a core-loop diagram showing which repeated choices are meant to create that feeling.
• I add a vision test: if a prototype cannot demonstrate the promised experience without progression or polish, the concept needs revision.

The vision states the experience we want to deliver, while pillars define the recurring qualities required to deliver it.

• I keep the vision as one memorable player-facing statement and document pillars as three to five decision criteria.
• I give every pillar observable evidence, such as meaningful route choice rather than the vague label freedom.
• I reject a pillar that merely restates the vision or names a feature, because it cannot compare alternative implementations.

A useful pillar creates a hard reason to say no, even to an individually appealing feature.

• I maintain a pillar-fit matrix that scores each proposal by direct support, neutrality, or contradiction.
• I require a feature owner to name the player behavior the feature strengthens, not just the pillar vocabulary it resembles.
• I cut or redesign any feature that weakens a higher-priority pillar unless measured value justifies an explicit exception.

I rank principles by authority so lower-level rules cannot quietly override the product promise.

• I use a principle stack ordered as player promise, product pillars, system rules, and local content guidelines.
• I attach a concrete failure signal and review trigger to each level, such as a core loop no longer rewarding its intended behavior.
• When principles conflict, I protect the higher level and document the local exception in a decision record with a review trigger.

I place a feature where its intended behavior and failure cost match the player's level of commitment.

• It belongs in the core loop only if repeated use is essential to the player promise and removing it would change the game's identity.
• It belongs in the metagame when it organizes choices between sessions, such as loadout planning, without interrupting moment-to-moment mastery.
• It stays optional when it serves a narrower motivation or adds learning cost, and I prototype its effect before letting it create progression or economy dependencies.

I align rewards with the verbs and choices the game claims are central.

• I build a verb-to-reward map linking each core action to immediate feedback, progression value, and the behavior it reinforces.
• I audit dominant strategies because an efficient reward path can make expressive or skillful verbs functionally irrelevant.
• I change the incentive before adding content when telemetry or playtests show players repeating a low-value action for the best reward.

I preserve the genre contract that supports comprehension and differentiate one high-impact part of the experience.

• I create a genre contract sheet separating table stakes, flexible conventions, and assumptions we deliberately challenge.
• I express the differentiator through a repeated core-loop choice rather than a theme, setting, or one-off mode.
• I prototype the changed convention early and restore familiar cues if novelty increases confusion more than meaningful choice.

I isolate uncertainty so the team can test a bold premise without betting the whole product on it.

• I keep a risk register that separates experience risk, comprehension risk, production risk, and commercial dependency.
• I define a cheapest credible test and a pass threshold for each high-risk assumption before expanding scope.
• I protect one signature risk, but remove dependent experiments when several unproven ideas must all succeed for the core loop to work.

I choose the option that creates more meaningful decisions per unit of production cost.

• I use a depth-versus-scope model comparing new decision space, reuse of existing assets, learning burden, and ongoing content cost.
• I deepen a system when players have mastered its current answer and new interactions can create multiple viable strategies.
• I add breadth when repetition comes from exhausted situations, but avoid new content that only reskins the same optimal decision.

I make the trade-off explicit, rank it against the player promise, and choose with reversible evidence where possible.

• I write a decision brief naming the competing values, affected player segment, expected behavior change, and cost of being wrong.
• I apply the principle hierarchy first, then compare options with a weighted matrix only when both values remain legitimate.
• I time-box a prototype for the most uncertain assumption and record the chosen trade-off, metric, and revisit condition.

A strong boundary gives each system one clear set of invariants while exposing only the information other systems need.

• Assign ownership by rule: combat owns damage resolution, while progression owns unlock conditions, so neither system silently changes the other's contract.
• Describe each interface as inputs, outputs, timing, and limits; for example, a quest requests a reward package rather than setting wallet balances directly, trading convenience for safer change.
• Map dependencies as a directed graph and make feedback loops explicit; gear unlocks harder content and harder content supplies gear, but a shared power-band rule keeps that loop coherent.

Emergence is safest when players can combine simple rules freely inside a few non-negotiable constraints.

• Define invariants such as one action per turn or a bounded resource budget; a deck combo may bend normal efficiency, but it cannot bypass the turn economy entirely.
• Price effects through shared budgets such as damage, tempo, reach, and reliability, accepting that a common budget improves comparability but can flatten unusual mechanics.
• Add systemic dampers rather than exception lists; diminishing returns on repeated crowd control contains many future combinations, while per-card bans preserve more local texture but scale poorly.

I keep long-term purchasing power predictable while allowing short-term demand and opportunity to move.

• Anchor the economy to a benchmark basket, such as one upgrade plus several consumables, so nominal prices can change without losing sight of real player purchasing power.
• Create dynamism in relative value through rotating recipes, event bonuses, and category demand; this produces discovery without inflating every faucet at once.
• Use tolerance bands for stock-to-flow and faucet-to-sink ratios by progression segment; narrow bands improve predictability, while wider bands permit stronger events but create more correction risk.

Faucets and sinks should follow economic state, not treat the whole population as an average player.

• Segment by progression, wealth, and activity because account age alone misclassifies returning or highly efficient players; a new endgame entrant and a wealthy veteran need different pressure.
• Use a cohort flow matrix that shows source volume, sink incidence, and resulting inventory; leveling rewards can fund essential upgrades while veteran surpluses meet prestige crafting or collection sinks.
• Keep bridges between cohorts deliberate; tradable catch-up materials help newcomers, but caps or diminishing returns may be needed to prevent veterans from turning support demand into another compounding faucet.

Each currency needs a distinct economic job, time horizon, and set of conversion relationships.

• Model currencies as nodes and earning, spending, and conversion paths as edges; soft currency handles routine breadth, while raid tokens guarantee progress in one narrow domain.
• Avoid reversible conversion cycles unless every cycle has a meaningful loss; premium to soft to tradable goods can otherwise create an unintended exchange rate and arbitrage path.
• Balance universal and specialized currencies deliberately; universal value reduces cognitive load, while event or mode currencies isolate inflation and protect progression but increase wallet clutter and stranded balances.

Long-lived progression needs new value axes more often than a permanently rising power ceiling.

• Maintain a power budget across damage, survivability, utility, and constraints; a sidegrade can trade raw damage for mobility, preserving choice instead of strictly dominating prior gear.
• Design content around overlapping capability bands; an older encounter can remain relevant for materials or mastery even when its direct power reward is no longer best in slot.
• Use bounded resets, caps, or selective upgrading to control accumulated gaps; these protect balance and onboarding, but overly aggressive normalization weakens ownership and the meaning of past investment.

A resilient conversion loop has no profitable closed cycle and limits the damage any single edge can cause.

• Evaluate the conversion graph after fees, bonuses, and by-products; crafting and salvaging the same item should return less total value than it consumes, even under the best legitimate modifiers.
• Put containment at high-risk edges through bound intermediates, capacity limits, or diminishing returns; this restricts arbitrage exposure but also reduces freedom for legitimate specialists.
• Give rates an economic anchor such as time, scarcity, or a benchmark good; fixed isolated ratios are simpler, while anchored rates adapt better when upstream faucets or downstream demand evolve.

An item needs a planned path from scarcity to saturation and eventually to a useful exit.

• Define an adoption curve for introduction, broad acquisition, and maturity; a rare recipe can begin as an aspirational drop, then gain deterministic access as the content ages.
• Match sinks to item identity and supply; upgrade consumption suits materials, while collection, rerolling, or durability can absorb equipment without making every reward feel disposable.
• Preserve residual value through salvage, inheritance, or legacy collections; generous exits support ownership trust, but they also retain more wealth and reduce the strength of future demand.

Rollover policy should separate seasonal competition from durable player ownership while preventing stockpiles from deciding the next season.

• Classify resources by promise: rank and seasonal crafting inputs may reset, while paid value and long-term collection progress should usually persist.
• Use a capped or diminishing conversion into a durable currency; this gives leftover effort residual value without making hoarding the dominant seasonal strategy.
• Preserve a small head start only where freshness can tolerate it, such as cosmetic tokens rather than power materials; a full reset maximizes parity, while full carryover protects continuity but compounds wealth gaps.

Sustainability comes from a content cadence that reuses systemic depth without accumulating unbounded economic obligations.

• Build a content matrix from reusable verbs, modifiers, reward roles, and audience bands; a familiar encounter rule in a new combination costs less novelty than a wholly bespoke mode but risks repetition.
• Give each release an economy budget covering new supply, new demand, and permanent inventory growth; adding a material faucet with a matching long-term sink prevents content volume from becoming pure inflation.
• Balance permanent, seasonal, and repeatable layers with planned catch-up and retirement paths; permanence builds breadth, while rotation limits complexity and keeps future entry points manageable.