What an SQL interview is like - SQL Tutorial

- [Instructor] So you've been studying and working with databases using your preferred server, whether it's MySQL or Microsoft SQL Server, and you feel pretty confident walking into the interview. Your code is solid. You've practiced. But wait, there's no computer waiting for you, just a pen and a piece of paper. What do you do? This may seem odd, but most SQL interviews I've had have been paper and pen or an interviewer asking me questions. It can catch you off guard, even if you prepared and reviewed thoroughly. The good news is you'll be able to prepare yourself with four simple steps. There's no particular order, but I think they are good instructions to build a base for your study routine. Step one, study your terminology. This isn't just limited to what we covered previously, but really get curious about what it all means. How does this greater concept fit together? There's no worse feeling to me than knowing how to do something practically but not knowing how to articulate what it means. Doing this before the interview will ensure that you come into the room with confidence and with a good direction. You may not always answer the question 100% correctly. But if an interviewer can follow your train of thought, you'll be on the right track. There are several options for where to find reliable information, whether that's in a book or on the internet for free. The two points I'd focus on is is my definition clear, and could I provide a clear example if asked. Step two, comment, comment, comment. Get used to commenting your steps while working. We will delve into this in our practical example. Documenting what you're doing while you're doing it may seem unnecessary at the time. But when you're not able to work with software that will give you error messages and intelligence, it'll come in handy. Remember, it's not about getting it right once. It's about not being able to get it wrong. So some things to think about in this section. Could I reproduce this verbally? Do I understand why I'm doing what I'm doing? Step three, find your good enough. No, I'm not advocating for mediocrity. But if you want to prepare for every eventuality before you get started, you may never get started. Start small, know it inside and out, then make small progressions. You don't need to be a SQL master overnight, just open and willing to be a continuous learner. A common mistake we make when learning anything is that we want to learn everything because we are interested and excited. Excitement and interests are wonderful, but they can quickly lead to being overwhelmed with the sheer amount of information that there is to learn and increase pressure to be perfect before getting yourself out there. A few points to think about. Do I have a solid foundation? Do I know where to go to learn more? Is this integral to the position I am seeking? Step four, ask for clarification. Don't be too proud to ask for clarification. Maybe something isn't worded clearly or you don't fully understand what the interviewer is asking of you. And this will happen. Ask follow-up questions or clarifying questions that will help you put your best foot forward. Ask yourself, do I understand the question entirely? Do I have enough information to give a clear and cohesive answer? If the answer to any of those is no, please ask for clarification. So thank you for embarking on this journey toward a successful interview. I wish you the best of luck.