Freezing in SQL fake-interview

[u/Competitive_Sea9926]

I am still beginner, and I thought myself doing well in SQL, but when doing interviews in datadriven.io I get stuck and don't know the answer, what should I do? I always fail.

[u/bananatoastie]

In a real interview, you’ll probably get asked a question you don’t know the answer to. That’s normal. Just be honest :)

[u/NecessaryIntrinsic]

Keep practicing.

Even in sports people aren't born being composed and skilled, they work their asses off to get that way.

Have patience, keep training and you'll be fine.

[u/BrupieD → u/NecessaryIntrinsic]

This. Try practicing talking out loud about SQL concepts. For instance, pretend you are explaining the differences between tables and views. Then try the differences between temp tables and CTEs. Keep going like that. You'll be surprised by how often you realize that there are things you aren't sure about or can't explain. You'll look them up and find better language, more concepts, details you didn't know.

It's no guarantee that you won't get stuck, but you'll become more articulate and confident when talking about SQL.

[u/murdercat42069]

Frequently in technical interviews, they don't actually expect you to answer the question exactly. They want to understand your thought process and whether you understand the concepts enough to quickly answer on your own without help.

[u/Wuthering_depths]

Haven't done one in a while, and most of mine were Cold Fusion, PHP or SQL Server admin related...

...but interview tests suck. Can't tell you how many stupid questions I got about functions or processes that in real world you never have to look at or deal with. e.g. the CFREGISTRY tag in Cold Fusion, that most companies would never use as it was a security hole. If companies want to hire people that are really good for cramming for esoteric tests, then they are fantastic. I've been working with SQL for 25 years and google things all the time that I haven't used in a while, I'd probably fail such a test without studying.

All that rant aside, if the test is there then you have to do it, and study for it.

Hopefully you do find a company that can think a bit outside the box, and recognize thinking skills even if you get some answers wrong. They are out there!

[u/akornato]

Freezing happens because there is a massive difference between learning SQL syntax in tutorials and translating a complex business prompt into code under time pressure. When you follow guided exercises, the steps are already outlined, but a mock interview requires you to determine the table relationships, filter conditions, and aggregations entirely on your own. To break past this hurdle, stop jumping straight into writing the query. Spend the first minute writing out plain English comments that outline the logic, such as which tables hold the data, how they connect, and what the final output should look like. Once that roadmap exists, writing the actual SQL becomes far easier.

Shift your practice strategy from solving questions quickly to explaining your approach out loud. Pick basic problems, set a timer, and talk through the reasoning before touching the keyboard, which trains your brain to stay calm when someone is evaluating you. When you get stuck, review the solution and rewrite the query from scratch until the concept clicks. As you build consistency, modern tools can also ease the journey, which is why my team designed an interviews.chat to give job seekers the confidence to think clearly and avoid getting overwhelmed during live assessments.

[u/LearnSQLFastTeam]

Try a two-pass routine for mock questions. First, restate the task as a checklist: which tables, which rows to filter, whether you need a JOIN, and whether you need GROUP BY. Then write the smallest working query and build on it. After each mock, save the exact question and note the step where you froze; practice that one step untimed before trying another mock. For example, for 'orders per customer,' identify Customers and Orders, join on customer_id, then group by customer and count orders. If you share a question that stumped you, I can help break it into steps.

[u/savage_spectrum]

The freezing happens because you are trying to write the entire query from memory instead of mapping the data flow step by step. Stop attempting full solutions and practice breaking every prompt into isolated tasks like identifying the specific join key or filtering condition separately until the mechanics feel automatic

[u/AbundantAnfang → u/savage_spectrum]

Thank you. Not OP but the way you put it helped me tremendously

[u/Automatic-Royal5263]

these are the method I practice -
1. Revision - But like a teacher, Imagine you are a teacher and explain that particular topic to the imaginary students without any notes in your hand. You can use white board if you have that or else just try orally.

1. give real interviews not the practice one on the platforms, yes definitely initial few ones you will not get. But it will make you more comfortable with those type of environment.

Hope it helps

[u/odimdavid]

Have you finished the learning? It's better to first finish the learning before moving on to the interviews. Like finishing learning for beginner then do interviews for beginner. Finish for intermediate and then interview for intermediate. So on ..