mikej412 wrote: 2 The key is "no experience." In my first job after the Military, the 3rd hire for our team was someone finishing their Masters in Information Systems Management (DePaul University). After 6 weeks, and still not being able to complete his first (and only task), he was let go. The other 2 of us liked the guy, and tried to talk him through his task.... but he "never got it." The funny thing -- we both decided he'd make a good manager someday, even if he didn't have a techie bone in his body (and we also wondered how he got through his techie IT classes).
mysql1988 wrote: Both of these two want a Network Engineering position in an 80% Cisco environment 10% Microsoft and about another 10% linux 1.) Someone with no experience but has a masters Degree in CS OR 2.) Someone with 4 years experience, with no college degree but does have a CCNA and a CCDA and is 1 test away from a CCNP who would you hire?
jdmurray wrote: I would likely hire the person who talks about IT like it's his favorite sports team. Someone who can just talk forever, and in detail, on problems they've encountered and the solutions that they personally discovered and implemented. At least this is one way of identifying creative and experienced programmers. Realize that this method favors interviewees with good verbal skills, and many good people are naturally very quiet and uncommunicative in new environments, so it should not be the only interviewing benchmark used.
jdmurray wrote: I would likely hire the person who talks about IT like it's his favorite sports team. Someone who can just talk forever, and in detail, on problems they've encountered and the solutions that they personally discovered and implemented.
bighusker wrote: The real question is "why the hell would somebody with a masters degree in Computer Science be applying for a network administrator job?" A person with a CS degree would be no more qualified for managing a network than someone with a mechanical engineering degree. If you have a degree in CS and "network management" was a significant part of your curriculum, then your school has badly misnamed that area of study. A grand total of *one* networking/communications class was required for my undergraduate CS degree, and it dealt more with math problems, theory, encoding schemes than any practical knowledge. The rest of the curriculum dealt with studying math, algorithms, programming languages, data structures, compiler/interpreter construction, and some software engineering. So, without any experience, a person with a masters degree in CS and no experience is not even looking for the right type of job. A better question would be if somebody with a masters degree in Information Systems with no experience were to apply for the same job.
Ed Rooney wrote: jdmurray wrote: I would likely hire the person who talks about IT like it's his favorite sports team. Someone who can just talk forever, and in detail, on problems they've encountered and the solutions that they personally discovered and implemented. At least this is one way of identifying creative and experienced programmers. Realize that this method favors interviewees with good verbal skills, and many good people are naturally very quiet and uncommunicative in new environments, so it should not be the only interviewing benchmark used. That's how I try to run my interviews. I get them in my office, give them a coke or a coffee, then tell them to loosen their tie and get comfortable. I'm not evaluating their wardrobe. I ask them a bit about their work experience, but I sort of shape the conversation so that it becomes less of a structured interview and more of a conversation. I avoid the "if you were a bird...." questions and stick to what matters.
Darthn3ss wrote: I'd relocate JUST for an interview that did not include Tell me about a time..." in the interview questions.
petedude wrote: Darthn3ss wrote: I'd relocate JUST for an interview that did not include Tell me about a time..." in the interview questions. Those annoy the life out of me, too. I like to deal with those incident issues as incidents, put them aside, and forget about them-- after those things, it's time to get back to work anyway.
kafifi13 wrote: I'm currently an employer and hire on a daily basis. The best thing to do is give the interview's a Written exam or something that will gauge thier knowledge. You will be suprised what people claim they have in experiance and knowledge but really don't know the info.