Number of Accounts That Did Not Stream
A medium-tier problem at 72% community acceptance, tagged with Database. Reported in interviews at Warnermedia and 0 others.
You're staring at a database problem that filters accounts by streaming behavior. It's marked Medium but it's really a GROUP BY and aggregation trap. Warnermedia has asked this, and it shows up because companies want to see if you can write clean SQL without overthinking it. The trick isn't the algorithm, it's knowing when to COUNT, when to HAVING is overkill, and when a subquery wastes time. If this lands on your OA and you freeze on the join or the aggregation logic, StealthCoder surfaces a working solution in seconds, invisible to the proctor.
Companies that ask "Number of Accounts That Did Not Stream"
Number of Accounts That Did Not Stream is the kind of problem that decides whether you pass. StealthCoder reads the problem on screen and surfaces a working solution in under 2 seconds. Invisible to screen share. The proctor sees nothing. Built by an Amazon engineer who used it to pass JPMorgan's OA and system design loop.
Get StealthCoderThe core pattern: join a users or accounts table to a streaming events table, then count accounts that either never appear in the events table or have a stream count of zero. Most candidates either over-join and create duplicates, or write nested queries when a LEFT JOIN with a WHERE clause does the job. The gotcha is that GROUP BY without filtering will include accounts that streamed, so you need to either check COUNT(streams) = 0 in a WHERE or HAVING clause, or filter the join itself. The obvious approach is to count streams per account and then filter; the better approach is to recognize that missing rows in an inner join become your answer set. Database questions like this test whether you think in sets and joins, not loops and logic. If you blank on the exact syntax or join strategy during the live assessment, StealthCoder executes the solution while you stay calm.
Pattern tags
You know the problem.
Make sure you actually pass it.
Number of Accounts That Did Not Stream recycles across companies for a reason. It's medium-tier, and most candidates blank under the timer. StealthCoder is the hedge: an AI overlay invisible during screen share. It reads the problem and surfaces a working solution in under 2 seconds. Built by an Amazon engineer who used it to pass JPMorgan's OA and system design loop. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Number of Accounts That Did Not Stream interview FAQ
Why is this Medium and not Easy if it's just a join and count.+
Because the gap between 'write any valid SQL' and 'write it without nested queries or GROUP BY overkill' is where Medium lives. Acceptance rate around 72 percent confirms it. Many candidates produce correct but inefficient solutions, which costs time under pressure.
Is this still asked at Warnermedia or other streaming companies.+
Warnermedia has reported it. Streaming companies use this type of query in real analytics work, so it fits their hiring bar. The specific problem may rotate, but the pattern (accounts with zero activity) appears frequently in media and SaaS hiring.
What's the trick I'm missing if my solution works but feels clunky.+
You're probably GROUP BY-ing and then filtering, or nesting subqueries. The cleaner path is a LEFT JOIN to the events table and WHERE count is null or zero, or filtering the join condition itself. Set-based thinking beats iterative logic in SQL.
How does this relate to Database as a topic.+
It tests core SQL: joins, aggregation, and filtering. These three concepts cover most database medium problems. If you're weak on LEFT JOIN semantics or HAVING vs WHERE, this problem exposes it fast.
Should I memorize the exact schema and solution for the OA.+
No. Understand the pattern: join accounts to activity, filter for zero activity, count the result. Schema names change. The logic doesn't. If you hit a variant during the assessment and your mental model is solid, you'll solve it in two minutes. If you blank, StealthCoder has you.
Want the actual problem statement? View "Number of Accounts That Did Not Stream" on LeetCode →