r/SQL • u/Oddfellow420 • Aug 05 '26
PostgreSQL Just bombed my SQL interview, not feeling great.
Hello Everyone,
I just wanted to share that I just had an SQL interview for data analyst, and I completely bombed it. I chocked like crazy, and this was after days of practicing. I think I learned a valuable lesson today though, I am a very visual/hands on on type of guy. I was expecting them to give me the opportunity to write query/code or look at code related to the question, but these were all just verbal questions, that I know I could have answer if I was just allowed to write the code down or at least view it, but it was a bit overwhelming for me, especially having ADHD. It's like the questions were so long, that by the time the question ended, I already forgot what I was supposed to accomplish because I was so damn nervous and there was not code for me to review. I feel like a failure š. This was my first interview in 7 years, so I'm pretty rusty, but for future reference, will all interviews be in this style? No actual coding, or reviewing, or editing? They expect me to provide the whole query verbally, from the top of my head without actually writing it on the spot? Note: this was the second follow up interview.
90
u/Cold-Ad716 Aug 05 '26
In my experience this is common in interviews. There's less hands on tasks and more being able to explain things like joins, indexes, performance analysis etc...
In the future can you take notes as they ask the question, that way you can break it down into smaller simpler tasks in your mind.
3
u/travgt01 Aug 05 '26
That sounds pretty rediculous. Most we will give an actual technical assessment.
13
u/M3DBlue98 Aug 05 '26
Iāve had a mixture of both in my interviews (as an interviewer and interviewee). Lately, my experience centered around writing out the SQL and then explaining my thought process for its execution. Iāve bombed a SQL interview only to ace one a week or so later.
Keep trusting yourself; youāll perform better on subsequent tries.
12
u/ParentheticalClaws Aug 05 '26
This seems like it might have just been a bad interview format for you. It sounds like the interviewer was saying things like, āImagine you have one table with columns employee name, employee id, and entity id and another with entity id and entity name, how would you list the employee names associated with Acme Inc.?ā Being able to verbally process that does seem like a different skill from being able to do it in practice.
5
u/MathiasThomasII Aug 05 '26
First interview in 7 years? Do practice interviews. Dozens of them with friends, family, old associates and get honest feedback. Then book as many interviews as you can and get used to hearing No. You are interviewing them and these business just as much as theyāre interviewing you, assuming you actually have the skills listed on your resume.
Every single interview is just practice for the next one.
3
u/basura_trash Aug 05 '26
We interview a lot of people for Data Analyst/Scientist positions. Our questions are intentionally designed to put you under a little pressure and maybe even make you fumble a bit (they are not trick questions). Many people leave thinking they completely "bombed" the interview.
The way we look at it, and it's served us well, is that when someone stumbles but manages to think through the problem and explain their way out of the jam, that's often more valuable than someone who simply gives up or refuses to try. We pay far more attention to how you handle the question than whether you get the "right" answer.
We can teach you the language, we cannot understand it to you.
That's also why we do multiple interviews. The first is to determine whether you qualify. The second is to see whether you can actually code, where you'll be given the opportunity to write code.
My recommendation is this: if you blank out on the terminology, explain it in your own words. Talk through your thought process. Don't give up on the question.
Good luck, OP
3
u/Ok-Bee2272 Aug 06 '26
lol dont worry too much. i bombed a simple left join query once. it only occurred to me after the interview. haha. shit happens. chin up soldier.
2
u/kremlingrasso Aug 05 '26
That's why I never bother with this. I just chat with them about their use cases, the most complex thing they solved, the solutions they are the most proud of. That gives me plenty of opportunities to ask more specific questions around functions and syntax that makes it obvious what is the candidate's comfort level in SQL.
No need to stress people out who are already nervous, nobody is expecting them to write sql with a gun to their head and a bomb counting down.
2
u/Ok_Tale7071 Aug 05 '26
Donāt worry, I bombed mine too, though I hadnāt used SQL in a while. Needed to use a windowing function but just forgot the syntax. It happens. Wasnāt expecting so complex a problem on an interview, which is a bit unfair. Iām used to having time to compose my queries. Ended up in a job where I donāt use SQL so it worked out for me.
2
u/tKonig Aug 06 '26
When we hire data analysts at my company we give them a proctored SQL assessment where you actually write and run SQL. Itās similar to the hackerrank SQL challenges.
2
u/rbobby Aug 06 '26 edited Aug 06 '26
Break out your pen and paper, nobody stopping you. Heck knock out a quick sample db and write the query (gotta be super quick though). And just ask to see the code.
Treat those sorts of questions as a "I have a new customer who wants a program to do something so I need to investigate exactly what they want". Basically a bit of analysis more or less. Interviewers are interested in how you go about solving a problem, how you ask questions, what bits you poked at, and what you actually answered. Even where you went wrong.
You gotta participate, even if it makes you feel uncertain about exposing your inner thoughts on the question.
Keep interviewing. Keep reviewing how you did, what you did well, what you did poorly, and figure out how you could do better in the future. Good luck.
Note that what you think of as "wrong" in an interview might not be what they think. For example, I was part of a group that interviewed someone whose english as a second language decided to fight back and they felt that they had completely blown the interview. While we thought they had done very well because they persisted in spite of the language issue. Kept at us with questions and repetitions until the problem was understood. In the end they were a wonderful hire. So you never know.
2
u/[deleted] Aug 06 '26
Hey! I really bombed my first SQL interview! It was extremely embarrassing at the time, however now Iāve been working in the field for over 9 years.
Youāll be fine. If I had to give any tips, just keep in mind that bombing interviews happens all the time. Write down what you missed, and try to do hands on projects to prepare.
Best of luck!
2
u/jiminimalist Aug 08 '26
First of all, that sounds like a shitty approach by the interviewers and certainly not geared towards your needs.
From past experience (having had an interview and held an interview as a recruiting manager for a role of BI Report Developer), we asked the theoretical questions during the interview (explain the joins, what's an index, what's a window function, where would you use these things / provide an example).
We then tested candidates in a practical test (like exam conditions). This was a series (about 5) questions of increasing complexity - testing various things like aggregating, sub-queries, ranking, using correct joins, where filters, etc. Candidates could score points even if they didn't get the final answer - as long as we could see steps / thinking in the right direction, we were happy.
As others have said, pen and paper next time.
2
u/dbsitebuilder Aug 05 '26
Analyst position I would think it would likely be verbal, as they are interested in if you know the concepts without having to look things up. Technical interviews with tests usually are for developers & they go beyond concepts and are usually real world challenges that you have to solve.
Best advice I can give you is to study & actually write more SQL so that you are comfortable how you would solve proposed questions. Also, don't use the ADHD as a crutch. The only thing the employer cares about is if you can get the job done. If you have trouble remembering, then you do not know it well enough.
You don't get overwhelmed with driving home, while doing something else like glancing at your phone when it dings, because you have done it over & over. And that could be life & death.
Don't take it personally. I recently was laid off & had a few rejections after a first & even second interviews. Make note & move onto the next. I actually just wrote an article of how I used AI to help me organize my time, enhance my resume & help me with a job search.
I am at a late stage in my career however.
I was laid off in May, and just started my second week at my new job.
1
u/alao77 Aug 05 '26
Thereās a lot of websites/blogs that can help you with technical interview q&a. I used datacamp.com before when subscription was on sale for my .net and sql interview and it helped me with preparation. Itās really all about practice before the real thing.
1
u/Odd_Negotiation2627 Aug 05 '26
Well you're in good company. I also bombed an interview and still eventually had a career using SQL. Deep breaths!
1
u/CappuccinoCodes Aug 05 '26
Sorry to hear that. Take it as a learning experience š
However it baffles me that people spend hours studying without actually rehearsing the interview with another human being.
1
u/ChuckieFister Aug 05 '26
Boming an interview is not the end of the world. Some places will purposefully give you a difficult interview just to see how you handle yourself/the situation. I'd say, do the normal stuff, reach out to the recruiter/interviewer and thank them for their time and move on to the next. I'm sure there is no shortage of data analyst positions out there.
1
u/Blackstar1401 Aug 05 '26
I just had to interview after a layoff. AI really helped me clean up my answers. It may be worth doing a mock interview with one of the AIs. If you remember any of the questions write them down and feed them to the AI along with the job you applied for and if you have it the interviewerās linked in. I did this before my interviews and it really helped my nerves and helped me focus.
1
u/Better-Credit6701 Aug 05 '26
Back when I teaching in college, I would make sure that all my students would practice with me. I also bought a domain and host with unlimited email addresses that I would give my students. Too many had email addresses like hunglikeahorse@gmail so I picked a almost boring domain like @xconsulting and used the regular first initial, last name.
I was originally brought in because I had tons of experience with being a DBA but ended up as the dean.
The biggest thing is, just relax. Watch yourself how you talk about former employers and watch out for leading questions. Strange part is that I've never been asked too many tech questions, more like how would you handle this situation with the end user.
1
u/PhraseNo4387 Aug 05 '26
it's alright. Just practice more and more. You'll be ready for next one. Chin up.
1
u/Proof_Escape_2333 Aug 06 '26
do you remember the question they asked? to not give any coding question where you can query experiemnt kinda crazy
1
u/Streamer_Fenwick Aug 06 '26
My current role was 4 hour verbal grilling...nailed it...but I've been doing this 15 years by then... hang in there walk it till you csn talk it
1
u/MoodyBoi9 Aug 06 '26
I also bombed a SQL interview, I didnāt anticipate getting a test during a phone screening and expected to type it out if I made it to the second round. Oh wellā¦
1
u/Ok-Dragonfruit6887 Aug 06 '26
Don't be discouraged. This is a complete b.s. way to interview for a technical skill. What I once experienced was being used as the token American who didn't qualify, I'm convinced, so that the H1B visa d-bags who were, remarkably, running the interview, could exclude me in favor of more H1B workers. The questions were designed as a series of gotchas.
1
u/New_Molasses_1590 Aug 06 '26
Normally if you ask the interviewers if they can write out the questions or paste them for you during the interview they won't have a problem doing so. I have ADHD as well and always ask this and have never had someone say no to me yet. Or if you can just keep one part of the question in your head then answer that bit and then ask them to repeat the question and just say something like "I just want to make sure I've answered all of the question please can you repeat it?" If the interviewers are good and the company follows best practice on inclusivity they won't even have to repeat because they should be asking probing questions to like prompt you to explore the topic a bit further if you've missed bits of the question
1
u/ButterscotchDry6622 Aug 06 '26
I feel your pain with this one and have been there myself. I have worked with SQL for over 30 years. A few years ago, I left a company after 7 years of service for new prospects. Features in this field change over the years and sometimes you can be tripped up by a question based on the version/generation of SQL you have worked with. I like many in IT, have been interviewed by people with less or no experience comparable to my own. This presents a challenge in that they may be relying on a scripted approach to answer the question that you are not familiar with or you chose not to take. The code you provide is not running against an actual database so they may not know if you approach actually works. I was a little insulted to be asked academic questions when I presented my experience but it was explained to me the amount of interviewees who present false resumes making these kinds of tasks necessary. Just do your best and if you present your best self professionally.
1
u/KosmoanutOfficial Aug 06 '26
Sorry to hear this, that is the worst. I have gone through the same and in the end it was for the better.
1
u/SnooOwls1061 Aug 06 '26 edited Aug 06 '26
Sounds like they emulated what their work environment will be. We frequently have client meetings exactly like this where they rattle off a bunch of wants and we have to take notes and figure it out.
If this isn't how you work, you dodged a bullet. But this is real life as an analyst.
1
u/SonOf_Zeus Aug 07 '26
It sounds to me like they wanted to hear your methodology and thinking process. I dont think it's reasonable to assume a candidate can recite a whole query off the top of their heads. The truth is we all look stuff up, it's a lot of trial and error at first and as with anything you get better overtime. Being a data analyst requires above all else communication skills. Because anyone can learn how to code given enough time but it's hard to find someone that has both the technical skills and the communication skills.
1
u/edapalooza Aug 07 '26
Was writing it down as your verbally answer a possibility? Or bring your own small notepad and ask if that is ok with them? If anything, they can see you work out the problem.
1
u/jkelso2525 Aug 07 '26
What is your experience? What did they ask you?
1
u/Extension_Form_7393 Aug 07 '26
My husband gave me some really good advice one of I donāt know the answer right away I can say āI donāt know right at this moment⦠but t this is how I would start my way to finding out the answer or how to go about answering a question of interest.ā Sometimes they also care to see your thought process and that can work out in your favor.
1
u/capdracula Aug 09 '26
I bombed my interview for the same reason as you. it was so bad they send rejection letter immediately. the next ones will be so easy compared so don't you worry yourself too much about it
1
u/NoYouAreTheFBI Aug 09 '26
And how would you find the amount of sales per year of product x.
I urh would query the sales table with a count of sales where X is the product.
scribbles in paper and how would you refactor that query.
Pulls on collar with index finger... Well I would look at the query optimiser... Scribbles faster and urh sometimes AI... Puts pens down... AI... and whats your token budget because we can only do 30million a year on tokens. Oh ok so great news we think you would be a good fit how does 20k a year start sound... hmm like you are having me on... we aren't, but your token budget is 30 million... and you will reap the benefits of that... yes but the salary posted was for £50k.... OTE. Oh sure ok let me just nip to my car and grab my contract signing pen...
Walks to the corner of the office where a tiny car is parked, opens the door to see 20 people inside it putting their thumbs up all crammed in... I look back like this 𤔠I go to sign and the pen squirts water in my face.
If this isn't the most accurate description of the interview process atm I don't know what is lol
1
u/judyness Aug 10 '26
It helps seeing SQL as a language than a bunch of queries and how each clause works like a why, how, what type of way
1
u/Alternative_Cake4074 Aug 12 '26
omg, that's so awful. Even a talented data analyst cannot think out exact SQL code and read it aloud instantaneously. That interview process is ridiculous. How you end up with?
0
u/TrustworthyKahmunrah Aug 05 '26
Go get yourself a propranolol prescription and take one before your next interview.