3 ms·
> Why are you asking questions about relational databases? Why not just have candidates accomplish the thing you're assessing with an actual relational database
by ddebernardy 8y ago
> Why are you asking questions about relational databases? Why not just have candidates accomplish the thing you're assessing with an actual relational database?
It's not the same thing. Browse around the various SQL tags in StackOverflow and you'll see plenty of candidates who can "accomplish" things using relational databases yet have positively no idea of how they work.
When shit hits the fan they're asking strangers to optimize their thorny queries. But a modicum of understanding of how a relational database works would have led them to a better way to do things to begin with.
- MBCook 8y agoI think the better example of a problem would be asking them how MySQL handles something when you really care about relational databases/SQL in general. Obviously if the job is highly MySQL specific and they need to know all the quirks that’s relevant.
- tptacek 8y agoAre you trying to say that there's some technical detail about solving a problem with an RDBMS that can only be expressed in an interview question? I call "shenanigans" on that. If the most obvious challenges are too easy for candidates to solve, so that they can just copy the answer from Stack Overflow, come up with better questions.
- ddebernardy 8y agoNot saying that at all. Merely that a mere of understanding of a few basics, such as how indexes work and when to use one, goes a long way towards being more effective at interacting with a database. "Here's some schema information. This complicated query meant to do X is running too slowly. Can you recommend ways to speed things up and explain your reasoning?"
- qaq 8y agoI'd care more if a candidate understands MVCC and transaction isolation levels. (which surprisingly few do)