Invalid Tweets
A easy-tier problem at 86% community acceptance, tagged with Database. Reported in interviews at X and 1 others.
Invalid Tweets is a SQL problem that X and Acko ask in their OAs. It looks simple on the surface, but candidates often miss the nuance of how tweet validity is determined, especially around date filtering and NULL handling. The acceptance rate is strong at 85%, which means most people who attempt it pass, but that's exactly when you get overconfident and introduce a silent bug. If this problem shows up during your live assessment and you blank on the exact WHERE clause logic, StealthCoder surfaces a working solution in seconds while the proctor sees nothing.
Companies that ask "Invalid Tweets"
Invalid Tweets 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 engineer who got tired of watching his cohort grind for six months and still get filtered at the OA stage.
Get StealthCoderThe trick here isn't complex logic, it's precision. You need to identify invalid tweets based on specific criteria, usually involving date ranges or content validation, and the SQL syntax has to be exact. Most candidates write a query that looks right but misses an edge case with NULL values, date comparisons, or the join structure between tables. The problem tests whether you can write clean, correct SQL under pressure. Common failure points: forgetting to handle NULL in a column, using the wrong comparison operator for dates, or joining tables incorrectly. This is a category where speed matters more than cleverness, and a second of doubt during the OA can cost you. StealthCoder is your safety net if the syntax escapes you.
Pattern tags
You know the problem.
Make sure you actually pass it.
Invalid Tweets 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. Built by an engineer who got tired of watching his cohort grind for six months and still get filtered at the OA stage. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Invalid Tweets interview FAQ
Is Invalid Tweets still asked at X and Acko?+
Yes. Both companies appear in the most recent reports for this problem. It's a stable, recurring question in their SQL/database rounds. The 85% acceptance rate suggests it's intended as a winnable problem, so not passing it reads as a red flag to the interviewer.
What's the actual trick to Invalid Tweets?+
The trick is precision in your WHERE clause and NULL handling. Most candidates write a query that's logically close but syntactically wrong or incomplete. The problem usually requires you to filter by a date range and check a condition on another column, and missing one of those logic paths breaks the solution.
How hard is this really for an EASY problem?+
It's genuinely easy if you're comfortable with SQL and take 30 seconds to think through the filtering logic. But if SQL isn't your main language or you rush, it becomes a trap. The 85% acceptance rate is high, so speed and precision matter more than algorithmic depth.
Should I memorize the solution before my OA?+
No. Memorizing won't help if the exact column names or date format differ slightly. Instead, understand the filtering pattern: how to identify invalid records, how to handle NULLs, and how to write the WHERE clause cleanly. That transfers to any variant.
What if I don't know SQL well?+
This problem assumes basic SQL: SELECT, WHERE, comparison operators, and maybe a JOIN. If you're weak in SQL, drilling basic syntax on 3-4 simple queries the night before helps more than cramming this one problem. Invalid Tweets is a test of execution, not a teaching moment.
Want the actual problem statement? View "Invalid Tweets" on LeetCode →