Comments on: Interviews Schminterviews http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/ my technology blog Sun, 06 Nov 2011 00:13:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nikhil S Vastarey http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-994 Nikhil S Vastarey Thu, 13 Jan 2011 09:17:50 +0000 http://riteshnayak.com/blog/?p=482#comment-994 Awesomesh as usual!! All the tech points went flying above my head, but there are a few points we cud discuss!! Chherrrs Awesomesh as usual!!

All the tech points went flying above my head, but there are a few points we cud discuss!!

Chherrrs

]]> By: Shailesh http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-980 Shailesh Fri, 17 Sep 2010 11:55:02 +0000 http://riteshnayak.com/blog/?p=482#comment-980 Nice set of points. would like to add a few -> If there are some existing code or project source code if the candidate can share, that would give some idea on his design skills. -> A Take home project or a coding assignment (often ignored in this part of the world) ,which can be quizzed upon during the further rounds interview -> first place in "bharatnatyam" or college fest might not matter, but participation in coding/development contests would be definitely interesting. ->I personally feel objectives do not add any extra value to normal software development career . It does look good for a research career. ->Interviews that gets over in a day is a dicey situation, u never know if it is a good hire or not. I feel interviews should be spread over a considerable amount of time with different levels of testing. Also, It helps to judge candidates (who are talented but not expressive) over a certain period of time -> A quick and easy way to find out if a person is passionate is " Do you or have you done projects apart from your work or academic projects"? A passionate developer would definitely have lots of personal projects to show case. Nice set of points. would like to add a few

-> If there are some existing code or project source code if the candidate can share, that would give some idea on his design skills.

-> A Take home project or a coding assignment (often ignored in this part of the world) ,which can be quizzed upon during the further rounds interview

-> first place in “bharatnatyam” or college fest might not matter, but participation in coding/development contests would be definitely interesting.

->I personally feel objectives do not add any extra value to normal software development career . It does look good for a research career.

->Interviews that gets over in a day is a dicey situation, u never know if it is a good hire or not. I feel interviews should be spread over a considerable amount of time with different levels of testing. Also, It helps to judge candidates (who are talented but not expressive) over a certain period of time

-> A quick and easy way to find out if a person is passionate is ” Do you or have you done projects apart from your work or academic projects”? A passionate developer would definitely have lots of personal projects to show case.

]]> By: Ritesh http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-974 Ritesh Fri, 30 Apr 2010 09:48:41 +0000 http://riteshnayak.com/blog/?p=482#comment-974 @Abhijit OO is always a good idea. Unless you are doing C, OO is a good concept to ask even for people who work on C++. But yes, for programming below the application level the interview will have to be slightly different. This is primarily targeted towards the everyday application developer. @Abhijit OO is always a good idea. Unless you are doing C, OO is a good concept to ask even for people who work on C++. But yes, for programming below the application level the interview will have to be slightly different. This is primarily targeted towards the everyday application developer.

]]> By: Abhijit http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-973 Abhijit Fri, 30 Apr 2010 05:26:32 +0000 http://riteshnayak.com/blog/?p=482#comment-973 I liked all the points you mentioned, yet wanted to know if for a system programming position (Kernel, networking stack , file systems etc) would OO, ACID properties, normalization be the right questions ? or is it expected regardless of what area you program in ? I liked all the points you mentioned, yet wanted to know if for a system programming position (Kernel, networking stack , file systems etc) would OO, ACID properties, normalization be the right questions ? or is it expected regardless of what area you program in ?

]]> By: Luis Sergio Oliveira http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-970 Luis Sergio Oliveira Wed, 28 Apr 2010 05:45:22 +0000 http://riteshnayak.com/blog/?p=482#comment-970 There are some much simpler programming questions that will reveal lack of experience in a programming language. Say, write a function that reverses a string to some candidates that say they are experienced in a language and you'll get sometimes answer times like 30 minutes. Its interesting that there are plenty of persons who expect to take a programming job interview without doing programming. There are some much simpler programming questions that will reveal lack of experience in a programming language. Say, write a function that reverses a string to some candidates that say they are experienced in a language and you’ll get sometimes answer times like 30 minutes. Its interesting that there are plenty of persons who expect to take a programming job interview without doing programming.

]]> By: Ritesh http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-969 Ritesh Wed, 28 Apr 2010 04:48:40 +0000 http://riteshnayak.com/blog/?p=482#comment-969 The reason for loving Latex generated resumes is sort of convoluted. A person who generates his/her resume on LaTex definitely would have worked on Latex before. It could only be to write technical papers and anybody who has attempted to write a technical paper knows the rigor and effort involved in writing them. That conveys a lot to me about the person I am about to deal with. Btw, here's a cool resume template for Latex http://github.com/sids/resume The reason for loving Latex generated resumes is sort of convoluted. A person who generates his/her resume on LaTex definitely would have worked on Latex before. It could only be to write technical papers and anybody who has attempted to write a technical paper knows the rigor and effort involved in writing them. That conveys a lot to me about the person I am about to deal with. Btw, here’s a cool resume template for Latex http://github.com/sids/resume

]]> By: Abhinav http://riteshnayak.com/blog/2010/04/27/interviews-schminterviews/comment-page-1/#comment-968 Abhinav Wed, 28 Apr 2010 04:40:15 +0000 http://riteshnayak.com/blog/?p=482#comment-968 " Instant brownie points if the resume is LaTex generated. " Really? You think thats gonna give you good developers ? Most probably it will give you impractical developers who insist on solving simple problems the hard way. "I have always felt writing programs is always about algorithmic aptitude, intelligent manipulation and handling of data and optimization. " --- I agree ” Instant brownie points if the resume is LaTex generated. ”

Really? You think thats gonna give you good developers ? Most probably it will give you impractical developers who insist on solving simple problems the hard way.

“I have always felt writing programs is always about algorithmic aptitude, intelligent manipulation and handling of data and optimization. ”
— I agree

]]>