4 ms·
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?
by hdennis 12y ago
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?
- VLM 12y agoHere is a parody of what they're terrified of https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
- ExpiredLink 12y agoPrejudice nowadays is accepted as long as it is not related to race, gender or religion.
- ghaff 12y agoThis blog post discusses it a bit. http://jobtipsforgeeks.com/2013/03/07/enterprisey/ http://jobtipsforgeeks.com/2013/03/07/enterprisey/ It wouldn't shock me if it also gets used as code for things like "hasn't worked at a startup before" or, frankly, "too old."
- hdennis 12y agoThank you for the link, it was very informative. 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."
- fecak 12y agoI 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).