My experience with interviewing is that what I think of as level two or three problems are presented, where you have to solve some recursive problem and give the O() notation for the implementation. This happens in each of the multiple interviews over the three to six hour interview session. If you're not extremely good at this you are going to be false negatived tf out of there right quick.
Top level problems are where the solution involves days, weeks or months of study and contemplation where the solution possibly involves a large amount of refactoring of existing code. Architectural level stuff. There is no way to test for this in an hour long interview.
When I mention refactoring, I often get a blank stare from the interviewer. I had a coworker recently who insisted on calling it "refuctoring", having no concept of it or any desire to investigate.
Top level problems are where the solution involves days, weeks or months of study and contemplation where the solution possibly involves a large amount of refactoring of existing code. Architectural level stuff. There is no way to test for this in an hour long interview.
When I mention refactoring, I often get a blank stare from the interviewer. I had a coworker recently who insisted on calling it "refuctoring", having no concept of it or any desire to investigate.