Hey, calm down. I'm not attacking you. You asked for input and feedback, and that's what I provided, calmly and speaking from several years experience. I am curious what your work experience in hiring has been, as I haven't seen you mentioned actually working HR before.
To address a couple of your concerns directly.
1) I never said our method is perfect - none is - but it demonstrates a documentably lower "bad hire" rate. It is still possible to make a bad hire.
2) Not every respected developer in the world uses OOP. It's one of six major paradigms, and it is perfectly possible not to fully grasp it at many different experience levels. That's speaking from factual observation, not just grasping at straws.
3) Pushing code under a stressful deadline isn't a management decision, it's a naturally occurring circumstance with some projects.
I was present in many interviews along with HR to ask technical questions. That's all. Our whole team participates in the interview process; sometimes its our team lead and me, sometimes it's the team lead and one or two others.
Although, I had some interview experience from a past job which is not related to IT.
In this world today, we have standards almost for anything. I am just asking for one more standard for job interviews (particularly for IT). That's all what I am asking for. You might be a great interviewer, but certainly others are not. An interview standard would make things much professional for both interviewers and interviewees.
As a developer/interviewee, I really do not know what kind of knowledge I should memorize and carry with me in my head to the interview.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey, calm down. I'm not attacking you. You asked for input and feedback, and that's what I provided, calmly and speaking from several years experience. I am curious what your work experience in hiring has been, as I haven't seen you mentioned actually working HR before.
To address a couple of your concerns directly.
1) I never said our method is perfect - none is - but it demonstrates a documentably lower "bad hire" rate. It is still possible to make a bad hire.
2) Not every respected developer in the world uses OOP. It's one of six major paradigms, and it is perfectly possible not to fully grasp it at many different experience levels. That's speaking from factual observation, not just grasping at straws.
3) Pushing code under a stressful deadline isn't a management decision, it's a naturally occurring circumstance with some projects.
I am calm :D and I appreciate your opinion.
I was present in many interviews along with HR to ask technical questions. That's all. Our whole team participates in the interview process; sometimes its our team lead and me, sometimes it's the team lead and one or two others.
Although, I had some interview experience from a past job which is not related to IT.
In this world today, we have standards almost for anything. I am just asking for one more standard for job interviews (particularly for IT). That's all what I am asking for. You might be a great interviewer, but certainly others are not. An interview standard would make things much professional for both interviewers and interviewees.
As a developer/interviewee, I really do not know what kind of knowledge I should memorize and carry with me in my head to the interview.