5 ms·
I have a PhD in Computer Science and 10 years in the industry, and I've never not been asked to do some trivial programming task in an interview. Thanks for sho
by ModernMech 9y ago
I have a PhD in Computer Science and 10 years in the industry, and I've never not been asked to do some trivial programming task in an interview. Thanks for showing some common sense, but most interviewers are just lazy. One time I couldn't implement a skiplist, and the feedback I got was "we were concerned about your problem solving skills".
- lkrubner 9y agoEven recently, I've gone to job interview type situations and the interviewer has literally asked me "Do you understand what Object Oriented Programming is? Can you write good quality Object Oriented code?" This despite that my best known essay is titled "Object Oriented Programming Is An Expensive Disaster Which Must End" a fact the interviewer should know if they'd looked at my resume or spent 10 seconds looking up my name on Google. Wikipedia now lists me as one of the critics of OOP -- https://en.wikipedia.org/wiki/Object-oriented_programming https://en.wikipedia.org/wiki/Object-oriented_programming I'm lucky in that my position is comfortable, so I can laugh off stuff like that, and either educate the person I'm talking to, or end things quickly by explaining that there is probably some kind of cultural mismatch. But it shows a remarkable laziness on the part of the people who, in theory, want to learn more about me.
- 0xADEADBEE 9y agoI was exposed to this essay really early on in my career and it completely changed how I thought about programming. Thank you so much for writing that; I still link people to it today.
- kerberos84 9y agoMaybe it is your essay why he asked you if you understand OOP.
- FireBeyond 9y agoThat would be easily countered with "So... I read your essay and it intrigued me. As a baseline, to understand where you're coming from... can you...?"
- thomasrognon 9y agoThanks for this, I added this essay to my reading list. Breaking people out of the OOP worldview is currently one of my biggest professional challenges.
- BeetleB 9y ago>One time I couldn't implement a skiplist, and the feedback I got was "we were concerned about your problem solving skills". I think you're overthinking the feedback you got. If it was at one of the big names, they have the luxury of being picky. They can't hire every qualified candidate, so they have to reject most of them. As the interviewer, the company policy likely dictates the interviewer give a reason. Which puts the interviewer in a bind because it implies that there was a good reason for rejecting you. So they'll put canned statements like what you got. I recently got rejected. And one of the reasons given was something that 3 of the 5 interviewers had explicitly told me they don't care about. I recognized it for what it was - they feel obligated to give some reason, so they nitpick after the fact even though they told you they were not going to nitpick.
- toephu2 9y agoAs it should have been. The fact that you have a PhD means nothing to Google, Facebook, and the like (except possibly a slightly higher base salary than a new grad w/ only a BS) The question is, can you whiteboard? They will be testing that. If you can, then all is golden and you probably didn't need to waste those 4-6 years getting that PhD because what you will be working on will have nothing to do with your topic of research (unless it was AI/ML).
- ex_amazon_sde 9y agoMe and my colleagues never asked this trivial question when interviewing for Amazon, just like you don't ask a driver what a brake is.
- toephu2 9y agoI assumed OP was referring to white board coding questions when he said "trivial programming task", which Amazon indeed does ask you to do throughout the interview process.
- Retra 9y agoI didn't have to answer any hackneyed technical questions or take any tests to get a job. The most technical thing I did was explain how a data structure I wrote works, which came up naturally in a conversation about what kind of programming I have done. If you can demonstrate that you understand programming concepts and can learn, then it's not much more to assume you can write code. If you need someone who can hit the ground running with some specific technology, then you might need to go deep into it, but not to find out if someone can program.
- toephu2 9y agoGoogle does not hire people by simply assuming the candidate can code. You do not get the benefit of the doubt, and in fact, you must prove otherwise. They want to see you write code on the whiteboard and solve the technical challenge given.