Sony Software Engineer candidates describe a recruiter screen, deep resume and project conversations, and a technical round that varies by team. Coding ranges from an easy-medium LeetCode problem to C++/SQL or DSA questions.
$163K
Avg. Base Comp
$216K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Sony's Software Engineer interviews as heavily centered on your own projects, with the technical bar depending a lot on the team. One candidate who received an offer said the process felt light: a recruiter call, a hiring manager conversation about past work, a resume-based technical round and one 20-minute coding problem, a variation of LC299 (generating a hint from a hidden secret). Another, who was rejected, reported follow-ups on every resume claim and a medium-to-hard water-trapping problem, plus questions about design choices.
The technical content looks different from report to report. One candidate was asked about C++ object-oriented concepts and SQL, including a top-3 salaries query with GROUP BY and HAVING. Another described a React live-coding round and an architecture breakdown of a live dashboard. A third faced a timed two-hour C programming test with no outside help, and said an unfamiliar algorithm would have been the optimal approach.
Behavioral and fit questions appear in several reports, including a recorded video answer format, strengths and weaknesses questions, and a director round that required a five-minute technical presentation. Candidates also describe uneven experiences, with one reporting questions that assumed knowledge of Sony's internal culture. Prepare a tight project walkthrough with your reasons for each stack choice, practice timed easy-to-medium coding without references, and review the fundamentals of the language named in your job description.
Synthesized from 11 candidate 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 Sony process.
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 | |
| Size of Joins | |
| Address Schema | |
| Average Quantity | |
| Permutation Palindrome | |
| Integer to Roman | |
| The Brackets Problem | |
| Liked Pages | |
| Employee Salaries (ETL Error) | |
| Twenty Variants | |
| Equivalent Index | |
| Completed Shipments | |
| Paired Products | |
| Detecting ECG Tachycardia Runs |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR call, about 30 minutes in one account. It covers the role and your background. Some calls include questions such as your weaknesses or why you should be hired. One candidate describes an online assignment after this screen, though the format may vary by team.
Candidates describe a conversation with a hiring manager or lead programmer focused on past work, projects and day-to-day expectations. Interviewers may press on design decisions and why you chose a language or stack. Be ready to defend each resume claim and explain trade-offs in detail.
Reported technical content differs widely. Candidates mention an LC299-style problem, water trapping, a timed C programming test, C++ and SQL fundamentals, and React live coding. Expect at least one practical problem, though depth appears to depend on the interviewer and team.
Some candidates report behavioral questions, including a video answer format and strengths and weaknesses prompts. One candidate described a relaxed team conversation and a director round that required a five-minute technical presentation. Outcomes and feedback timing varied between reports.
