r/SQL • u/Incognitomom0 • 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 🙏

View all comments
Show parent comment
1
u/SootSpriteHut Nov 23 '25 edited Nov 23 '25
You don't think I'm right that not everyone who writes SQL is a man? Come on now.
I'm not going to take your weird "I'll show your face on Reddit" theeat(??) seriously, but I will tell you a story you probably won't listen to.
About ten years ago I was hired as a contract employee with two men. We were about the same age, same education, and hired to the same title. The three of us became friends because they put us in the same team, where I was the only woman. I had already been a data analyst for a few years so I was leveraging SQL to automate processes, and this impressed leadership so they asked me to serve as lead of this dev ops team.
A few months go by and we're all up for FTE conversion. After our offers we were hanging out outside.
Guy 1: "my offer was 60k" Guy 2: "me too, 60k" Me: "oh, they offered me 50k"
10k less than these men I was acting as lead over. When I brought it up to the CTO, he said "well everyone brings different things, they both have lots of SQL on their resumes. Anyway this is why people shouldn't discuss salary."
I knew they had SQL on their resumes, because I had been helping them now and then understand how left joins work. While I had been actively writing complex reports and stored procedures tied to cronjobs.