Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Get the latest Education e-news
  • Game Job Interview Questions And How to Answer Them

    - Jake Simpson

  • 11. What do you do on your own time to extend your skills?

    As a programmer, do you work on home projects? As a designer, do you doodle design ideas or make puzzles? As an artist, do you do portrait work?

    Having hired many people in the past, one of the things I can speak to with authority is that those people who spend their off time working on discipline-related projects are the ones who are always up on current trends, have new ideas, are most willing to try something new, and will be the ones taking stuff home to tinker with on their own time. Now that shouldn't be expected of everyone, but the sad reality is that there is competition for jobs out there, and those who are prepared to put in the extra work are the ones that are going to be in hot demand.

    Demonstrating that you learned C# over a weekend because you thought it was cool for prototyping is exactly the kind of thing a programming manager wants to hear. Suddenly your toolset expanded, and not only did it show willingness to do something without being told, it makes you more valuable.

    The only care to here is to not mention an outside situation that might detract from or compete with your day job.

    12. Do you have any questions?

    Yes. Yes, you do have questions. Some of your questions will have been answered in the normal give-and-take of conversation, but you should always be asked if you have others (and if not, something's wrong).

    Having questions means you're interested. Some questions are best directed to HR, while others should be asked of managers and future co-workers. Ask questions that show an interest in the position and the long-term plans of the company. For some ideas, see "Questions You Should Ask in an Interview," below. 

    It's Just a Conversation

    Always have something to say. Most questions asked in job interviews aren't knowledge-test questions. They're more like an invitation to converse on a given topic. If you can't answer them directly but can at least talk about what the question means, that's a good start.

    Be as honest as you can be. A company generally gets only a day with you, maybe two, to gather all it can before making a life-changing decision, both for you and for them.

    They need to see who you actually are rather than whom you think they want to see, because if that's what you do once you've started, it will become obvious pretty fast, and then bad things tend to happen. They need to be comfortable that there are no surprises coming with you as much as you need to know that they are solvent and able to actually ship what they say they will.

    Be honest. Be open and engage in the conversation with your interviewer. Express interest in what they are talking about. If you don't know or understand what's being asked, ask them! They don't expect you to be mind readers and it shows you can ask when necessary. After all, it's just a conversation.

    Questions You Should Ask In An Interview

    - What are the core working hours?

    - How do you assign or schedule tasks? Who gets to decide who does what and estimates time?

    - What's the career path for this job? How do I get to progress? What is the process for promotion?

    - What training approach do you use? How would I learn new skills?

    - How are personnel reviews handled? Who does them and how often?

    - Are there any specific development processes used here, for example, Scrum?

    - Who would I report to?

    - If I'm hired, what is the next game I might work on? How much input would I have on that?

    - Is there a relocation package?

    - What bonus structure or incentives are there?


comments powered by Disqus