Sony Data Analyst interview typically runs 3 rounds: HR screen, online interview, in-person interview. The process takes about 2 months and is more practical and specialized than a standard analyst interview.
$72K
Avg. Base Comp
$135K
Avg. Total Comp
3
Typical Rounds
2 months
Process Length
Our candidates report that Sony is looking for more than someone who can summarize metrics cleanly. The strongest signal in the experience we saw was the deep dive into a past project: not just what was built, but how it progressed and what conclusion was drawn from the results. That tells us Sony cares about end-to-end reasoning and whether you can connect analysis to a real business or product outcome, not just produce a polished report.
A recurring theme is the company’s comfort with adjacent technical depth. Even for a Data Analyst role, candidates were asked about simple Python, data and ML operations, and broader AI topics like LLMs, deployment, and Gen AI. That suggests Sony values analysts who can operate near modern data workflows and speak the language of technical teams. We’ve also seen a clear emphasis on messy, incomplete, or conflicting data — the kind of question that reveals how you make judgment calls when the data is imperfect. In our view, that’s the non-obvious bar here: they want practical analysts who can explain tradeoffs clearly and stay grounded when the data doesn’t behave neatly.
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 Sony process.
After I submitted my resume through the JobsDB application, HR called me first to ask about my background and a few specific questions. Once I passed that screening, I was invited to an online interview, and that part felt more focused on my actual experience than on generic interview questions. They asked me to walk through one of my projects step by step, including how it progressed and what conclusion I reached from the results. The conversation also went into data and ML operations, which I wasn’t expecting as much for a Data Analyst role. I was asked to write some simple Python code, and there were questions around AI and ML models, including LLMs, deployment, and how Gen AI is used. It felt more practical than theoretical, but it definitely leaned toward people who have some exposure to ML workflows rather than just reporting and dashboards.
The later stage was smoother and more conversational. The interviewer was friendly, and the questions were pretty much what I would expect at this level. That round was in person at their Weybridge office, and the whole process took about two months from start to finish. One question that stood out was about a situation where I had to deal with messy, incomplete, or conflicting data, so I’d say they care a lot about how you think through real-world data issues and explain your reasoning clearly. Overall, the process felt fair, but the combination of project deep-dives, basic Python, and ML/Gen AI topics made it more specialized than a standard analyst interview. My main takeaway is to be ready to explain your projects end to end and to speak comfortably about how you handle imperfect data and basic ML concepts.
Prep tip from this candidate
Be ready to explain one project end to end, including the final result and how you got there, because they asked for a step-by-step walkthrough rather than high-level summaries. Also practice a simple Python coding exercise and be prepared to discuss messy or conflicting data, plus basic ML/LLM deployment and Gen AI usage.
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 | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Button AB Test | |
| Compute Deviation | |
| Prime to N | |
| Paired Products | |
| P-value to a Layman | |
| Random SQL Sample | |
| Upsell Transactions | |
| Raining in Seattle | |
| Decreasing Comments | |
| Hurdles In Data Projects | |
| Bank Fraud Model | |
| Popular Actions | |
| Identifying User Sessions | |
| Average Quantity | |
| Exam Scores | |
| Liked Pages | |
| Network Experiment Design | |
| Google Maps Improvement | |
| Completed Shipments | |
| Digital Library Borrowing Metrics | |
| Revenue Retention | |
| Reducing Error Margin | |
| Detecting ECG Tachycardia Runs | |
| Group Success | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
After submitting a resume through JobsDB, HR called to ask about the candidate’s background and a few specific screening questions. This first step was used to confirm fit before moving to the interview rounds.
The next round was an online interview focused on the candidate’s actual experience rather than generic questions. The interviewer asked for a step-by-step walkthrough of a project, including how it progressed and what conclusions were drawn, and also covered data and ML operations, basic Python coding, and questions on AI/ML models, LLMs, deployment, and Gen AI.
The later stage was an in-person conversation at Sony’s Weybridge office. It was described as smoother and more conversational, with questions centered on standard analyst-level topics such as handling messy, incomplete, or conflicting data and explaining reasoning clearly.