Real, anonymous reports from people who interviewed for QA Engineer at PlayStation, newest first and distilled into what to expect across the loop.
The most exhausting part of my PlayStation QA process was the take-home assignment. Along with it, they asked me to solve a hard LeetCode-style problem, and I ended up putting real effort into getting the solution right. Once I had it, I pushed the code into the GitHub repository and submitted it to the interviewer.
My interview experience was pretty smooth and fairly quick. After some introductory context about the company, I moved into a technical conversation that lasted about 45 minutes. The interviewer was easy to talk to, and I was able to answer everything they asked.
The interview process typically consists of multiple rounds, including initial phone screens, technical interviews, and managerial discussions, often culminating in a final onsite interview. Candidates can expect a mix of technical and behavioral questions throughout the stages.
Candidates should prepare for a variety of technical topics, including SQL, data warehousing, coding challenges (often LeetCode-style), and QA-specific scenarios that assess practical testing skills. The technical interviews are structured and may involve back-and-forth discussions.
Interviews often include behavioral questions aimed at assessing cultural fit and personal interests, particularly in gaming. Candidates should be ready to discuss their QA experience and how it relates to their passion for games.
Some candidates may encounter demanding take-home assignments or practical tests that require detailed documentation of testing processes. It's important to be prepared for the possibility of a practical evaluation that may include writing test cases and defect reports.
Candidates noted varying levels of clarity regarding expectations, particularly in final rounds, which sometimes led to confusion. It's advisable to seek clarification on the structure and focus of each interview stage to avoid surprises.
While many candidates reported positive experiences during interviews, a common theme was the lack of constructive feedback after rejections, leaving them uncertain about areas for improvement. Candidates should be prepared for the possibility of not receiving detailed feedback.