Start Building

Lesson 10: Interview Preparation & Negotiation

In Lesson 9 you focused on networking and industry connections so the right people can discover your work. This lesson is about what happens when those efforts pay off: interviews and offers. You will learn how to prepare without memorizing scripts, present your portfolio clearly, and negotiate in a way that feels professional rather than confrontational.

What You'll Learn

By the end of this lesson you will be able to:

  • Prepare for interviews with a focused, repeatable checklist
  • Tell strong project stories based on your portfolio pieces
  • Handle common interview formats (screening, technical, portfolio review)
  • Ask smart questions that show you are evaluating the studio too
  • Negotiate offers around salary, benefits, and scope with confidence

Step 1: Clarify Your Targets and Constraints

Good interview prep starts before you book a call. You need clarity on what you want so you can tell if an opportunity fits.

Define your target roles

Write down:

  • Target roles (e.g. gameplay programmer, technical artist, systems designer)
  • Seniority level you are aiming for (junior, mid, senior)
  • Platforms and engines you want to work with (Unity, Unreal, Godot, mobile, console, PC)

This gives you a filter for which projects from your portfolio to highlight and how to frame your stories.

Set your practical constraints

List your non-negotiables:

  • Minimum acceptable salary or rate (range is fine)
  • Location / time zone and remote vs on-site preferences
  • Working hours constraints
  • Visa or legal restrictions, if any

You do not need to share this list with studios, but it will shape the questions you ask and how you negotiate later.

Pro tip: A small, realistic range (for salary and role level) is easier to negotiate than “anything is fine.” It also helps you quickly decline roles that will not work.

Step 2: Build a Story Bank from Your Portfolio

Interviewers usually ask for examples:

  • “Tell me about a time you solved a hard problem.”
  • “Walk me through a project you are proud of.”
  • “Describe a time something went wrong and how you handled it.”

Instead of improvising under pressure, build a story bank based on your portfolio projects.

Choose 4–6 anchor projects

From your portfolio, pick projects that:

  • Match your target roles (same engine, genre, or responsibilities)
  • Have clear challenges (technical, design, team, or production)
  • Had measurable outcomes (shipped, players, performance, learning)

For each project, write a short bullet summary:

  • Context: What was the project and your role?
  • Challenge: What problem or constraint did you face?
  • Actions: What did you do specifically?
  • Result: What changed because of your work?

This structure (often called STAR: Situation, Task, Action, Result) keeps answers focused and concrete.

Map stories to common question types

Create a small table for yourself:

  • Technical problem you solved → project A
  • Collaboration or conflict you handled → project B
  • Failure or mistake you learned from → project C
  • Time you improved a system or process → project D

Now, when a question comes up, you already know which project story to tell instead of searching your memory live.

Step 3: Prepare Your Portfolio Walkthrough

Most game studios will either:

  • Ask you to share your screen and walk through your portfolio or a specific project, or
  • Ask you to send a video or deck ahead of time.

Prepare a consistent walkthrough so you do not ramble or forget key points.

Structure a 5–10 minute walkthrough

For a single project, aim for:

  1. Overview (1–2 minutes)
    What the project is, your role, tools used, and goals.
  2. Deep dive (3–5 minutes)
    One or two systems or features you owned (code, design, art, or production).
  3. Results and reflection (1–2 minutes)
    What shipped, what you would improve next time, and what you learned.

Keep visuals ready:

  • Build a simple checklist: playable build, video capture, screenshots, and any diagrams.
  • Test your screen share, microphone, and build beforehand.

Rehearse out loud

Practice your walkthrough:

  • Alone, recording yourself
  • With a friend or in a community channel
  • With mock interviews (Discord, forums, or portfolio review groups)

Focus on being clear and calm, not perfect. You want to sound like you are explaining your work to a teammate, not reading a script.

Step 4: Handle Common Interview Formats and Questions

Game industry interviews often mix:

  • Screening calls with recruiters or HR
  • Portfolio or technical interviews with leads
  • Culture or team interviews

Screening calls

Goals:

  • Confirm basic fit (role, location, salary range)
  • Check your communication and enthusiasm

Prepare short answers for:

  • “Tell me about yourself.” → 1–2 minute summary ending with why this role fits your goals.
  • “Why this studio?” → One or two specific reasons (games they shipped, values, tech stack).
  • “What are your salary expectations?” → Give a realistic range based on research and your constraints.

Technical and portfolio interviews

Here you will:

  • Walk through portfolio projects
  • Answer technical or design questions
  • Sometimes complete a small take-home or live exercise

When you do not know an answer:

  • Be honest: explain what you do know and how you would find out.
  • Show your thinking: outline steps, trade-offs, and risks.

Common mistake: Pretending to know something you do not. It is better to show how you learn and reason than to guess confidently and be wrong.

Culture and team interviews

These questions focus on collaboration and values:

  • “Tell me about a conflict on a team and how you handled it.”
  • “How do you handle feedback on your work?”
  • “What does a healthy team look like to you?”

Use your story bank and be specific. Mention what you learned and how you adjusted your behavior afterward.

Step 5: Negotiation Basics for Game Dev Roles

If an offer comes, negotiation is not about being difficult; it is about finding a mutual fit.

Know your ranges

Before you see an offer, define:

  • Ideal range (what would feel great)
  • Acceptable range (still a good fit)
  • Walk-away point (below this, you decline)

Use salary reports, community data, and local cost of living as references. Remember to adjust for remote vs on-site and benefits.

How to respond to an offer

You can:

  • Thank them and ask for time to review (24–72 hours is common).
  • Ask clarifying questions about responsibilities, expectations, and growth.
  • If you counter, be specific and polite:
    • Reference your research and competing opportunities if relevant.
    • Ask for changes that matter most (base salary, title, relocation support, remote flexibility).

Example framing:

“Thank you for the offer. Based on my research and experience, I was hoping for something closer to [X–Y] for this role. Is there room to move in that direction, or adjust other elements of the package?”

When to say no

It is okay to decline if:

  • The offer is far below your acceptable range and cannot move
  • Red flags appear during the process (toxic behavior, unclear scope, unpaid overtime expectations)
  • The role does not align with your long-term goals

Saying no respectfully keeps the door open for future roles:

“Thank you for the opportunity and the time everyone spent with me. After considering the offer and my current goals, I have decided to decline. I appreciate the conversation and hope we can cross paths again.”

Mini Challenge

This week, complete the following:

  1. Create a story bank with at least 4 portfolio-based stories mapped to common questions.
  2. Record a 5–10 minute walkthrough of one key project and watch it back once, noting what to improve.
  3. Write down your salary range and constraints and one or two negotiation phrases you feel comfortable using.

Optionally, share your story bank or a short clip of your walkthrough in a trusted community or with a mentor and ask for feedback.

Troubleshooting

“I get extremely anxious before interviews.”
Start with low-stakes practice: mock interviews with friends, communities, or even talking to a camera. Build a ritual (short walk, breathing exercise, notes review) that you repeat before every interview.

“I do not have many shipped projects yet.”
Use game jams, prototypes, or course projects as your examples, but be honest about their scope. Focus on your specific contributions and what you learned.

“I am afraid negotiating will make them withdraw the offer.”
Healthy studios expect some negotiation. If a studio punishes you for politely asking questions or making a reasonable counter, that is useful information about whether you want to work there.

Recap and Next Steps

  • Clarify your target roles and constraints so you know what you are aiming for.
  • Prepare a story bank and portfolio walkthrough so you can answer questions calmly and clearly.
  • Negotiate with respect and data, focusing on what matters most to you.

In Lesson 11: Professional Development & Learning you will design a long-term growth plan so that, once you land a role or project, you keep leveling up your skills and portfolio over time.