In the part of the article that lists "Rejection Reasons" one rejection type is "Too Enterprisey". Could someone please clear up what that means for me?
I wrote the piece you linked, and I do see still see that feedback on some candidates almost two years later. I think your interpretation of this as code for other things is fairly accurate, although not as much for the 'too old' piece. I've heard it for even the 7-10 years of experience range (though perhaps that could be construed as too old for some).
The two main points in the blog stated that an "enterprisey" developer may not be a good fit in a startup (change in development pace, responsibilities, etc.) and that they may use languages unpopular in a startup environment (Java and .Net are called out in the post).
I'm interested to see if there are other posts that echo this sentiment, aside from the OP, because now I have a fear of being "too enterprisey."
Instead of the Left Outer Join, couldn't you also make it an Inner Join to S.BOOK_ID? The question, if I read it correctly, only requires you to return sales in Nov 2013. If there is no data for a book_id, you want to exclude it from your returned data, no?
I would imagine it is up to interpretation. It would probably be a good thing to ask the interviewer about to show that you are thinking about edge cases.
If it were me, I'd prefer to see those that made no sales based on the question. I guess if I didn't want to see them, I would ask for "where sales are greater than $0.00".
Jumping onto this chain, I'd also like to take a stab at a sanitized version of your test. We often have to reverse engineer our Client's existing reports when creating new BI reports for them in Cognos, and I'm curious to see how challenging your 3rd and 4th problem sets are.
