I ended up asking him very close to #6 actually. I did a very open "A
user calls and tells you they can't log in, what do you do?". This guy
assumed (as many probably would) that I meant "log in to the network".
Since I have got these very ambiguous calls I know "can't log in" can
mean network, application, website, or God-only knows what - which of
course tests what Klint lists and then some - it was fun!

 

Next was the PEBCAK one.

 

Next up was "you've been asked to deploy new-to-our company software on
15 machines, what steps do you take?" Follow up was "What if you got the
same request except 100% of our desktops needed it".

 

Dave Lum  - Systems Engineer 
[EMAIL PROTECTED] - (971)-222-1025
"When you step on the brakes your life is in your foot's hands" 

 

From: Klint Price - ArizonaITPro [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 09, 2008 1:26 PM
To: NT System Admin Issues
Subject: Re: Interview Q ideas

 

I like doing what-if scenarios in interviews

For example in #6, a user states their PC is not on connecting to the
Internet, how do you isolate the problem?

This shows how well they know their stuff on the net side of things.  As
they isolate the problem down one branch, take care of some assumptions,
and have them walk down the next branch.

*       how long has it been down
*       did you do anything
*       laptop vs PC (think hardware profiles)
*       is there a link light?
*       repair
*       ipconfig

        *       valid ip
        *       dhcp

*       ping router?

        *       vlan changed
        *       ping next hop up
        *       icmp blocked

*       nslookup

        *       is IP not responding or DNS?

*       proxy server?
*       dns cache / dnsclient
*       software firewall
*       swap network cards / update driver
*       does other PC work?
*       Does PC work in other switch port
*       was vlan changed?


Za Vue wrote: 

Dave,
 
Use some the questions they used on you when you started out. The
questions
may also depend on the required job experience and education. 
 
I will interview candidates soon for a desktop position too. Some
general
questions that I have in mind are:
 
1) What are key accomplishments have you attained that you can tell us?
2) How do you handle an angry customer?
3) How will you install operating system in more than 50 PC's at a time
when
the all PC's having same configuration?
4) What is the different between POP & IMAP? How do they work?
5) What is the different between FAT/FAT32 and NTFS?
6) Explain how you go about troubleshooting a computer that has no
network
connectivity?
7) What role do you think q desktop support analysts should play in the
company?
8) Can you explain DHCP works?
9) What operating system do you prefer and why?
10) What steps can you take to secure a stand-alone workstation?
 
 
 
-----Original Message-----
From: David Lum [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 09, 2008 11:18 AM
To: NT System Admin Issues
Subject: Interview Q ideas
 
We are interviewing for a desktop support position - not an "entry
level" spot, but someone with a couple years experience. I would LOVE to
have a clever, unexpected, yet relevant-to-the-position question. Do you
guys have anything I can use?
 
Dave Lum  - Systems Engineer 
[EMAIL PROTECTED] - (971)-222-1025
"When you step on the brakes your life is in your foot's hands" 
 
 
 
 
~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>
<http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>   ~
 
 
 
 
~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>
<http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>   ~
  

 

 

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to