In this video, data career coach Kedisha Bryan explains why conventional SQL learning methods—long courses, endless LeetCode problems, and tutorial‑driven practice—don’t translate to success in technical interviews. After failing a mock interview with an Amazon hiring manager, she realized the gap between using SQL in a development environment and solving interview‑style problems. She introduces the "whiteboard method," a three‑part practice framework designed to mimic interview conditions: (1) a "no‑fly zone" where no editor, autocomplete, or AI assistance is allowed; (2) vocalizing your thought process aloud to simulate the interview dialogue; and (3) drafting a plain‑language pseudocode skeleton before writing actual SQL syntax. By separating logical reasoning from syntax, learners can internalize SQL thinking rather than rely on surface‑level recognition. Kedisha argues that practicing under these constraints builds the mental models needed to ace any SQL interview, much like training with weighted gear improves cycling performance. She also addresses the misconception that AI can replace this skill, emphasizing that without a solid logical foundation, AI tools are ineffective. To cement the habit, she proposes a 30‑day challenge where viewers create and solve their own whiteboard SQL problems, optionally using AI for generation and grading. The video concludes with a call to action, inviting viewers to comment, connect on LinkedIn, and consider her coaching services for landing a data analyst role within four months.
Chapters
I got really good at SQL in just a few weeks, and I did almost none of the things everyone else tells you to do. No 50-hour course, no 200 LeetCode problems. I'm going to show you the exact unfair shortcut on my screen right now, and once you see it, you can't unsee it. Here's why you're probably stuck. You've been told the way to learn SQL is to grind through tutorial after tutorial, watch someone else type, and then you'll forget it all by next Tuesday. That is a slow way. It may feel productive, but you can do that for a year and still still fail your technical interviews. So in the next few minutes, I'm going to walk you through the exact unfair strategy, the thing that I did instead of tutorials that made SQL actually stick. It's one core strategy that will take your SQL skills up 10 levels in literally a week. So let's get started. All right, so most aspiring analysts are not that great with SQL, but you have to get good at SQL to land a data analyst job because it is still one of the biggest gatekeepers in interviews. I used to be one of those that was not very good. Then I became so good that I now even teach SQL. So I'm actually going to share with you today the unlock that took me from a SQL noob that was failing mock interviews to acing the interviews and also now teaching SQL. Okay, so the background of this is that I actually did a mock interview with an Amazon hiring manager. Thought I knew SQL at the time, but I pretty much failed it with flying colors. I pretty much exposed the fact that I only knew advanced SQL on the surface level, right? As we all like learn SQL, right? Very easy to get the basics down, like SELECT FROM WHERE, whatever. But once we get into the, you know, more advanced joins and the CTEs and things like that, things slow down, right? So I knew it at the surface level, but in that interview, I was put in an environment that I had never experienced before. And it pretty much exposed all the gaps in my SQL knowledge. And after that, you know, I did feel an embarrassment, but I really wanted to figure out how the heck can I close this huge gap in my SQL knowledge? So one thing that I learned after that day was that using SQL on the job versus passing SQL interview are 2 different things. So whenever we're in an environment like a coding environment where it's, you know, in MySQL and we have like a code editor and we see all the tables and things like that, it's different than when we're tested on the interview. There's going to be different forms of it. Doing SQL like on the interview is a completely different environment. And if we don't create that environment ourselves, we're always going to just bomb on the SQL interviews. Even if we feel comfortable whenever we're taking the courses, again, it's a completely different environment for the interview assessments. And we're never going to pass them unless we learn how to create that environment ourselves. Alright, so the tutorial trap when it comes to SQL, and we've all been there. And this is something that I realized after that failed mock interview, right? I know we've taken, or we've used those SQL practice websites, right? You know, they'll have autocomplete or, you know, we can see what the answer is, right? We'll have errors that will flag real time. We can see the expected output. That's just not how interviews actually work. And we get into this trap of SQL recognition, but not thinking in SQL. So after that failed mock interview, I was like, how can I close the gap and learn how to think in code rather than try to just memorize things, but how can I think in code so that whenever I'm faced with any problem or challenge, I can be able to pretty much have success. And again, this is what pretty much the differences are when it comes down to working always in a SQL editor. We're always, we're just practicing recognition, right? The autocompletes and everything like that. But in a real interview, we have to pretty much practice our thinking in code. And if we don't create the environment before the interview that forces us to think in code, we're never going to pass the interviews. So the unlock is I'm going to teach you how to create that environment or how to force yourself to think in code, think in SQL code, so you can ace any SQL interview. So right now, here's an honest test. In plain English, can you verbally say why you would use a CTE instead of a subquery? Or can you verbally say the differences between the two, why you would choose one over the other, not the syntax, but the actual reasoning. If there was any pause in your answer or you wasn't really sure, you feel like you have to go to ChatGPT or whatever, you already know what I'm going to point at, right? It's not your intelligence, right? We haven't really learned how to think in SQL code yet to just say that in plain English. So the fix is what I call the whiteboard method, right? There's going to be 3 parts to it. There's going to be what I call a no-fly zone. There's going to be voicing out loud and a skeleton before the syntax. The whiteboard method is literally what took me from surface level SQL to knowing how to think in SQL code and being able to ace any assessment. So the whiteboard method is literally what it is in plain English. This is just a screenshot of one of the shorts that I have on my channel where you literally have a Word document or a notepad. You'll have a question, you know, a picture of the tables. And then you literally have to write the code or your SQL code on the Word document. There's no code editor. There's no, you know, database. You literally have just screenshot of tables, a question, and you have to force yourself to write your code on the Word document. That sounds pretty darn scary when you think about it, but I'm going to show you exactly why and how to do it yourself. All right, quick pause. Now, if you want to land your first job in data analytics and avoid the lengthy mistakes that I did, click the link in the pinned comment where you can find the exact steps that my students use to land their job in data analytics without going back to school. All right, now let's get back to it. So the first component of the whiteboard method is the no-fly zone, right? So before your session starts, you gotta commit to nothing external. You know, there's no SQL editor, you can't look stuff up on AI tools, nothing. It's completely on your own, okay? And just a reminder, this is what you do when you're trying to practice. So you don't do this like, you know, when you're, you know, learning first. This is for practicing For the interview. Secondly, right, when you are faced with you know having to you know do the whiteboard questions, right, you voice your thinking out loud. So this part is going to be pretty foreign because whenever we're taking courses or anything like that, we're not talking out loud. But you want to voice your thinking out loud while you are answering the question. This is what you would do in the SQL interview assessment or any interview assessment. Any technical interview assessment, you don't want to be silent. You want to voice your thinking out loud, describe your logic in plain language so the interviewer can understand where you're going, right? Know that you're not lost and can kind of see, you know, what you're thinking. So this part is skeleton for the syntax. So just like previously where I said you want to voice your thinking out loud, you want to basically write out the steps of what the query would be in pseudocode. So plain language, right? So for example, the question says, you know, hey, pull the customers who purchased after June 2024, right? So before you even start on like, oh, I'm going to select from where, just write out in plain language the steps that you're going to do, right? And say that out loud, you know, like, okay, I'm going to need to isolate records from last quarter. I'm going to need to connect to the customer table. If you learn to write in plain language, like pseudocode, it almost also gives you like a navigation because then you're going to translate that into your SQL code, right? So most people just don't do this in general, but rather than just rushing to, okay, let me just get to the SQL code first. No, if you write it in plain language and then convert that plain language into SQL code, it'll make everything so much smoother. So you're not, you know, trying to figure out the logic and the syntax at the same time. You just write the logic first, you solve the logic part First, and then you write the syntax, right? So you don't have to do it at the same time. Okay, so why this works is the goal is not about the problem that you solve; it's about the conditions of which you solve them, right? Again, people who are professional cyclists, right? They're not practicing with training wheels. You're not going to win the Tour de France if you're practicing with training wheels. So again, it's about the conditions that you're under. So in order to pass interviews. Right? Technical interviews. You need to create those conditions yourself and practice under those conditions. You don't wait till the interview to be under those conditions for the first time, right? That's where overwhelm comes. Learn how to— you practice how you play. That is what the whiteboard method is about. Now, some of you may be saying that, oh, maybe you've done interviews and you've never seen this before. The great thing is, if you can do whiteboard SQL, you can pretty much do anything. It's almost like running with a weighted vest. It'll be easier once you take it off. But if you can do whiteboard SQL, any SQL interview is going to be easy. That is the point. That is a huge point of it. Now, some of you may be thinking, okay, well, AI writes SQL now. AI gets stuff wrong. Okay, AI gets stuff wrong and you still need to be able to direct the AI. Okay, AI is not going to know the right questions to ask or anything like that. AI can maybe make things easier, but it's not going to do the work for you. Okay, so remember that if you don't know the right logic, To tell the AI or to instruct the AI or whatever it is, then AI is no good use to you. That's why you still need to know the logic. Okay, so your 30-day challenge is I want you to create your own whiteboard SQL challenges. If you can do whiteboard SQL, I'm telling you, you're going to be able to pass any SQL interview. You can use AI to create your own, right? You can use AI to also grade it for you. This will force you to learn how to think in code so that whatever challenge On an interview that you ever get, it's going to be easy peasy. Absolutely. All right. So listen, you got the unlock. Go do this right now. Okay. Go do this right now. And please drop a comment on the biggest takeaways and also even DM me on LinkedIn if this helped you a lot. All right. Now, again, I'm Kedisha, data career coach. If you ever want to work with me to land your first role in data in under 4 months, the link is in the description. I'd love to coach you. I'll see you in the next video.
