It s been one year since we launched the GamesIndustry.biz Academy, and the section has gone from strength to strength since then.
With the aim to both support the next generation of game developers and provide resources to existing members of the games industry, the Academy produced over 250 guides to making, funding, monetising, promoting and working in video games in the last year. These articles were produced by the
GamesIndustry.biz team of course, but we also collaborated with over 100 external contributors, experts in their fields, who shared knowledge in our pages.
In October, with the support of Creative Assembly, we organised a digital event designed to connect university and college students with games industry professionals in the UK GI Live: Academy, during which more than 1,500 students and 40 games companies joined a Discord server to meet and network. You can watch the event here.
You ve made it through the application selection and have been invited for an interview for your dream role. This is just the beginning of a long and stressful process where your hard and soft skills will be constantly evaluated through a series of tests.
Being interviewed is something all of us will have to go through multiple times throughout our careers, but it can be daunting even for the most seasoned professionals.
Not only have I been through plenty of interview processes as an interviewee, but I also regularly interview candidates for programming vacancies at Splash Damage. As another hiring period is about to begin, I would like to share a few pointers and tips based on my experience interviewing candidates. Don t expect a ten tips to get the job type of post, rather a collection of observed behaviours that can lead to an unsuccessful interview.