Zoom coding interview
questions, leaked.
3 problems reported across recent Zoom interviews. Top patterns: database, array, two pointers. The list below is what most reported candidates actually saw, plus the honest play if you can't grind all of it.
Zoom's coding interview is lean and direct. You're looking at three problems total, and the data is clear: database queries dominate. Two of the three are database problems, both Easy, and they're variants of the same pattern, filtering user activity by a 30-day window. The third problem bridges array manipulation with greedy logic. This isn't a gauntlet. It's a focused test of whether you can write clean SQL and handle a medium-difficulty two-pointer problem. If you blank on the medium during the live assessment, StealthCoder runs invisibly and surfaces a working solution while the proctor sees only your screen.
Top problems at Zoom
| # | Problem | Diff | Frequency | Pass % | Patterns |
|---|---|---|---|---|---|
| 01 | User Activity for the Past 30 Days I | EASY | 100.0 | 49% | Database |
| 02 | User Activity for the Past 30 Days II | EASY | 100.0 | 36% | Database |
| 03 | Container With Most Water | MEDIUM | 66.0 | 58% | Array · Two Pointers · Greedy |
Frequencies derived from public community-tagged interview reports. Click a row to view on LeetCode.
You have a week, maybe less. You can't out-grind the list above. StealthCoder runs invisibly during the actual Zoom OA. The proctor cannot see it. Screen share cannot detect it. Built by an Amazon engineer who used it to pass JPMorgan's OA and system design loop.
Get StealthCoder- database2 · 67%
- array1 · 33%
- two pointers1 · 33%
- greedy1 · 33%
Database work is the anchor here. Two Easy problems asking you to query user activity data means Zoom expects fluency with SQL filters, date logic, and table joins. Don't skip these thinking they're trivial. Easy doesn't mean the test is easy, it means the pattern is familiar to anyone who's done database work at scale. The medium problem, Container With Most Water, tests whether you can apply two-pointer logic under greedy constraints. It's a classic that trips people up when they're tired. Your prep sequence is straightforward: lock down SQL date filtering and aggregation first, then solve the array problem a few times until the two-pointer scan feels automatic. StealthCoder is your hedge if the medium problem's constraint throws you mid-interview.
Companies with similar patterns
If you prepped for Zoom, these companies recycle ~60% of the same topics.
You've seen the list.
Now make sure you pass Zoom.
Memorizing every problem above in a week is a fantasy. StealthCoder is the hedge: an AI overlay that's invisible during screen share. It reads the problem on screen 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.
Zoom interview FAQ
How much SQL should I study for Zoom's interview?+
Two of three problems are database-heavy, so SQL competency is non-negotiable. Focus on WHERE clauses, date filtering, aggregation functions, and simple joins. The problems use a 30-day window, so practice DATEDIFF or equivalent date arithmetic in your target database system. One medium problem won't save you if you flub the SQL.
Is Container With Most Water the only algorithmic problem I'll see?+
From reported problems, yes, one medium, no hard problems. But don't coast on that. The two-pointer greedy approach appears in many Zoom follow-ups, and the logic is tricky under pressure. Solve it cold at least twice before your OA.
What should I prioritize: SQL or arrays first?+
SQL first. Two out of three problems live there, and database competency signals seniority to Zoom. Arrays and greedy logic are things you can brush up in a day or two. SQL mistakes kill your score faster because they're harder to debug in a timed setting.
Are the two User Activity problems identical or different?+
They're variants of the same pattern. Version I and II likely test the same filtering logic with slight twists, maybe different aggregations or edge cases. Solving one deeply will cover both; don't treat them as separate studies.
How long should I spend on prep if my OA is in a week?+
Three problems and a heavy database focus means you can be ready in 5 to 7 days. Spend 2 to 3 days on SQL date queries and joins, 1 day on the medium problem, then run 2 to 3 full mock rounds. Zoom's small problem set is actually your advantage. Use it.