Got an interview for system admin position tomorrow....
Rockets34Life
Member Posts: 122
Lucked out to get an interview for a sys admin position while I'm at my current job....
The guy from the agency told me even though the job description says they are looking for certain things, he told me to not worry about my lack of sys admin experience and that this is a Jr.-to-Midlevel/"eager to learn, make it up by giving your all" type of system admin position. I'm like yeah right.....I'm going to get grilled for stuff I don't know, but it's an opportunity I don't want to pass up career wise.
But before the interview, I had to take 3 exams so they can see where my knowledge was for Server 2003, Exchange 2007, and Active Directory. So not to **** myself, I went through all exams without surfing for the answers. Active Directory, I did whatever I could knowledge wise with my class time and work experience. Was average with that. For Server 2003, whatever I could remember from class and just guesses. Exchange exam, all guesses. I saw the scores and I thought they were crap.....but the guy from the agency said I scored average which was fine to the employer to grant me an interview.
So here's what the guy at the agency sent me to prep for the interview (my answers in bold):
1) They will start off the interview asking you about your background and go over your resume. Be sure you are aware of everything listed on your resume so that you can be sure to articulate and elaborate in detail. This is fine, I can do my best on this.
2) They will ask you about your virtualization background. They use Hyper-V. Heard of this, don't know squat about it and haven't worked with it.
3) They use Service Desk Plus as their trouble ticketing system. Experience with your background using ticketing system and working through resolution. This is no problem to me since I've worked with ticketing systems for 10 years
4) Experience with Monitoring Software- They use Op Manager Don't know squat about it and haven't done it before.
5) They will ask the typical top strengths and weaknesses interview question. Be prepared to expound upon that question I can mention strengths, but what are good weaknesses I can mention that can make them think that they are also strengths?
6) Explain your comfortability level doing Windows Server Administration and using Active Directory. Active Directory, I have worked with a lot in the past 1 1/2 years from my last job and this job, but only working with user accounts and groups. Windows Server Administration - don't know what they mean by this.....I'm thinking building, designing, implementing servers, which I haven't done before. I have remoted to servers to setup printers, manage directories/permissions, disk space issues, etc. but that's about it.
7) Discuss your scripting experience Don't know squat about it and haven't done it before.
8 ) Why you want to work there? What have you guys said in your interviews for this question?
9) Explain your experience with Dell Hardware and Switches. Don't know squat about it and haven't done it before.
He told me the pay was $50K, full-time, perm (he said he will try to knock up the $ a little more, but I doubt he'll get anywhere with my background - dude wants to get paid!).
I understood the pay and I told him before even saying yes to the interview that to not expect much since I haven't done much with sys admin work (I know I'm belittling myself, but I've been burned before from one of my previous jobs and I don't want to go into a situation where I'm going to screw myself if the company doesn't want to invest/train me for skills I'm lacking that I have brought upfront). He said that's fine and to do my best in the interview.
What do you guys think? Any advice?
Sorry for the long post....
The guy from the agency told me even though the job description says they are looking for certain things, he told me to not worry about my lack of sys admin experience and that this is a Jr.-to-Midlevel/"eager to learn, make it up by giving your all" type of system admin position. I'm like yeah right.....I'm going to get grilled for stuff I don't know, but it's an opportunity I don't want to pass up career wise.
But before the interview, I had to take 3 exams so they can see where my knowledge was for Server 2003, Exchange 2007, and Active Directory. So not to **** myself, I went through all exams without surfing for the answers. Active Directory, I did whatever I could knowledge wise with my class time and work experience. Was average with that. For Server 2003, whatever I could remember from class and just guesses. Exchange exam, all guesses. I saw the scores and I thought they were crap.....but the guy from the agency said I scored average which was fine to the employer to grant me an interview.
So here's what the guy at the agency sent me to prep for the interview (my answers in bold):
1) They will start off the interview asking you about your background and go over your resume. Be sure you are aware of everything listed on your resume so that you can be sure to articulate and elaborate in detail. This is fine, I can do my best on this.
2) They will ask you about your virtualization background. They use Hyper-V. Heard of this, don't know squat about it and haven't worked with it.
3) They use Service Desk Plus as their trouble ticketing system. Experience with your background using ticketing system and working through resolution. This is no problem to me since I've worked with ticketing systems for 10 years
4) Experience with Monitoring Software- They use Op Manager Don't know squat about it and haven't done it before.
5) They will ask the typical top strengths and weaknesses interview question. Be prepared to expound upon that question I can mention strengths, but what are good weaknesses I can mention that can make them think that they are also strengths?
6) Explain your comfortability level doing Windows Server Administration and using Active Directory. Active Directory, I have worked with a lot in the past 1 1/2 years from my last job and this job, but only working with user accounts and groups. Windows Server Administration - don't know what they mean by this.....I'm thinking building, designing, implementing servers, which I haven't done before. I have remoted to servers to setup printers, manage directories/permissions, disk space issues, etc. but that's about it.
7) Discuss your scripting experience Don't know squat about it and haven't done it before.
8 ) Why you want to work there? What have you guys said in your interviews for this question?
9) Explain your experience with Dell Hardware and Switches. Don't know squat about it and haven't done it before.
He told me the pay was $50K, full-time, perm (he said he will try to knock up the $ a little more, but I doubt he'll get anywhere with my background - dude wants to get paid!).
I understood the pay and I told him before even saying yes to the interview that to not expect much since I haven't done much with sys admin work (I know I'm belittling myself, but I've been burned before from one of my previous jobs and I don't want to go into a situation where I'm going to screw myself if the company doesn't want to invest/train me for skills I'm lacking that I have brought upfront). He said that's fine and to do my best in the interview.
What do you guys think? Any advice?
Sorry for the long post....
Comments
-
afcyung
Member Posts: 212
It seems like an open book test. While you lack the exp on the software there isn't anything stopping you from doing some research and knowing the general information about the software they use. The answer I would provide is to give general info about Hyper-v and then explain that you haven't used it before. Being honest is the best thing to do. -
Rockets34Life
Member Posts: 122
It seems like an open book test. While you lack the exp on the software there isn't anything stopping you from doing some research and knowing the general information about the software they use. The answer I would provide is to give general info about Hyper-v and then explain that you haven't used it before. Being honest is the best thing to do.
I didn't think of it as an open book test. I didn't want to ace the exams and prove to them my answers in the interview. I wanted to be open and honest and do my best with the limited knowledge I know of the topics. I wanted to give them the real me because in the long run, if I had some how pass the interview going open book, they will expect me to know that stuff w/o any help.
I was going to be honest in the interview process from the start. I just want to do it in a professional way where I can counter with answers with the questions I have zero experience to. That way they can give me a shot so I can prove to them that I will work my tail off and that I have a passion to learn system administration. -
pham0329
Member Posts: 556
Rockets34Life wrote: »I didn't think of it as an open book test. I didn't want to ace the exams and prove to them my answers in the interview. I wanted to be open and honest and do my best with the limited knowledge I know of the topics. I wanted to give them the real me because in the long run, if I had some how pass the interview going open book, they will expect me to know that stuff w/o any help.
I was going to be honest in the interview process from the start. I just want to do it in a professional way where I can counter with answers with the questions I have zero experience to. That way they can give me a shot so I can prove to them that I will work my tail off and that I have a passion to learn system administration.
I disagree. Unless the "real" you doesn't do research before you implementing changes, products, or technologies, I don't see a problem with reading up on the subject before the interview.
While you may not know the technolgies listed above, it shows that you took the initiative and you have the drive to go and learn it. Having a high level understanding of something is a lot better than "don't know squat" about it.
When I was interviewed for my current position, there were a lot of technoligies that I was not aware of (CallManager, Hyper-V Live Migration, HP SANs, SCOM, SCCM, LYNC, etc) but because I showed that I at least knew what they were, I was chosen for the position (well, among others considerations). No one is going ot expect you to come in and know everything about every single piece of software/hardware they use, but you should at least be aware of what it is and be willing to learn it. -
pzero
Member Posts: 192
I know when ive applied for positions, if I dont know/understand a technology that is being advertised in conjunction with a position, Ill research it. If it comes up in the interview, you can at least have some knowledge of what is being talked about.
Be honest in the interview by saying "Whilst I not have not used that tech before I looked it up and know what it used for etc". It shows a bit of initiative.
Good luck with the interview -
LordQarlyn
Member Posts: 693 ■■■■■■□□□□
If I was expected to know everything about every piece of technology for a particular job, I'd never gotten hired.
By all means, research the stuff!! I can cite at least two jobs I did get selected, because I researched all the systems that were listed in the posting. One of them, I was specifically told by the hiring manager, that I was the only one who gave an accurate description of a specialized radio tool, which told him that I was the only one who bothered to research it, therefore I stood out - in a good way.