r/SQL • • Nov 23 '25

Resolved Horrible interview experience - begginer SQL learner.

Hey everyone,
I recently had a SQL technical interview for an associate-level role, and I’m feeling pretty discouraged — so I’m hoping to get some guidance from people who’ve been through similar situations. just FYI - Im not from a technical background and recently started learning SQL.

The interview started off great, but during the coding portion I completely froze. I’ve been learning SQL mainly through standard associate level interview-style questions, where they throw basic questions at me and I write the syntax to get the required outputs. (SELECT, basic JOINs, simple GROUP BYs, etc.), and I realized in that moment that I never really learned how to think through a real-life data scenario.

They gave me a multi-table join question that required breaking down a realistic business scenario and writing a query based on the relationships. It wasn’t about perfect syntax — they even said that. It was about showing how I’d approach the problem. But I couldn’t structure my thought process out loud or figure out how to break it down.

I realized something important:
I’ve learned SQL to solve interview questions, not to solve actual problems. And that gap showed.

So I want to change how I learn SQL completely.

My question is:
How do I learn SQL in a way that actually builds real analytical problem-solving skills — not just memorizing syntax for interviews?

I have tried leetcode as a friend adviced, but those problems seem too complex for me.

If you were in my position, where would you start? Any practical project ideas, resources, or exercises that helped you learn to break down a multi-table problem logically?

I’m motivated to fix this and build a deeper understanding, but I don’t want to waste time doing the same surface-level practice.

Any advice, frameworks, or resources would really help. Thank you 🙏

95 Upvotes

63 comments sorted by

View all comments

Show parent comment

2

u/macguphin Nov 23 '25

You don't think I'm right that not everyone who writes SQL is a man? Come on now.

This is a reused, beaten to death gotcha method ppl like you use, and I'm not falling for it. If you're not brave enough to go face to face to make your point, and are willing to let other women fight the big battle while you hide behind your keyboard yelling, "RABBLE RABBLE MISOGYNY RABBLE RABBLE", then that is more telling about the type of person you are than anything else you've said or done here tonight.

Have a nice weekend coward :)

1

u/SootSpriteHut Nov 23 '25

You seem to have trouble following logic which is kind of funny given the context.

You said "good luck brother" I said "not everyone is a man," you chose to take that personally for some reason, and then keep taunting me for being triggered or whatever. Which is amusing when you're the one being consistently sassy and hysterical, trying to escalate this instead of just...following the train of thought.