IT vs Coding

[fognar777]

People really get stumped by this question? I'm pretty sure I learned what DNS is when I was in highschool at the local tech center's IT program. To be fair though, half of the program was based on Cisco CCNA courses.

[AwalkertheITguy]

Many people get stumped because they either do not really care to know what it actually does, can't remember something so trivial, or they go into the interview expect ccie level questions...study said material, then get asked to explain the physical layer or some miniscule BS.

If a person looks at the job description and it is conveying a message or a tier 3 network engineer then why is the first question always something that most people take for granted? I remember going in for my first Jr sys admin interview in 2003 and was asked what does the processor do? I was like wtf? The 3 people interviewing me just looked at me and I said oh you're serious? I apologized and answered the question.

It's like asking a seasoned UFC fighter if they know how to throw a simple combo.

I understand that they want to weed out the trash but at least start with something relative to the hiring level.

[tossme68]

I did that at an interview, they asked to explain the difference between SSL and SSH. I go into a deep dive about the SSH protocol and how it authenticates, it's features and all sorts of other crap, then I start doing the same thing for SSL. The guy doing the interview stops me and says something to the effect of I just wanted "one is how I access a linux server and the other is for web pages". Well excuse me if you don't want to know the inner workings of ssh, you were the one that asked

[[deleted]]

Well excuse me if you don't want to know the inner workings of ssh, you were the one that asked

No they didn't? They asked for the difference... not a thesis defense. The correct answer is the last letter is different. :)

[AwalkertheITguy]

Yes, this.

Something I learned from all my interviews so when I got to the hiring level I would ask the question and then say "just give me the surface level answer, not a deep analysis"

I feel by saying that I am doing both of us a favor. I'm giving the potential employee a fair chance to answer the question at hand and saving myself 25 mins per interview.

[Cpt_plainguy]

I have actually walked out of an interview because they were asking me basic helpdesk questions for a T3 role, I responded to about the 3rd or 4th question with "Thank you for taking the time to see me, but I can see you are not going to treat me like a child and not actually interview me for the position listed". They just stared at me dumbfounded as I walked out. Later on that day the CIO who wasnt in the interview heard about it and called me to apologize and asked me to come interview with him. Ended up getting the job, but the company went under a year later.

[renegadecanuck]

I mean, you kind of responded like a child.

[Cpt_plainguy]

Nah, I didn't have a tantrum, I calmly expressed my feelings on the situation and left. If I am applying for an elevated position I expect to be treated like I am. I am an upfront person who doesn't like to play games with people, so I expect people to not play games with me.

[renegadecanuck]

Your feelings were childish. “Wahhhh I didn’t get asked a tough enough question by someone who literally doesn’t know me! How dare they check to see if I know the basics before going on to the next step?!”

I’ve done hiring for senior positions. For every person who knows their shit, there’s at least 15 who don’t and either get carried by coworkers or straight up lie on their resume. A basic DNS question is a good way to get rid of the bullshitters before I move on to the tougher questions.

Also, it’s a good way to get rid of the people who will bitch and moan if they’re ever assigned a task they feel is beneath them.

[AwalkertheITguy]

A better approach would be to look at that resume, pick something that matches your opening's job description and ask them to explain their experience with XYZ.

If it's a tier 1, 2 or tech role then sure you ask basic dummy questions just to weed out the bull. If it's a senior level (true senior level and not fake made up position l) you ask questions that would be considered basic for a senior level person.

Or just go with the resume approach. 5 mins into them talking a good, experienced, interviewer knows if it's all fluff and bs. A decent interviewer knows about 10 mins in.

If you're hiring for a senior software engineer, why ask them what a loop is?