As someone who can do both but values the latter skills much more, I wonder about what these “low level questions” actually optimize for selection at some companies.
Part of me says that many companies want to select for willingness to “play the game” / conform rather than actually code deliverable product. In fact, being able to go from blank page to decent app in an app store might be considered a contra-indicator of a good applicant — easier for them to bail and do their own thing or be a hired gun.
Most orgs I’ve seen need a relatively small percentage of their devs to be creators and builders, but a large percentage need to be good maintainers and tweakers of existing code. These are vastly different skill sets and personalities, imho.
Thoughts on this?
And what sort of company / department do you work at that needs/wants a lot kf true builders?
In my experience, a good growth company will have at least the three following stages that can yield a healthy ROI with good builders:
1. Initial product (start up stage).
2. Secondary products and upsells.
3. Internal tools, iterative, and often in perpetuity for the life of the company.
I am not sure the “builders” should ever be more than about 5-10% of the programmers except in early stage 1.
I could figure it out, but the issue is that it will take time, and it is stressful. A new college grad by contrast still remembers Data Structures 101, and how to manipulate trees. This kind of "bozo filter" favors both new grads, and people who spend a lot of time memorizing trivia in order to solve these problems quickly.
"Invert a binary tree" like questions just filter out anyone who hasn't recently graduated with a CS degree or recently and deliberately studied algorithms. I don't think they're that useful if you want to find a leader.
This is why I think those low-level "invert a binary tree" and "find a substring in a string" questions are not really that great if you're trying to find someone to actually build an application. Many more people know how to invert a binary tree than know how to go from an empty text file to a non-trivial mobile app distributed in an App Store.
This is why I like high level design questions like: "Design an application that takes a user's GPS location, draws it on a map, and shows the 10 nearest restaurants." I'm not expecting them to open up their IDE and start coding. I want to see someone who can draw boxes and lines connecting them, and write the right words in those boxes. I want them to show which of those lines are network calls, which of them are IPC, and which of them are API calls within the actual app. Which of them are provided by the operating system and which of them will they need to write themselves? Then show what one of those lines might look like as an API. I don't care if they know the exact code that should be in those boxes. I want to know they are thinking sensibly about how everything fits together.