breh you a hiring manager right?? What do you do when the person you are interviewing is nervous as hell and fukks up the interview even though that person might be qualified for the job?
I generally have a first 4 question rule as in you have to get all of the first 4 questions right. These are not hard questions, these are just typical questions you have to know the answer to just to work in the section of IT I do. I feel like if a candidate cannot answer these first 4 fluff industry questions, then they cannot answer anything after that. I work in virtualization, so if someone can't tell me what a vmotion is, they sure as hell can't tell me why you want to have vmotion network traffic separate from everything else, or how to separate it.
As far as being nervous, I don't really pay attention to it. A job interview is a high pressure situation for both parties. It is a high pressure situation for the candidate because they are looking for a new job, generally for a reason that is pretty serious to them ( trying to break into the industry, job they have sucks, they got laid off ). Contrary to popular belief by IT workers it is also a high pressure situation for me, because I either have to replace a guy who left or moved to another group ( and his work is just sitting around not being done ) or I got to hire a new guy because our work load increased ( and all my guys are starting to feel overworked and shyt if I don't get someone in here soon then they are going to start leaving ) or some manager over my head passed some corporate mandate that says "grow your team" and I got some HR person standing over me saying "you got your group up to 13 people yet?" So I am expecting the person to be nervous, I am expecting them to cross up some words. Now if it is something that is overt...and I have had people who get overtly nervous, I interviewed a dude one time who literally passed out, I interviewed a dude who started sweating so bad that it literally started pooling in his chair and falling on the floor, if it is something that bad then I cannot hire that person. If they get that nervous over an interview, what will happen if I hire them and they got a deadline to meet with a bunch of people emailing them saying "you know if we do not deliver tomorrow we lose a 5 million dollar contract right?"
To me if the person fukks up the interview then they are not qualified for the job. There is more to an interview than just answering technical questions. There is more to IT than just knowing technical stuff and being good at it. I would say unless you get to the super duper senior level where you have to be a walking wki page for whatever your IT discipline is, the actual art of being smart and knowing the technology is maybe a 3rd of what you really need to make it in IT. Most IT people do not take the time to really develop problem solving and people skills, and in IT that stuff will take you way further career wise than being some guy who can re-write the entire inventory application using powercli...
The only exception to that rule, again, is if you get to the super senior level. When I do an interview for those jobs I only care what you know and that is it, any other personality traits, as long as they don't strike me as severe, I ignore. In most IT disciplines once you reach the Engineering \ Architect level you are just being a walking dictionary all day and the only thing people expect of you is to spout out some random technical stuff on command and by that time you have seen so much IT shyt and worked so many projects that you can find the problem with an issue in a fraction of a time it used to take you.
When it comes to interviews, especially for people breaking into the field, I would say go on as many as you can. Doesn't matter if you are over qualified, under qualified, go to it. Do well at it. Bomb at it. But go on a ton of them to get familiar with the questions asked. Most IT interviews are going to be some standard industry questions and then some questions internal to how that company does things. You want to be able to nail those standard industry questions at the drop of a hat and you can only do that with practice.
what do u mean breh? is the virtualization route now the way to go? because literally everyone is telling me that is the route to go.
Have to create a linkedlist and a hashtable from scratch, no references to the built in classes. Senioritis is too strong for this.