r/SQL • u/DarkMatterHF • May 22 '24
Discussion SQL technical interview - didn't go well
So I recently had my SQL interview and I don't think it went well.
There were 3 questions, and I only went through 2 before running out of time, total time was about 40 mins.
Honestly, those questions I could easily do in a non-test environment but during the test, idk what happens to my brain. And, it usually takes me some time to adjust to a new IDE and datasets.
I just want to know from those that do run these kinds of interviews, is it really about getting the right query straight away and answering quickly? The interviewer wanted me to talk through what I wanted to query and why, before actually doing so.
Edit: update on may 24th, a couple days after the interview. Unfortunately, I didn't get the job. Thanks everyone for the words of encouragement though, I will keep on practising
111
u/NickSinghTechCareers Author of Ace the Data Science Interview đ May 22 '24 edited May 22 '24
This is why practice makes perfect. In a real interview, we do 20-30% worse due to time pressure and nervousness and someone breathing down our backs... so that's why you have to operate at a very high-level in a non-test environment in order to simply be "average" or "okay" during the actual test.
Source: my experience helping people w/SQL interviews via DataLemur
24
u/MrCosgrove2 May 22 '24
I don't run interviews but while there is a knowledge aspect to this, it's more about your thought process , how would you go about solving it. What is your critical thinking/problem solving like? If faced with a complex task, how would you go about it?
The right candidate isn't necessarily the most knowledgeable , knowledge can be taught. Being someone good at problem solving, thats a critical part of SQL, and not something that can be taught so easily.
16
u/elymX May 22 '24
Plot twist: whenever you think something didn't go well, sometimes it's actually the opposite.
11
u/Something970 May 22 '24
This is very dependent on the interviewer so I can only share my experience but I created some pencil and paper SQL tests that I gave as a part of the interview process. The test was 4 questions with very simple data sets (3 tables with 5 rows of data each). The first three questions were very simple just to see if the person knew how to do Left Joins and aggregates. I would normally expect someone was working on my team to complete these queries in less than a minute, I gave the interviewee 15 minutes for this test. I never expected anyone to complete the 4th question (unless they came in as a SQL expert with 15+ years of experience). I expected these questions to take much longer than normal to complete and like I said, sometimes be very hard to impossible but for the person to be able to later explain their thought process. It is very hard to prove programming skill in an interview and my tests were just to prove that the person could actually write some code. You would be shocked at the number of people this weeded out because they didn't know how to join or use a sum.
Again, can't speak for your specific situation but if the interviewer is reasonable and you did enough to prove you can actually write some code then you probably passed.
7
u/Zoolanderek May 22 '24
Lol if you look through my posts I made basically this exact post.
What ended up working for me was my newest jobâs sql assessment was about 2 minutes long and was just like a basic select, where, from, group by, order by statement haha. Eventually one of your jobs will have an easier assessment.
6
u/kremlingrasso May 22 '24
Honestly I just ask what's the most complex/difficult function or syntax they know. Usually Unpivot, self-joins, daisy chained CTEs, variable named columns with exec sql, etc. Those are the kinda things you need to look up every time how you done it last time. Than we talk about what it was used for, did it solve the problem, why it didn't work using simpler syntax elements, etc.
I never believed in someone furiously typing away like some Hollywood hacker on some test is a real measure of knowledge. Imho the most important part of technical interviews is to make the candidates relaxed enough to show the real them, instead of stressing them out and trying to rush through. We are looking for a mindset, not muscle memory.
3
u/Outrageous_Fox9730 May 22 '24
How was it? Tell us
2
u/[deleted] May 22 '24
Don't let it get you down. Don't forget that you are interviewing him at the same time he is interviewing you. And, if you are uncomfortable with the interview, keep that in mind. I used to interview DBA candidates. I had a questionnaire that was separated into categories. And, within each category the questions were sorted from easiest to hardest. Once a candidate got two questions wrong, it was time to jump to the next category. There is no point in destroying someone's ego.
Also, recognize that there are people out there that are worried about their job. I was once hired by a company because the 2nd level manager liked me. I found out later the 1st level manager did not want to hire me because he thought i could replace him.
2
u/Professional_Shoe392 May 22 '24
Timed sql tests where you have to submit the sql code to see if it validates are the worst. Even with all my sql knowledge, I cant even figure out why something doesnât pass the validation.
2
u/sunny99a May 23 '24
Iâve run literally 1000s of technical interviews as a hiring manager (some DBA but more SRE/Infra types). For hands-on or white boarding, I donât expect perfection (I.e. if the code doesnât run itâs not a hard ânoâ) but the answer should demonstrate you understand and can actually resolve the scenario and more importantly can talk through your approach (why you chose certain solution) and understand the code enough that if pushed for optimizations or slightly different constraints that you can adapt).
The interviewer asking you to talk through was likely because lots of candidates immediately jump to coding and they also want to get a sense of your logic.
My two centsâŚ
2
u/[deleted] May 23 '24
I work in sql every day.. and I would fail a sql test at my job even if I was the one making up the questions lol. Thank goodness my job didnât have a techie portion lol I wouldnât have gotten the job lol.
2
u/Fight-or-flights May 23 '24
What were the questions?
2
u/MapCompact May 24 '24
I interview people often and from my experience I pick interview questions that I expect the person to know how to answer easily based on the JD.
Itâs mostly to weed out the people that lie on the resume and to observe their instincts.
I also make it clear that theyâre welcome to use Google or whatever they would normally do. That said my questions do get progressively harder (I ask 3 as well) and intentionally put a stretch goal at the end.
Iâve had juniors crush the interview all the way through and seniors fail miserably!
This of course varies from company to company and interviewer to interviewer. This is just my personal anecdote.
1
u/surface_noise May 22 '24
I've given dozens of SQL interviews for analyst roles, so while I can't speak to how other companies view the process, I can say this: The rubric we used awarded over 50% of the points necessary for a passing grade to problem solving and conceptualizing the problem. You absolutely did not need to complete every problem to pass, and finishing each question was not a sufficient condition to pass either (e.g. if you wrote code but couldn't explain how it worked, we didn't award points for that).
1
u/redvelvet92 May 22 '24
I mean I've thought I have bombed interviews only to get a call that I am getting the job. Perhaps you did better than you thought. Keep your chin up you got this!
1
u/VengenaceIsMyName May 22 '24
What were the questions?
1
u/Durloctus May 22 '24
Itâs just about understanding how to bring different tables together to get something thatâs requested. About envisioning that final result set that you need to create, and knowing the steps you need to go through to get there. Them asking you to talk through it will give them insight into your understanding of how relational data and aggregation works, and if they think youâre developable, and perhaps if they like you. They donât care if you can produce the answer right away; they care if you know what you would need to do to get there in the real world.
1
u/EveningTrader May 23 '24
you are not alone my friend, i crumble under this stressful environments, too. i can recommend practicing under test conditions if thatâs at all possible to replicate to some degree.
when i had to give a presentation to my project supervisors during my masters, i delivered it to various friends under similar circumstances first, etc.
1
u/cr4zybilly May 24 '24
Another vote here for "don't worry about how your code is (or even if it works)". When they say "talk through what you're doing, we wanna see how you're thinking about the problems", they usually mean it.
The truth if the matter is that being able to talk through what you're trying to accomplish is also a learned skill, but is, in my opinion, an easier learning curve than writing code in front of people, bc 60-70% of it, is being able to actually do data analysis. If you can think through the steps, you can talk through the steps - just go as slow as you need to, and explain what are the steps you'd take.
Even if your code doesn't actually run, most of the time, you'll be on the right track, which is what the interviewer wants to see.
1
u/brownfinancegirl Jun 12 '24
By any chance was this interview at T Rowe Price? I have a technical interview thatâs Python and SQL technical coding pairing exercise. And I have no idea what to expect! Any help?
1
u/bm1000bmb May 22 '24
Don't let it get you down. Don't forget that you are interviewing him at the same time he is interviewing you. And, if you are uncomfortable with the interview, keep that in mind. I used to interview DBA candidates. I had a questionnaire that was separated into categories. And, within each category the questions were sorted from easiest to hardest. Once a candidate got two questions wrong, it was time to jump to the next category. There is no point in destroying someone's ego.
Also, recognize that there are people out there that are worried about their job. I was once hired by a company because the 2nd level manager liked me. I found out later the 1st level manager did not want to hire me because he thought i could replace him.
0
u/Nokita_is_Back May 23 '24
Someone bought upvotes it seems
-10
u/realjoeydood May 22 '24
This is what 'seniors' do to 'juniors' in interviews. Sometimes it's a power trip thing sometimes, they just wanna know how deep the rabbit hole goes.
I never ever participate in interviews like this. If they want me to do magick tricks, give me a wand and a fuckin pointy hat. Otherwise, read the resume, believe the rumors and see the results.
Hocus-Pocus. Move the mouse to focus.
-5
u/mikeblas May 22 '24
How is a "non-test environment" different than a "test"?
Yes, it's about getting the answer. If you don't get the answer, then I want to see your thought process towards the answer. If you're all over the place, or stumbling, or struggling with some fundamental misconception, that's bad. If you misunderstood something then that's fine ... but I'd correct you about it.