For example, take red-black trees. How do they work? Most of the time, I shouldn’t have to care. If you need one, every language has an excellent pre-written, well tested, high performance library that you can just use. The important skill is not being able to recreate this library, but knowing how to spot when you can use it profitably to solve a bigger problem, whether it is the right tool, how this will fit into the time or space complexity of your overall solution, etc
And that is exactly why I never ask anyone to implement basic data structures in interviews. Nor would I want to work with anyone who does (unless the work was designing language features).
I would never employ someone who didn't have the basic understanding of how the most common data structures work internally. Not red-black tree level of knowledge, more that they understand maps are not implemented by linearly searching a list.
the moment you would mention sth like that in an interview, I'd kindly thanked for your time and move on. There are much more important and pressing matters in the day of an java/spring developer than theory crafting about btrees. Like I will ever need that as a java/spring developer in the enterpise environment.
26
u/Roachmeister Jan 24 '21
And that is exactly why I never ask anyone to implement basic data structures in interviews. Nor would I want to work with anyone who does (unless the work was designing language features).