4 ms·
I genuinely don't understand how it's useful to interview someone this way. It basically makes it a game of 'Show us what you remember from CS101/MAE101/etc'. R
by druiid 13y ago
I genuinely don't understand how it's useful to interview someone this way. It basically makes it a game of 'Show us what you remember from CS101/MAE101/etc'. Really why should interviews for people established in the industry be like that? Sure you should know how to do basic algorithms and optimization type questions, but having minute detail style programming questions that every engineer not fresh out of college will have forgotten since their core discipline classes is just silly.
- chris_mahan 13y agoMaybe it's a subtle form of age discrimination?
- druiid 13y agoNot sure how it could be considered age discrimination though. You tend to forget 'knowledge' like this fairly quickly. I know for my part at least I generally have to brush up on this kind of learning about every six months (or even less perhaps), if I wanted to retain it.
- chris_mahan 13y agoThat's why I said subtle. It would be like requiring you to recite all the marks you received on all your assignments in all your classes in your last semester of your senior year of college. I assume that if you had just graduated, this would be easy, but if you had graduated 10 years prior, this would be hard (feasible if you'd kept the paperwork--but hard).
- Zimahl 13y agoYeah, I don't know how it's useful. I think you could get just as many bad developers who are brilliant as good developers who are brilliant. I worked with a bad brilliant developer who just couldn't produce production code to save his life. We all saw where he was going with his code but he couldn't get there. We'd all end up cleaning up his code to get it into a better place. He would've aced interviews like at Google. In the end you need people who can deliver.