Games companies are a good place to work if you dont like sleeping, and you dont like having software that was designed to be testable in the first place. (See my answer to question 4 for more detail.) But If I was in an interview, and I got 4 questions, I’d be sure to provide answers I am confident with sharing.
Q1 : Core Functionality 20% ; New Functionality 50% ; Broad functionality 30%. No point in testing core functionality if higher level tests in the “All” segment should be designed to catch core issues anyway.
Q2 : Verify all bugs that the devs say they have fixed ; then do the release checks , then fill out a report. In that order. Why? Since the bugs you are verifying were high enough priority to fix, they are of value to the TEAM, and to the mission, else the devs would not have attempted to fix them, not fixing them jeopardizes the mission goal. Start the release checks, likely you will spot a thing that got missed in the mad rush that you find yourself in at 5pm on a Friday. That thing is your reason for raising a red flag. File a test report, without doing a full regression test run and make a note about why the report is so blank.
Q3 : This is a trick question that assumes that you don’t have process pain in your teams. Tasks that had no testing identified will probably not be listed, for example.
Q4 : You will become a QA lead at some future point, so a good answer is needed. The right answer is however very context dependent. I would start by making the whole team responsible for quality as my primary message. I would be asking my team to include a small quality related deliverable (not a bugfix, but a quality-improving ticket/task) as a goal in every sprint-goal.
(coda) Software maintainability is increasingly identified as a cost to a project, so anything you do that improves troubleshooting, reliability and overall code maintainability and most of all security (code and penetration security) are quality improvements. To this end many modern teams are trying to cut technical debt, this is largely never true in computer games however - so these teams could forever be in tech debt pain.