
Originally Posted by
chris_fuel
Well, the specifics on the interview process will depend on what type of job you're dealing with. However, there are a few things to keep in mind:
1) Does this person know anything about the company?
Did you give them a web page or something to look at to describe your company? If so, figure out how much they've learned. Not much of a response? Might be a flag of a "safety interview" in case another job offer goes sour.
2) Do you feel like punching them in the face?
Humor aside, a somewhat overly tight person with little regards to humor might create a somewhat agitated work environment. Do they smile at all during the interview? Laugh at jokes? If you've got someone on your time that's kind of agitated all the time, other workers could potentially be spending more time thinking about how much they hate him than the next project's requirements.
3) Working independently
Yes, it's going to be most likely a team environment. However, strong independent thinking is also a plus. Someone who constantly has to tap into the knowledge of others loses time for the project, as well as the other person's time. If it's something that needs a lot of constant attention, well you've got meetings to get as much as possible out of the way.
4) Don't take quitting/2 weeks or fired as an instant throwaway flag
Someone quitting gives an obvious sense of lack of motivation for a job, but first figure out why it occurred. It may be something completely out of their control. If you throw someone perfectly suited for the job out based on this, you could have lost a key player to your team.
5) Do research yourself on the position
Look around at what people are expecting known for the job position. Even look around like you were applying for it yourself. In tech areas, look for standards that they should adhere to and see if they know said standards.
6) Look for buzzwords
As part of 5, figure out what the common acronyms and buzzwords are and how they relate to the position. If someone pulls like HTML, CSS, XML, SOAP, REST, etc. make sure they can actually expand them out and aren't just putting them up for kicks and giggles. Same goes with management or any other type of position.
If you want to throw out what type of position it is, I can look and see if there's anything else I can add.
Bookmarks