Had my interview today. Did I screw up badly?

Had my interview today. I think it went well, met with a lady from HR first, and then an IT manager. I answered some typical questions, some of them your boiler plate interview questions, others were a little more tech related and touched a lot on customer service (it's a desktop support interview). At the end there was a simple quiz that was neither pass nor fail, but let them know where you stood with general IT knowledge. I was questionable on 3, but I looked them up when I got home and saw I blew them:

1. How many bits in a byte? > 8 (answered 4)

2. What's the default subnet for:

Class A networks: 255.0.0.0 (answered 255.255.0.0)

Class B: 255.255.0.0 (255.255.255.0)

C: 255.255.255.0 (255.255.255.255)

Minimum amount of drives for RAID 5? > 3 (i answered 4)

i was nervous and rushing, and flew through them instead of taking my time. Hopefully that didn't screw me too much.

They said there would be a second interview in a couple of weeks. Any ideas what to expect if I get the call?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

ptilsen

I don't know if this is a deal-breaker, depending on how well you did on the whole thing and what they're looking for, but these were definitely softball questions you frankly should have been able to answer.

Depending on the company, the second interview can be a formality to verify what they've already decided (to hire you), a deeper dive into technical questions, a personality/soft skills interview. It could be the final interview, or just the 2nd of several. It's unlikely any of us can guess what you'll have.

My recommendation is to brush up on networking. Look at the Net+ material. And no matter what, keep job searching. There are other opportunities out there, and no good reason to let this one stop you from finding them.

FloOz

It really depends on how the other candidates stacked up. Next time just think each question through, and don't beat yourself up over this interview. I am sure you will have plenty more to come if it doesn't work out.

z3r0cool

There were about 25 questions and these were the only 3 that I felt I missed. I know they're super-easy, I just made some simple errors. The IT manager did say it wasn't pass/fail....

Danielm7

3 out of 25 shouldn't be a huge deal, unless of course the others all got 25/25. For desktop support I doubt you'd really have to know any of these day to day but they are checking general IT knowledge. They might look at what people get wrong and say, "is anyone going to ask him to convert bits to bytes, he's not touching a raid array and we pull IP addresses via DHCP anyway" maybe they will.
Either way, good luck.

NetworkVeteran

For a networking position, your answers to the second questions would have been a deal-breaker. By identifying the mask for Class C networks as 255.255.255.255, you proved you really don't get how subnet masks work. You will be nervous and rushing when your network has problems as well, so that doesn't excuse such errors. Then again, you don't list a Network+ or CCENT, so this is probably not a pure networking position. And your competition likely have gaps in their knowledge, too.

There's no sense beating yourself up. Do your best. Learn from your mistakes. Hopefully they'll call back.

ptilsen

If you got 22/25 that is probably fine from the employer's perspective. I've certainly never seen an employer give out a written technical test and expect 100% correct answers. If anything, more than 80% is pretty good.

If this were out of ten questions and these were what you missed, you'd be in trouble. I don't view these as simple errors, to be honest. Bytes and bits are fundamental, and I don't buy anyone mixing up a byte with a word. The number of drives required for RAID 5 is trivial in and of itself, but not knowing it demonstrates you don't understand how RAID 5 works. This is probably not a big deal for DST, but huge for even a junior server admin. The subnetting thing is again fundamental. If you'd mixed up A and B or something, maybe it could fly, but getting all three wrong and mistaking a single host address (/32) for being a class of addresses again shows you probably don't have a very solid understanding of subnetting. I'm not trying to rail on you or get you down your or anything here. Just trying to reinforce picking up on your weak areas.

Again, you may well have this job. DST generally doesn't require significant RAID or subnetting knowledge. I personally would expect understanding bits and bytes, but depending on the position they might not care about that at all.

z3r0cool

I agree, and it's embarrassing. I do support work now, and I've studied some of the Net+ material so I should have known the subnets without a problem. I don't have any experience with RAID arrays, and the bit and byte thing I should have known.

All of the higher level questions I felt I answered correctly, and I feel like the interview at least went well. I guess we'll see.

Thanks for the input.

About7Narwhal

I would have missed the bits and bytes thing, but I did remember that it was a Nibble that = 4 when I saw the correct answer. The only reason I know the subnet things is because of my 70-680 and same goes for RAID 5.. I know it because Windows 7 does not support SW RAID 5. Someone earlier said you didn't list as a Net+ or CCNA and I do think that holds water, but they are still simple things that we should know.

Either way, I wouldn't worry about it. If you felt those 3 were the only ones with issues and the interview went well, then they might consider it a pass. Time will tell.

networker050184

Ouch, never good to miss the really simple ones. Fundementals are a huge deal to me when interviewing. If those are the only ones you missed you likely aren't out of the running though. Learn from this one and be ready next time!

Darril

Many hiring managers understand that someone can get nervous and as the interviewer mentioned, tests like this aren't pass or fail (unless you really bomb it). Part of the interviewing process is also to determine how someone interacts and if they can get along with others.

Good luck.

RouteMyPacket

What is this job for again?

The Bad:

Not being able to identify your subnets was definitely not good. It simply showed a lack of experience IMO.

RAID disk requirements, again a lack of experience

Not knowing amount of bits in a byte, pretty basic question..could chalk this up to nerves maybe

The Good:

An interview isn't always about answering every single question in the fashion the interviewer would like. Of course they want to hear the right answer but even more important is listening to your thought process, do you know it but just aren't able to articulate the answer or do you really not know and are trying to BS them?

It's as much about getting a feel for your thought process as it is testing your technical knowledge. Also, IMO it say's a lot about a potential employee who has the humility to state right off the bat that they don't know the answer instead of trying to BS around it.

I would be more comfortable with bringing someone into my environment who knows they don't know it all and that will ask a question versus someone who thinks they know it all and will push and click buttons without asking.

In closing, you did fine. Use this a learning experience. Good luck!

z3r0cool

RouteMyPacket wrote: »

What is this job for again?

Desktop Support Specialist.

RouteMyPacket wrote:

The Bad:

Not being able to identify your subnets was definitely not good. It simply showed a lack of experience IMO.

RAID disk requirements, again a lack of experience

Not knowing amount of bits in a byte, pretty basic question..could chalk this up to nerves maybe

The Good:

An interview isn't always about answering every single question in the fashion the interviewer would like. Of course they want to hear the right answer but even more important is listening to your thought process, do you know it but just aren't able to articulate the answer or do you really not know and are trying to BS them?

It's as much about getting a feel for your thought process as it is testing your technical knowledge. Also, IMO it say's a lot about a potential employee who has the humility to state right off the bat that they don't know the answer instead of trying to BS around it.

I would be more comfortable with bringing someone into my environment who knows they don't know it all and that will ask a question versus someone who thinks they know it all and will push and click buttons without asking.

In closing, you did fine. Use this a learning experience. Good luck!

Thank you!

PurpleIT

RouteMyPacket wrote: »

Not knowing amount of bits in a byte, pretty basic question..could chalk this up to nerves maybe

The good news is the OP didn't choose 17 or some off the wall number; I mean it's still hard to explain, but you can rationalize it if you try hard enough.

Whatever happens I can assure you these are three questions the OP will not forget anytime soon.

z3r0cool

PurpleIT wrote: »

Whatever happens I can assure you these are three questions the OP will not forget anytime soon.

Understatement of the decade.

RouteMyPacket

z3r0cool wrote: »

Desktop Support Specialist.

Thank you!

Asking someone going for a Desktop role subnet questions is odd. Do you happen to have stated any networking experience on your resume? I ask because it could have been asked as a bonus just to see where you are in networking. I wouldn't sweat it at all IMO.

Asking you about subnets is as valid as asking a Sys Admin how to redistribute BGP into EIGRP. Recruiters and people in general need to look at IT like doctors. Would you visit a neurosurgeon for heart surgery? Would you ask a cardiologist about a nuerological tumor?

nicktornetta

I think they just wanted to get a general idea of where you are. I mean if you didnt know what ghosting a machine was, if you didnt know physical layer or troubleshooting questions, and particularly if you are bad with service (which is a large part of what a desktop support person will do), those are probably more deal breakers than the networking questions. For desktop support, A+ is a very good cert to start with, followed by Network+ as others have mentioned.

z3r0cool

RouteMyPacket wrote: »

Do you happen to have stated any networking experience on your resume? I ask because it could have been asked as a bonus just to see where you are in networking.

A bit. Our network is entirely static IP's. But the majority of the machines are Class C, which takes the default subnet mask that windows supplies when you tab through the applet. I know some of the icmp commands and protocol ports and have stood along side some of our engineers when they configured our ASA's and L3 switches. I've even set addresses for some cisco switches to open them up, and had to learn a few ios commands but I admit, I don't extensively deal with networking on a day to day basis.

As a popular saying goes, I know just enough to be dangerous.

z3r0cool

nicktornetta wrote: »

I think they just wanted to get a general idea of where you are.

Those were his exact words actually

nicktornetta wrote:

I mean if you didnt know what ghosting a machine was, if you didnt know physical layer or troubleshooting questions, and particularly if you are bad with service (which is a large part of what a desktop support person will do), those are probably more deal breakers than the networking questions. For desktop support, A+ is a very good cert to start with, followed by Network+ as others have mentioned.

Those are subjects that I was able to touch on as I handle a lot of that daily. I also tried to stress the importance I place on service. They have mentioned the subject in an off handed way; I took the opportunity to show that I know the importance.

Akaricloud

If there were only like 5 questions and you missed those 3 I'd be concerned, but 3/25 is pretty good!

For a position like this I would expect a person to miss some of the basics but understand most of them. In a Desktop Support position I don't really see you using any of these three missed topics directly so you should still be in good shape.

I personally would try to convey exactly what you have here: You feel you shouldn't have missed those but have clearly found the right answers and care about learning. Everyone lacks some knowledge and makes the occasional mistake but good techs use these situations as opportunities to expand their knowledge. If you have a chance to convey this you should be in real good shape.

z3r0cool

I couldn't have been too terrible, I just got an email from HR regarding a second interview next week!

silverp1

z3r0cool wrote: »

I couldn't have been too terrible, I just got an email from HR regarding a second interview next week!

Congrats! Good luck!

About7Narwhal

Awesome news!

z3r0cool

Thanks guys. In your experience, what's the 2nd interview mostly about? I'm definitely going to review the basics before I go in. I was thinking it may be more situational questions related the job and maybe personal questions to make sure I'm not some weirdo that won't fit in?

About7Narwhal

Depends on the company. My experience has been that the second interview with be with your potential manager's boss. In those cases it is more about company questions and less about technical.

PurpleIT

z3r0cool wrote: »

I couldn't have been too terrible, I just got an email from HR regarding a second interview next week!

First of all, congrats!

What does everyone on here think about bringing this whole issue up during the 2nd interview? IMO, it could be a very good thing if done correctly.

"You know, I think my nerves got the best of me during that test and I walked out thinking I made a couple of silly mistakes. I went home, double-checked the answers I thought I missed and sure enough, I can't believe I made those simple mistakes".

To me, that says here is someone that knew what they missed, took corrective action and owns up to it.

Thoughts?

About7Narwhal

I think that would be fine only if the topic is brought up by the interviewer. No need to bring up something the interviewer may know nothing about. But if he / she asks, it is a great opportunity to turn the mistakes around and show that even after all was said and done, z3r0cool followed up and learned the correct answers.

z3r0cool

About7Narwhal wrote: »

Depends on the company. My experience has been that the second interview with be with your potential manager's boss. In those cases it is more about company questions and less about technical.

You're right, the meeting is with the IT Director. I met with the IT Manager for the first interview. Can you be more specific about the company questions? As in, what the company is about, doing, and where it's going?

I definitely would let sleeping dogs lie and not bring up my poor testing.

About7Narwhal

It could be anything, honestly. My final interview wasn't an interview of skill or knowledge at all. What are you doing with your life? What are your five year goals? What is your opinion of the economy? Do you belive the 401K plan is valuable? Some of them were really off the wall. Others were beyond my particular scope of knowledge: We might deploy this type of change to our Data Center. Do you think it will provide beneficial results?

I would assume questions like the following might be in there though:

What are your short term and long term goals?
Why do you think you are the best fit for our company?
What do you except the company to provide you? or Why do you think our company is the best fit for you?
Can you name a time when you made a mistake at work? How did you deal with / resolve the issue?
Can you describe a time when you and a Co-Worker did not agree on something? How did you resolve the disagreement?

I have had those questions in a fair share of my interviews. There is no rule saying they cannot ask technical questions though, so be on guard for anything.

Darril

Congats on the second interview invite. It might also be focused on what you think you can bring to the company.

You might like to review the advertisement to see what they're looking for and see if you can include those words in your responses.

I don't know the company you interviewed with but the process sounds very familiar. If it's the company I'm thinking about, you might be asked about your willingness to work overtime. I would also expect you to be asked about a frustrating experience with a customer and how you handled it. You might even be asked to handle a fake trouble call and be judged on your ability to keep your cool even if the customer is frustrated and having problems keeping his/her cool.

Good luck.

z3r0cool

Well folks, it looks like everything is working out nicely. I was offered the job last night and went in today to sign my offer letter, contingent on a successful background check and negative result on drug screening.

I don't think I'll have a problem with either; I don't do drugs and my current facility requires you to maintain a certain standard for background history. I did have a DUI almost 10 years ago, though. They didn't ask me to divulge anything so I didn't.

I'll point out one thing that I learned from the hiring process: people skills are just as important as technical skills for those of you pursuing help desk/desktop support roles. The HR manager kept going on about how important customer service was to them. I picked up on that and tried my best to stress how much I believe in CS and how important it is. After they offered, she said that was one of the things that most impressed them.
The soft skills are just as important as the technical ones.