3 ms·
This kind of thing may be partly why interviews are heavy on CS fundamentals -- most good developers agree that they are important in a way that framework quirk
by CydeWeys 11y ago
This kind of thing may be partly why interviews are heavy on CS fundamentals -- most good developers agree that they are important in a way that framework quirks are not, even if we don't remember all the details throughout our daily lives. Personally I feel much more at ease disqualifying someone in an interview because they e.g. don't know what a binary search tree is for than if they try to use a Java for-each loop over an Iterator when that only works over an Iterable.
- crdoconnor 11y ago>This kind of thing may be partly why interviews are heavy on CS fundamentals -- most good developers agree that they are important in a way that framework quirks are not Google's interviews are heavy on fundamentals because virtually all of Google's tech stack is home grown. Other companies imitate this behavior largely because "if google does it it must work great". Ironically a majority companies actually miss the CS fundamentals that are vitally relevant to them (e.g. relational theory) in favor asking the fundamentals that aren't (e.g. big o notation).
- NotSammyHagar 11y agoWhen I worked on databases at Microsoft we were totally trying to find people with good cs fundamentals, and who could program. That was what we were looking for (like totally, dude :-)). At google we looked for those things. And in my new job, we also look for those things. Sure, now we ask questions about server and distributed programming, but good cs fundamentals are fundamental still.
- CydeWeys 11y agoYou mean relational as in RDBMS, right? I'm curious, what parts of relational DBs do you think are under-emphasized in a typical CS education that you make sure to ask interview questions about? Things like what does a LEFT JOIN do, etc.?
- crdoconnor 11y agoNormalization is under-emphasized in interviews.
- CydeWeys 11y agoOne interview problem I've had before that was clearly intended to measure good database design sense and understanding of normalization was "How would you design the database for a restaurant reservation system?" There are a bunch of restaurants, each of which has a bunch of different tables, each of which can be reserved for chunks of time on various days. I won't go into the details, but you can see how a good answer is maximally normalized. Is normalization taught in a typical CS education outside of a Databases class? Is it a general topic, or is it so specific to the scope of RDBMSs that you don't see it mentioned elsewhere? I don't remember.
- gaius 11y agoCS fundamentals is a filter for "recent graduate". It's a way to sneak ageism past HR, that's all.
- CydeWeys 11y agoI strongly disagree. I was definitely not a recent graduate. They sent me a detailed study guide before the interview with all the basic CS fundamentals they might reasonably ask you about. I think it's more of a filter at determining people who want the job and are willing to study for it than testing for recent graduation. It didn't take me that much studying for all of the CS-y stuff to come back, but the programming skill I've accumulated over a career is harder to fake. A lot of fresh grads aren't that great at coding yet, and it shows in interviews.
- BatFastard 11y agoSo they should test, or really talk about that. It's more about your approach to solving a problem then it is to the format of the language. Someone recently talked to me about how to handle a multithreaded issue. I showed them how to avoid the problem completely, but they didn't want that. They wanted to know what they figured out last week.