Gamestop Software Engineer interview typically runs 4 rounds: HR screen, technical screen, onsite business interview, and onsite technical system design interview. The process took about a few weeks and was unusually drawn out for the role.
$135K
Avg. Base Comp
$153K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that GameStop is not screening for a narrow software engineer profile so much as a broad, end-to-end problem solver who can move from business framing to architecture to implementation without losing the thread. One experience stood out for how aggressively the conversation drilled through every layer of the stack: sizing, infrastructure, system architecture, application design, and even coding. That pattern tells us the bar is less about isolated technical depth and more about whether you can reason across the whole product and explain tradeoffs clearly under pressure.
A recurring theme is that the interviewers seem to be looking for a very specific kind of candidate, not just someone who matches the job posting. The questions about whether the candidate codes a lot and whether they had read two 300+ page system design books suggest a preference for people who have already invested heavily in architecture thinking. We’ve also seen signals that the process can feel unusually selective for the level, which means candidates who sound generic or overly polished may not stand out. The strongest fit here is someone who can speak concretely about systems, justify decisions with business context, and show comfort with ambiguity rather than trying to force a standard coding-interview script.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Gamestop process.
Far too many steps for what was advertised. I had a 30-minute remote HR screen first, then a 60-minute technical screen with a director, followed by a 30-minute onsite business interview with the VP of IT. The last round was the biggest one: a 90-minute onsite technical system design interview with the director and one remote technical person. That round started at a very high level, with business requirements and sizing, and then kept drilling down into rough order of magnitude estimates, infrastructure architecture, system architecture, application architecture, and eventually actual coding. It felt less like a normal software engineer interview and more like they were trying to see whether I could cover every layer of the stack at once.
The questions themselves were broad and a little odd. They asked things like whether I code a lot and whether I had read two 300+ page system design interview books, which gave me the impression they were looking for a very specific kind of candidate rather than someone who fit the job description. The process also felt extremely drawn out for the level of role, and the compensation seemed low for what they were asking. I never got an offer, and honestly it seemed like they had already interviewed a huge number of people and were still searching for a unicorn. If you go in, be ready for a heavy system design focus that goes all the way from business framing to implementation details, not just standard coding questions.
Prep tip from this candidate
Be ready to walk through system design from business requirements to sizing, infrastructure, and application architecture, and expect follow-up questions that test whether you actually code regularly. It would also help to review the kind of material covered in long-form system design interview books, since that was explicitly referenced.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Gamestop
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Customer Orders | |
| Merge Sorted Lists | |
| Prime to N | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Scrambled Tickets | |
| Closest SAT Scores | |
| Top 3 Users | |
| P-value to a Layman | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Over 100 Dollars | |
| Size of Joins | |
| Address Schema | |
| Download Facts | |
| Last Transaction | |
| Permutation Palindrome | |
| Average Quantity | |
| Manager Team Sizes | |
| Emails Opened | |
| Longest Increasing Subsequence | |
| Nearest Common Ancestor | |
| Month Over Month | |
| Daily Retention Summary | |
| Flight Records |
Synthesized from candidate reports. Individual experiences may vary.
A remote screening with HR to cover basic background, role fit, and logistics. This appears to be the first contact in the process.
A technical interview led by a director. The candidate reported broad questions and an emphasis on technical depth, setting the tone for a process that goes beyond a standard coding screen.
An onsite business-focused interview with the VP of IT. This round likely assessed communication, business understanding, and alignment with the team’s needs.
A long technical round with the director and one remote technical interviewer. It started at a high level with business requirements and sizing, then drilled into rough order of magnitude estimates, infrastructure architecture, system architecture, application architecture, and eventually coding.