Sony Software Engineer candidates reported a recruiter call followed by background, technical, and behavioral/project-management conversations, with one concise LC299-style coding exercise.
$145K
Avg. Base Comp
$216K
Avg. Total Comp
4 rounds
Typical Rounds
2-4 weeks
Process Length
For a Sony Software Engineer interview, the clearest reported pattern is a process centered on your prior work rather than an extensive algorithm sequence. One candidate described a recruiter call, then a hiring-manager conversation about background and earlier work. That was followed by a technical discussion focused on the candidate’s resume, a project explored in depth, and basic questions about the language or stack used, including Java basics.
Prepare to explain one project end to end: what you built, the choices you made, and why that stack fit the work. The reported technical exercise was a LeetCode-style variation of LC299: generate a hint from a hidden secret input after clarifying requirements. The candidate found it manageable in roughly 20 minutes and characterized it as easy-to-medium rather than a difficult DSA screen. A later behavioral-style conversation was framed around project-management experience.
There was no separate system-design interview in this report, and the candidate emphasized that interviewer approach can shape the experience. Evidence is limited to one detailed firsthand process, so treat the sequence as a useful preparation focus rather than a fixed template. Practice communicating project tradeoffs clearly, then refresh concise coding problems where careful requirement clarification and a clean implementation matter.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Sony process.
The process felt lighter than what I usually expect for a software engineer role. I started with a recruiter call, then had a hiring manager round that was mostly about my background and the work I had done before. After that there was a technical round, but it was still pretty focused on my resume and the project I had discussed rather than deep algorithm questions. There was also a behavioral-style round that they framed more like project management experience, and I did not have a separate system design interview.
The only real coding round I had was a standard LeetCode-style problem that was doable in about 20 minutes once I clarified the requirements. The question was a variation of LC299, where I had to generate a hint from a hidden secret input. That was the most technical part of the process, but even then it felt more like an easy-medium coding exercise than a hard DSA screen. In the other technical conversations, they asked about my resume, a project in depth, and some basic questions around the language or stack I had used, including Java basics. Overall the interview felt more dependent on the interviewer than on a rigid process, and the online format was straightforward.
I ended up getting the offer, and my main takeaway is that this process seems to reward being able to talk clearly about your past projects and explain your stack choices, while also being ready for one concise coding question rather than a full algorithm marathon.
Prep tip from this candidate
Be ready to walk through one project in depth and explain why you used a particular language or stack, since that came up repeatedly. Also practice the LC299-style secret/hint problem and similar easy-medium coding questions, because that was the main coding round.
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 Sony
Return keys with weighted probabilities
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Prime to N | |
| Random SQL Sample | |
| Find the Missing Number | |
| P-value to a Layman | |
| Upsell Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Retailer Data Warehouse | |
| Google Maps Improvement | |
| Recurring Character | |
| Hurdles In Data Projects | |
| Address Schema | |
| Average Quantity | |
| Permutation Palindrome | |
| Integer to Roman | |
| The Brackets Problem | |
| Size of Joins | |
| Liked Pages | |
| Twenty Variants | |
| Equivalent Index | |
| Completed Shipments | |
| One Element Removed | |
| Paired Products | |
| Detecting ECG Tachycardia Runs |
Synthesized from candidate reports. Individual experiences may vary.
One candidate started with a recruiter call. Be ready to summarize your background and interest clearly, while recognizing that no specific recruiter questions or timing were reported.
The reported hiring-manager round focused mostly on the candidate’s background and previous work. Prepare a concise narrative for your experience, contributions, and the context around a project you owned.
The technical conversation reportedly returned to the resume and a project in depth, with basic language or stack questions including Java. Its coding portion used an LC299-style secret-and-hint variation; candidates may benefit from clarifying requirements before implementing an efficient solution.
The candidate also described a behavioral-style round framed around project-management experience. Expect discussion of how you planned, coordinated, or delivered work, but specific questions were not reported.
