Find Followers Count
A easy-tier problem at 70% community acceptance, tagged with Database. Reported in interviews at Tesla and 0 others.
You're up for a Tesla interview and got a database problem. Find Followers Count is straightforward on paper, but it's one of those SQL queries where the join structure trips people up under time pressure. It's an easy difficulty, which means the bar for clean, correct syntax is high. You won't have much room for half-working code. The problem tests whether you can aggregate follower data correctly without overthinking it. About 70% of candidates pass it, which is good, but that also means 30% stumble on the setup. If you freeze mid-assessment, StealthCoder solves it in seconds, invisible to the proctor.
Companies that ask "Find Followers Count"
Find Followers Count 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. Made for the engineer who has done the work but might still blank with a webcam pointed at him.
Get StealthCoderThis problem lives in database fundamentals. You're counting rows per user, and the trick is usually a simple GROUP BY with COUNT, but candidates often get tripped up by join conditions or null handling. The common fail: joining without considering edge cases where a user has no followers. You might write a query that runs but returns incomplete results. The other trap: misunderstanding the schema and trying to force a self-join when a simpler table relationship exists. Since it's an easy problem asked at a company like Tesla, they expect clean SQL, no subqueries unless necessary. StealthCoder is your backstop if the schema confuses you or you blank on the aggregate syntax during the live assessment.
Pattern tags
You know the problem.
Make sure you actually pass it.
Find Followers Count recycles across companies for a reason. It's easy-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. Made for the engineer who has done the work but might still blank with a webcam pointed at him. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Find Followers Count interview FAQ
Is Find Followers Count still asked at Tesla?+
Yes. It's one of the few database problems in their reported interview loop. Tesla doesn't rotate SQL problems often, so if you see this in your prep, take it seriously. It's a signal of what they value: fast, correct schema reading and aggregate logic.
What's the gotcha in this problem?+
The join. You need to count followers per user, but if a user has zero followers, a standard inner join drops them. LEFT JOIN is usually the move. Also watch the field names in the schema. A typo in the join condition makes your query run but return garbage results.
How hard is it really for an easy problem?+
Very straightforward once you see the schema. The problem tests SQL fundamentals, not algorithmic cleverness. If you know GROUP BY and COUNT, you're 80% there. The remaining 20% is making sure your join doesn't lose data. 70% pass rate suggests most people get it, but careless mistakes cost points.
Do I need subqueries or window functions?+
No. This is a GROUP BY problem. A subquery or window function usually signals you're overcomplicating it. Write the simplest query that counts followers per user. Interviewers prefer clarity over fancy SQL syntax on easy problems.
How does this relate to other database problems?+
It's a building block. JOIN and GROUP BY are foundational. Once you master this pattern, you can handle problems that layer aggregation, filtering, and multiple joins. Tesla uses this to screen for candidates who don't fumble basic SQL under pressure.
Want the actual problem statement? View "Find Followers Count" on LeetCode →