Glassdoor users rated their interview experience at Push Gaming as 33.3% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Account Manager and Devops Engineer rated their interviews as the hardest, whereas interviews for Account Manager and Devops Engineer roles were rated as the easiest.
The hiring process at Push Gaming takes an average of 14 days when considering 3 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for Junior Game Mathematician had the quickest hiring process (on average 14 days), whereas Junior Game Mathematician roles had the slowest hiring process (on average 14 days).
I applied online. I interviewed at Push Gaming in Jul 2025
Interview
2 stage interview process, one with HR and another with the QA Lead. HR is a screening check, and QA Lead was a barrage of technical questions with a poorly planned technical test where you need to write a test plan for a prototype slot game.
Interview questions [1]
Question 1
Questions were mostly QA based questions, but software QA not gaming QA, some terms you wouldn't typically use in the gaming industry. So be aware of technical jargon from outside video games.
I applied online. The process took 4 weeks. I interviewed at Push Gaming (London, England) in May 2024
Interview
Interview was just basic probablity and stats questions in long form. Interviewer was very cold and not very welcoming. I had a hard time trying to concentrate unfortunately, just a bad day for me.
I applied online. I interviewed at Push Gaming (Birmingham, England)
Interview
The 3-stage Interview process includes an initial chat, a technical interview, and a company fit interview. The technical interview includes Typescript questions and basic object-oriented questions with code examples. The company fit interview was a bit more of an extension to the technical interview, it was with a Senior developer and involved asking questions about how I would recreate some of their games and showing examples I had worked on from GitHub.
Interview questions [1]
Question 1
A question that caught me off guard was the requirements to change the major part of a version number, i.e. semantic variation.