Did the Sony SWE loop earlier this year while employed, interviewing on lunch breaks and after hours. Here's the full coding breakdown so someone else doesn't have to piece it together from 4-year-old glassdoor posts.
Online assessment (OA): Two coding problems on HackerRank, 90 minutes. No proctoring (at least for my role). Problems were mid-difficulty. Think: graph traversal and a sliding window array problem. Not hard by competitive-programming standards. If you can comfortably do LeetCode medium you should be fine. I'd say difficulty is similar to the easier end of Amazon OAs.
Phone screen coding: One question, about 40 minutes to solve plus 15 minutes of discussion. I got a problem about tree serialization. They were more interested in my thought process and edge case handling than getting a fully optimized solution. I over-explained and it worked fine.
Onsite coding (two rounds): Each 45 minutes. I had: Round 1: String manipulation + a follow-up about optimizing space complexity Round 2: Graph problem (shortest path variant, nothing exotic)
Neither round was LeetCode hard territory. The interviewers I had were pretty relaxed. One of them said outright that they care more about clarity than speed.
One thing: they do care about test cases. Walking through examples and catching your own edge cases before submitting matters. I saw them note something when I proactively added a null-input check.
For context, I was interviewing for a backend SWE role, mid-to-senior level. Consumer electronics side, not SIE (PlayStation). Different division probably has a slightly different bar.