Interviewing: The other side of the table.

Hey Friends,

It’s been a while since I have made a post, I have a lot to write but I have been bit busy with work, family, friends and some side projects. Today I want to dedicate this post to “Interviewing“.

In my new job I have been given an opportunity to interview people for various roles. Not sure about you, but I still have memories of my interviews (all good and bad, stupid and smart) and therefore I know what it’s like to give a technical interview for a job and now I know what it’s like to take one. I feel I shall share my early experience with you. I have not counted them all but I have taken some tech interviews till now and overall I feel, I have collected some knowledge that I can share with you guys.

While all this is good and I feel esteemed to do so, It’s also bit of a concern, specially when I know that the person I am interviewing has twice the experience I have and sometimes is going to be designated a role higher than me. I mean, what do you ask a candidate like that? Are my questions going to be too easy for them? And this sometimes apply to guys whose resume and projects looks outstanding. So after some early experience for me It turns out that it does not matter. If your questions are reasonably sound and tests basic knowledge, you can test the deverloper/problem solver in them. I have had people from fortune 500 companies do massive blunders when they write code on board and yes I have had people write error free compilable code on white board for the same questions. No, the questions were not given from “Crack the coding interview” or similar :). Sometimes I see someone making mistakes that I made or may be still make and sometimes I see a totally different approach that I didn’t thought of and it gladly surprises me. I have also had some bad interviewers interview me and I try not to be one myself during the interview.

The point is, If in your job, you are trusted to interview some one, feel proud, feel glad that you are given an opportunity like that but prepare/spend some time thinking about your questions and knowing about the person. In an interview you sort of are the representative of the company to that person, It becomes your duty to give the best of yourself, they do not know the company yet, but your approximate forty five minutes with them can give a general sense of type of people working in your company.

In all, I feel every developer should get a chance to interview other people in course of their career, Doing it the right way can give you insights about your mistakes in the interview and it also gives you a chance to represent the name on the door that you walk in every morning, five days a week.

Share your experience and stories in the comments.
Happy Coding.

Leave a Reply

Your email address will not be published. Required fields are marked *