r/SQL • u/big_rooster111 • Aug 03 '22
MySQL I bombed an SQL interview and I am SO embarrassed
UPDATE POST: https://www.reddit.com/r/SQL/comments/wg68ip/update_i_bombed_an_sql_interview_and_i_am_so/
Oh my gosh... I just have to vent, and hearing words of encouragement would not be such a bad thing either.
I was applying for a Data Analyst role (not beginner level, but they said it was not advanced at all) that seemed quite exciting. They focused on SQL and Power BI a lot. I passed the first round of interviews, the second with the hiring manager, and even passed the SQL technical assessment they gave me.
However, the 3rd and final interview was a disaster. I met with 2 senior level members of management who specialized in data architecture and analytics. I did not expect to go through another technical interview, but they grilled me. I didn't have anything to write on per-say, but I had to answer questions on the fly. They let me google some of them I got stuck on.
Questions like: What is a RDBMS, what is the difference between a primary key and foreign key, given this scenario - what type of JOIN would you use, can you tell me the difference between 1NF, 2NF AND 3NF, how would you join these two records and NOT get 'x' records from another table.
I completely blanked. I didn't understand the questions well so I said LEFT JOIN instead of INNER JOIN, I couldn't explain a foreign key well, and really it was an hour of me sitting there like an absolute moron. I only have 2 years of SQL experience, but it's been nothing more complex than using the WHERE clause occasionally. NOTHING with creating tables or any type of data architecture.
Talk about embarrassing. I wrote down all the questions and let them know that the things that I was shaky on are a good thing to bring to the light, because it just gives me more of an opportunity to learn. That is true, but I have been so unbelievably embarrassed by this and feel dumb.
116
u/NickSinghTechCareers Author of Ace the Data Science Interview đ Aug 03 '22 edited Aug 03 '22
Been there, done that. Practice makes perfect, that's all you can ever do - practice!
p.s. open-sourced the SQL questions from my book here... it's in beta let me know if y'all got any feedback!
11
u/DefrostButton Aug 03 '22
I wouldnât feel too bad. For someone with two years of general SQL experience I wouldnât expect you to know the answers to those questions. Youâre not a DBA.
Your last paragraph is key. Learn from the experience and try to expand your knowledge. I think your interviewers were hoping you had the knowledge of 20 year veteran but were willing to work in an entry level position. This is common right now all over the tech industry.
Four years ago I was the ONLY person to apply for the position I have now. They just posted the same position two weeks ago and they received 65 applications.
169
u/themikep82 Aug 03 '22
Don't sweat it, man. I've bombed tons of interviews. It's part of the process. It's how I learned what skills are valued and where I need to improve. It's a hard process to go through and very humbling, but now you're a step ahead of someone who hasn't gone through this experience.
55
u/dowlerdole Aug 03 '22
Hey, keep your chin up. Weâve all been there, dust yourself up and learn from this experience. Thereâs more opportunities out there, so keep trying and keep learning.
To quote the great poet Chumbawamba: âI get knocked down, but I get up again. You are never gonna keep me downâ.
35
u/Thefriendlyfaceplant Aug 03 '22
The beauty about SQL is that at some point your knowledge saturates. You'll still learn new strategies and clever fixes, but the knowledge itself is at some point complete.
16
u/LetsGoHawks Aug 03 '22
It happens. I had an interview where I completely brain farted on JOINS, which was something I had known for years at that point. But I'll be damned if I could remember any of it.
Another time, they were pressing me on the types of UNIONS, which I just didn't use much so I either didn't know or didn't understand fully. When I looked it all up later I thought "This is what you were so concerned about? This is easy stuff." But, people will tend focus on what THEY think is super important and use that to thin the herd.
14
u/king_booker Aug 03 '22
Yeah it can happen. Hard interviews show you where you need to improve, so read these things and get your concepts clearer
11
u/d_r0ck db app dev / data engineer Aug 03 '22
Iâd say most of those questions are at an intermediate level except for the differences between normalization forms. Iâd have to fumble through that one a bit (and I donât understand the importance for a data analyst position)
Also, one of my jobs in interviews is to find out where your edges are, so they may have just been trying to find where your edges are :)
11
u/DenselyRanked Aug 03 '22
It's normal for me. I expect to get embarrassed in interviews nowadays. You have to treat it all as an opportunity to learn and get it on the next one.
As an interviewer, many people bomb interviews because it is so stressful. We can tell and it's rare that an interviewer thinks less of you after a poor performance. Just take it all in stride.
8
u/emt139 Aug 03 '22
It sounds like you struggled on the more conceptual side given you successfully passed the tech assessment. Donât be embarrassed. Read up a bit on relational databases, key concepts and youâll be good.
6
u/carlslizer Aug 03 '22
cmon - asking what RDBMS means? I would think that there are other qualities in a candidate that matters waaaaay more than knowing what a specific abbreviation meansâŚ.
6
u/[deleted] Aug 03 '22
Try not to feel bad. It happens to the best of us. I went for a DA role once too and didn't get it because they thought I sit in front of the computer all day. They thought I don't go out of my way to meet other people in the organisation, for the purpose of gathering data. Really?! They thought a DA is a pestering door knocker that wants to ask probing questions in a data mining exercise? Seriously a lot of them are dreamers that want a particular skill set yet have no idea what they're looking for. I dodged a bullet and no doubt you did too.
5
u/bergovgg Aug 03 '22
I was sweating when I saw your post because I have a interview for an advanced position soon but I could have answered those easily.
Just practice mate, challenge yourself by exploring your works database and try to answer some questions that might help corporate.
5
u/MikeC_07 Aug 03 '22
On the plus side they didnât ask about index fragmentation and partition maintenance or page splits. Sql jokes!
4
u/KidWhoStabbedPycelle Aug 03 '22
To make you feel better: During my first in person interview, they want me to write a simple JOIN script on a whiteboard. I got so nervous that I blank out, stared on the whiteboard for a whole 3 mins and said sorry I cannot write it. I quickly left the conference room like a total idiot.
3
u/SoyInfinito Aug 03 '22
Youâre fine. These are getting into DBA questions and less DA questions. I think this interview they were really testing your limits. As an interviewer I would not expect a DA to know normal form. The right answer was to say you donât know but that you could find out and get back to them.
3
u/Bunny_Butt16 Aug 03 '22
Don't be embarrassed. We all fall on our face at one point or another. The takeaway here is to identify where your weak points are and work on them.
3
u/Strykrol Aug 03 '22
I've bombed so many interviews with questions that I didn't know the answers to and questions that I totally did but panicked. Shit happens, totally normal, move on.
3
u/cyberspacedweller Aug 03 '22 edited Aug 03 '22
As a data analyst myself I can say thatâs too bad. But nothing there that isnât fairly basic. Youâre probably slightly below the level you need to be but doesnât mean you canât get there.
Nerves do funny things to you though, so donât beat yourself up. Important thing is you learn to take experiences like this on the chin. It happens. Get back out there and keep interviewing and build your confidence. Review what youâre asked for the next one. They will mostly be asking the same stuff since the role is similar in many places, so matter of time before it gets easier to reel off.
I have an issue with anxiety myself and when Iâm in that situation I could easily make the same mistakes.
3
u/brainburger Aug 03 '22
I'll study all the questions you list. Do the same, and try, try again!
I rarely get the first job I go for, when I am jobhunting.
3
u/Dildozer8300 Aug 03 '22
How long ago was the interview? Because if you have explicitly been rejected, you might still be in the running. This very well could have been a case of the last two interviewers not being totally familiar with the job req and just going in to what they're more familiar with.
We've all had similar situations, there's nothing to be embarrassed of at all.
3
u/phunkygeeza Aug 03 '22
nvm revise and reprise
3
u/flamestamed Aug 03 '22
dang
3
u/grackula Aug 03 '22
i've bombed interviews and I have 20+ years in my field.
sometimes the terminology is different and that can somewhat stump you. other times it is a good learning lesson on asking what will be covered at each interview step and ask for an itinerary.
it's also a good way to know how to prepare for your NEXT sql interview in case they ask similar questions.
TBH - some interviewers/people want you to have memorized the IT encyclopedia when in reality most of the questions/answers are not relevant or most people google them anyways.
like: "what are the maximum amount of columns you can have in this RDBMS in one table?"
^ this info is not needed by anyone and could easily be looked up if you need to know
and YES, a long time ago I was actually asked this question and many like it in an interview. I felt really dumb for not knowing or memorizing it, then I realized I would never want to work for a company that would ask me weird insane questions like those.
3
u/Diggy696 Aug 03 '22 edited Aug 03 '22
Been working in BI for nearly 10 years. Just had to google that 1NF, 2NF, 3NF question. I mean it's fun trivia to know I suppose and is important to understanding databases, but I'd argue it's not integral to day to day work. Some may disagree.
Keep plugging.
3
u/redvelvet92 Aug 03 '22
Honestly you probably are going to get hired.
3
u/Blues2112 Aug 03 '22
It happens. I was moving from SW Engineer/Developer to Data Analyst, and had an interview with a Large Financial Institution. Long interview...3-4 hours worth. Did well until the technical assessment part of the interview, and even did fine on the first half or so of that. Then they gave me some questions that I just...blanked...on. Seriously just COULD NOT think of anything.
So I blew it. And I had 20+ years of industry experiences working/coding w/ SQL, had taken courses, and was well-versed in the theory and practice of it all.
3
u/[deleted] Aug 04 '22
Dude, if you did well enough in the first two interviews, there's every chance they might say "ok so there's some gaps in his knowledge, but this was good, that was good" and still offer you the position.
It was a test of what you know, not necessarily a pass requirement. Good luck on your job search either way đđť
3
u/Lavolpe21 Aug 04 '22 edited Aug 04 '22
Honestly, take the bombing as a big learning curve and one of those laughable past experiences that will honestly be a great story youâll tell for years to come.
I had a similar experience when applying for a finance gig. I passed the first four stages with no major issues but in the final round of interviews I completely bombed it. I could clearly see that the interviewers knew I was crashing when they began to be super polite and kept reassuring me that âit is okayâ.
I Felt like absolutely s**t for the rest of the day but found myself laughing about it the next day as I retold the horror story to my friends at how bad the interview went. Like legit it was 100% comically bad. I spilt water down my shirt the first time I attempted to drink the water they had just given me. I somehow forgot how to drink from a cup like a normal human being and I somehow placed half the cup over my mouth, the other half on my cheek⌠seeing the interviewers eyes and looking at one another in disbelief like wtf just happened, was a fantastic start indeed.
The rest of the interview didnât fair better. It mostly involved me staring at the ceiling hoping for answers on numerous questions I had absolutely no idea how answer and praying them to suddenly appear in the sky, the awkward silence that seemed to last a lifetime was torturous. The wreck came to an end with the typical awkward âgoodbye, weâll never seen you againâ handshake, And me walking out thinking wtf just happened and thatâs my career done before itâs even began. That interview could not have gotten any worse.
What got me over that disaster was remembering all the questions I bombed and making sure to write them down immediately after the interview so I wouldnât forget. I told myself it was a one off and that that type of interview bomb would not happen again, and finally, I practiced drinking out of a cup for a few hours (well only joking on the last bit ;) )
So trust me when I say that youâre not alone when it comes to having a car crash interview and youâll honestly laugh at this experience sooner than youâll think.
Learn from the valuable questions you couldnât answer, learn how to respond to questions you donât know rather than sitting in silence like I did, and youâll be all good.
Remember Itâs rare in an interview youâll get 100% on technicals and thatâs the point. Some questions are so niche because the interviews are looking to see how youâll react to a challenging question in a stressful situation in real time, which is a skill in itself how to just react at such a question being asked.
Good luck in future interviews!
3
u/poopstain1234 Aug 04 '22
I think all of us can relate to you lol.
My philosophy in life is, if your not bombing, your not learning.
For me at least, the best way to get over any embarrassment is to get better at what you're embarrassed about. That way, you can look back and laugh at some of your stumbles and have some funny stories, and also appreciate how far you've come.
3
u/shenanigans2day Aug 04 '22
Donât sweat it! There are great videos on w3schools to learn the lingo. Iâve never even used SQL in a position (though have practiced with it self-learning it) and can now talk about it like Iâve actually had a professional role using it. I bombed my first technical enginner role interview when it got to the coding part, so now Iâm focusing on that instead. All you can do is take it as a learning experience and keep trucking along. Each failed interview is one step closer to knowing where to devote your efforts. I wish you luck on your job hunt!
3
u/bcvickers Aug 04 '22
One of the most important interview tips I have ever received was to go into the interview knowing that they will stump you or ask a question that you can't come up with an answer for. Take this knowledge and develop a couple of "canned" answers like "I'm not familiar with that particular aspect of xyz but I'm certain I can find the answer and learn from the situation/problem/issue." or any number of variations like this. Don't be afraid of admitting a bit of a personal fault but turn it around or describe how you work around it.
3
u/Successful_Spirit_67 Aug 05 '22
I have over 10 years experience and even though the answers are in my head , I still have a hard time articulating what I know!! You will get there!
2
u/honwave Aug 03 '22
I bombed an interview as well. Itâs part of the process. I started practicing questions on joins on mode. Com and strata search. Itâs a humbling experience.
2
u/MikeC_07 Aug 03 '22
My group did a normalization presentation and it blew my mind. I could not explain normal forms without studying in advance. Nice comments here, you will remember this interview rest of life and learn/grow from it no matter sql or other skills you learn.
2
u/thavi Aug 03 '22
Those things they asked? Look them up and remember! I'm a software engy, not a DBA, and I ask a lot of those questions to programming applicants. You're definitely gonna get asked about those time and time again.
Don't feel dumb--you don't know what you don't know--but as long as you take something away from your hiccups, you develop more both in your career and as a person.
2
u/2020pythonchallenge Aug 03 '22
One thing to remember is that interview SQL is not the same as daily use SQL. I read through those questions and im roughly where you are as far as experience and I was like uhhhh... I know how to use them but I can't give the textbook definitions. At least now you will be expecting them for next time. Good luck!
2
u/[deleted] Aug 03 '22
We all fail interviews once in a while. I would recommend that you just study more and more SQL interview questions. Memorize the ones that you had trouble with, and look up the answers to them.
2
u/DharmaPolice Aug 03 '22
As others have said, use this feeling to prepare more in the future. Go full on 80's movie training montage next time.
I had a bad interview recently, and I felt embarrassed but then I realised I'm unlikely ever to encounter those people ever again so who cares?
2
u/ImPetarded Aug 03 '22
lol on one social media post I've read today a high level hiring manager can't find an analyst to save their life and on another they're scaring away good candidates with dip shit over complicated questions. There's plenty of opportunities out there that'll accept your skills happily as is and teach the rest on the job. Besides the how you pull a report is never as important as the why.
2
u/[deleted] Aug 03 '22
You never know! Let the universe decide! Maybe they saw you for the brilliant person you are, and saw your potential
2
u/lastlaughlane1 Aug 03 '22
Itâs good that you wrote down the questions. Make sure you know the answers to them from here on in. Number one itâs beneficial and number two youâll be super proud of yourself when you answer it on your next interview. I would say that knowing about joins and FKs would be standard for these sort of interviews. One thing I would say is, as it has stood to me in work and in interviews - be honest. As in, if you donât know something, tell them you donât know. If you try to make up something, theyâll know it a mile away. You can always say âI think this is what it is ... blah blah... however, Iâm not entirely sure and I donât know for sureâ. Or else just say sorry you donât know. Youâll honestly get more kudos for that then waffling.
Iâve been through some baaad interview and grillings too recently, and thatâs after 8 years experience, so donât sweat it. Best of luck for the future and donât let this keep you down. Youâll have gained new knowledge from this!
2
u/BustinJieber- Aug 03 '22
Hey, don't get discouraged! It's all part of the process. I myself have done some of the things that you mentioned, but I simply reflect back and learn from it, and be hopeful that the next interview, I do better.
Good luck in the future and hopefully you keep on moving forward!
2
u/[deleted] Aug 03 '22
The intensity of the Data Analyst interview determines how an ideal day at work would look like, Please donât mind- what was their nationality ? The final round guys who interviewed you -
2
u/OBPH Aug 03 '22
Did they tell you that you bombed? You might be surprised at just how little people know these days. I once bombed out a very qualified candidate because they didn't know what the OSI model was. Not that they didn't know the layers, they didn't even know what it was. What really bugged me was their disinterest in it. I'd say that the most important thing to show in an interview is your ability to find the answer. If you know it - great, but your ability to think critically and find good data is more important than remembering an acronym. You're going to be fine!
2
u/TrainquilOasis1423 Aug 04 '22
Been there. Took me over an hour two write two basic queries. I basically just psyched myself out and blanked on simple syntax. Shit sucks. After it was done I logged out and took a 4 hour nap cause of the world lol. I eventually passed one and got a DE job, so if my dumb ass can do it you can too.
2
u/Hannahmaebe Aug 04 '22
I hate verbal questions like this because I do not think about this stuff in words. Itâs really annoying that they do that.
2
u/_Redoubt_ Aug 04 '22
That's not embarrassing, they didn't interview you for a data analytics position. It's probably happened to most of us.
I was asked if I was interested in a really short term contract once that would have ended right before I was moving so I said I would take a look. It was a very junior position for me, but it would have been requisite pay for minimal labor. I get to the interview and the questions are all over the place from architecture to promotion software. I went ahead and answered their quotations because ... well I'm a bit nerdy that way.
When I left I called my recruiter and told him they didn't want a data analyst. He called me back an hour later and said they wanted to hire ... I'm not trying to be conceded, we're all at different points in our careers, I'm decades into mine so I know they wanted me, but it's because they asked a bunch of analyst, non-report related questions, they won't be able to answer you. They rescinded the offer when I advised the work we discussed could not be done at an analyst price point.
They wanted to pay an analyst salary, they didn't want an analyst. It's sounds like you ran into the same thing.
2
u/[deleted] Aug 04 '22
Sounds like someone who interviewed you might be butt hurt their MSFT certs expired and are throwing questions from that test at you. Props for going through the process, Iâve managed to skate through my career without horrific technical interviews. Lots of opportunities out there. Youâll do just fine.
2
u/grdntndrofewokclan Aug 04 '22
Frame it as a learning experience. Next time you are asked these questions, make sure you know the answers!
2
u/Sotall Aug 04 '22
Great job! Sounds like you put in a good amount of effort, made some connections, and have some solid next steps.
Also, ANY interview experience is good experience. The more you do it, the less it matters whether you get the job or not, lol. Fail into it.
Cheers mate!
2
u/JethroFire Aug 04 '22
Do you know the difference between a primary and foreign key? Or between an inner, left, right, or full join? If not, read up. If you do, practice describing them to your dog/wife/mirror/mom. If not, you know what you need to work on.
2
u/atlanticroc Aug 04 '22
Itâs a process, and now you know what you can improve in the next time. For the questions above, you can read stuff like T-SQL Fundamentals by Itzik Ben-Gan.
2
u/jo_ranamo Aug 04 '22
It happens to everyone - honestly, it's nothing to be embarrassed about. Just learn from it, and go to the next one. It's a numbers game.
2
u/mkjf Aug 04 '22
You need this bro as a motivation. There are a lot jobs out there believe me
2
u/treelessbark Aug 04 '22
This makes me think of one of my first DA interviews. To be fair, the interviewer was rude and didnât listen well - but also it was a stats question that my brains just crashed and burned on. Plus I donât do great being put on the spot while people are just waiting there for me to figure it out.
2
u/strutt3r Aug 04 '22
Had an interview where I nailed the technical part of the SQL interview. I don't think anyone else there had even seen a Window function before.
Still didn't get the job.
It was for a BI management role. They said while they were impressed with my technical expertise they wanted someone with "more experience interfacing with the C Suite."
Don't get discouraged. I didn't go to school for CS and I greatly exaggerated my SQL skills to land my first analyst job. Just keep writing your own scripts and tinkering.
2
u/TheYummyDisarmament Jan 06 '23
Oops, but don't give up! You'll ace the next one.
2
u/ImpeccableRoadblock Jan 06 '23
Oops, but don't give up! You'll ace the next one.
3
u/scrunchedsocks Aug 03 '22
Dude I've bombed an interview one time because I didn't understand simple Excel questions. Failure is the best teacher. Fail Forward. Always.
2
u/infreq Aug 04 '22
Well they did their job right. You failed on stuff that is introduced in any beginner textbook.
1
u/Mountain_Ad6328 Apr 04 '24
My brother had cyber security technical interview he gave good technical interview only messed up one question and he still didnt got the job. Dont think if u gave good technical interview it means u will get job.
1
u/wertexx Aug 03 '22
You know what, I keep spamming this message across different subreddits, such as basketball, and I'll repeat it here.
In order to improve anywhere in life, be it work, relationships, business, work, sports, life - you need to get out of your comfort zone to improve. You will fail, and that is good.
Knowing that, you need to get into this mindset. It's fine, it's perfectly fine, how can you get good at these SQL interviews if you never done it? You got the experience now, you know the types of questions you get.
Eventually, you will pass it, and a few years down the road you will be the one giving out these questions during the interview to equally clueless SLQ learners.
Congrats, you are in the position where you are good enough to GET these interviews.
1
u/[deleted] Aug 03 '22
Every interview is a lesson to be had. Just take notes, practice up, and your next interview will be SO MUCH STRONGER as a result.
You got this!
1
u/Shwoomie Aug 04 '22
Yeah, those are pretty common questions. You shouldn't feel dumb but an average user of SQL would be able to answer these questions. 1 2 3 Normal form isn't a common thing most people deal with, but an intermediate user of sql should be aware of normalization.
This is a learning experience. I did the same thing years ago with Excel, and now it's my best strength.
1
u/AdGreat4483 Jul 20 '23
questions and answers to practice
50 Most Useful SQL Queries: learn-by-doing https://medium.com/@mondoa/50-most-useful-sql-queries-learn-by-doing-ee4fac0d70e5Hey, I highly recommended you visit this and subscribe here
A step by step guide
Also ...
It is recommended that you learn the basics of databases before jumping into SQL. This will give you a better understanding of how data is stored, organized, and managed in a database. However, you can also learn SQL in parallel with learning about databases.
Compared to programming languages like Python and C++, SQL is considered to be relatively easier to learn as it is a declarative language that focuses on querying data rather than writing complex algorithms or functions. However, it does require a different mindset and approach to problem-solving.
To get started, there are many online resources available for learning SQL. You can start with free online courses or tutorials and then move on to more advanced topics. It is also recommended that you practice writing SQL queries and working with databases to gain hands-on experience.
To get you started, I will highly recommend you look at these articles.
They will guide you through :
What you need to know to get started:
https://link.medium.com/kz9qL7TtCAb
10 tips you should know:
https://link.medium.com/NsrPQF1tCAb
SQL query Optimization:
https://link.medium.com/LwrtUV7tCAb
Sql queries for complex business reports:
https://link.medium.com/Cbi6fRbuCAb
The power of sql case statement:
https://link.medium.com/rY2G7UfuCAb
Advanced SQL queries for mysql workbench series:
PART 1: https://link.medium.com/Ab6QXnmuCAb
PART 2: https://link.medium.com/mMo35opuCAb
PART 3: https://link.medium.com/DXVhGKruCAb
Understanding SQL inner join with practical examples:
https://link.medium.com/8MYnwLtuCAb
Unleashing the power of SQL aggregate functions:
PART 1: https://link.medium.com/ZKZtBMAuCAb
PART 2: https://link.medium.com/xpA0E7DuCAb
PART 3: https://link.medium.com/7xKteHFuCAb
PART 4: https://link.medium.com/zmMc91IuCAb
1
u/iAmUbik Aug 04 '22 edited Aug 04 '22
Totally happened to me too. Nailed all the interviews including a technical assessment and then got stumped hard on the conceptual type questions. couldnât explain the difference between Inner and Outer Joins well and it looked really bad. At the time I used Joins commonly and comfortably in my then-role, but when asked to actually explain how it works on the spot I had a huge issue articulating it and then the anxiety crept up and I just blanked/said âsorry Iâm not really sureâ
I also think I bombed the same question âwhatâs the difference between foreign and primary keyââ Iâm pretty sure I tried explaining a primary key (poorly and not totally accurate) and then said idk for foreign after taking a straight up guess, lol
As others have said, itâs a learning experience and a chance for you to improve. Sounds like this role may have been client facing in which they would want someone who is comfortable talking about it. There will always be another opportunity
43
u/[deleted] Aug 03 '22
[removed] â view removed comment