I once asked a senior developer "how will you figure out which class/method is causing the server to crash". They gave me all sorts of answers other than "i'll add appropriate log statements and check the logs".
anyone who has actually worked for a while with large data sets should be able to answer your question. but since it "sounds simple", it probably causes most folks to freeze or go onto a tangent.
Unfortunately, because of how our industry treats interviews, people "prepare" for it and that puts even good folks in the mindset of prepared answers rather than practical answers.
anyone who has actually worked for a while with large data sets should be able to answer your question. but since it "sounds simple", it probably causes most folks to freeze or go onto a tangent.
Unfortunately, because of how our industry treats interviews, people "prepare" for it and that puts even good folks in the mindset of prepared answers rather than practical answers.