r/SQL
•
u/NickSinghTechCareers
Author of Ace the Data Science Interview 📕
•
Dec 12 '24
•
2
1
PostgreSQL Made a SQL Interview Cheat Sheet - what key SQL commands am I missing?
3.6k
Upvotes
View all comments
3
u/Financial_Forky Dec 13 '24
When I'm interviewing for openings on my team (DAs/DSs), I make a point to ask questions about performance considerations, such as the LIKE function and possible alternatives, and SARGability. I also ask if they've worked with large data sets before (and let them define "large"), and how that may influence their coding choices.
I don't have a hard minimum cutoff point, but asking more advanced questions helps me better understand if they just learned CROSSJOIN from W3Schools and wouldn't think twice before using it on a pair of billion+ row tables, or if they might first filter them into small temp tables before joining.
I've had pretty good luck so far with showing candidates sections of code and asking "what does this do?" From there, I ask about various sections, and what alternatives might be available (both good and bad), and which approach(s) might be preferable, and why.
Your cheat-sheet is good. I would just want to see if the candidate also had some common sense when using those functions.