> A weakness of these types of SQL questions however is that it's near impossible for the interviewer to provide help/guidance I've given SQL interview questio

> A weakness of these types of SQL questions however is that it's near impossible for the interviewer to provide help/guidance I've given SQL interview questions quite a few times and like to present a sample dataset or schema, and state a problem statement or expected result. Then I collaborate with the candidate to come up with assumptions, and I give gentle guidance if they are stuck or going down the wrong path. I'm always up-front with the candidate about not looking for perfect syntax, and I am more interested in their problem solving and collaboration skills than the actual SQL they write. People who ask ask questions about the data and schema usually do much better than those who jump right into the solution. Just like in the real world where really nice SQL or code doesn't matter if it solves the wrong problem.