Upload

Published on May 2016 | Categories: Documents | Downloads: 44 | Comments: 0 | Views: 370
of 4
Download PDF   Embed   Report

Comments

Content

General Questions Q. What desktop operating systems are you familiar with? A. Before you answer this question, you should have some background information on what operating systems are used within the organization you are interviewing with. Undoubtedly, you will be asked to elaborate on your skill set with each of these operating systems so it s best to tailor your elaboration to the operating systems that are relevant to the hiring manager. This being said, don t leave out mentioning experience in other operating systems. You never know whether the com pany may be evaluating the migration to a different OS. Q. Have you used imaging software before? How do you find these tools useful? A. Automation tools are an important part of your job as a desktop support techn ician. Elaborate on the tools that you ve used. Hiring managers want to assess you r in-depth knowledge and experience with using these tools. This means talking a bout how you use their various feature sets. (If you have an opinion, you probab ly know the product pretty well.) Q. What are the pitfalls of using imaging software? A. This question is meant to assess how well you know these products. For exampl e, discussing the importance of testing the image demonstrates that you use thes e tools on a regular basis. Q. Have you used any software distribution tools? If so, which ones and how were they used? A. Like imaging software, software distribution tools are an important part of y our job. Hiring managers are looking for knowledge that these tools exist and ho w they can be used to support your organization. Q. What do you like most about desktop support? A. Hiring managers are looking for what motivates you. Hopefully your answer wil l match the characteristics of the job: being busy, working with different peopl e, and the challenges of learning new operating systems and configurations. Q. What do you like least about desktop support? A. The hiring manager is testing whether you will fit in with the existing team. An appropriate answer here would be not being able to resolve a problem in a ti mely manner for reasons outside your control, such as hardware failure. Stick to things outside of your control for the best response. Q. When solving a desktop problem, do you prefer to work peers, or on your own? A. This is another question to determine your fit within g managers understand that to be successful as a support e to work in a team environment. This means working with s, and end-users on a constant basis. with the end-user, your the organization. Hirin technician you will hav other employees, vendor

Q. Can you describe a situation where you have had to deal with a difficult pers on? How did you handle it? Would you do anything differently? A. Desktop support can be very demanding some days. End-users only see their own priority needs and often are not interested in other demands on your time. This question explores how you deal with a difficult end-user by understanding their problem, assessing priorities, and communicating a timeframe for resolution. Of ten good communication can help both sides come to an agreement. Make sure you h ave an example with a successful outcome. Q. How would you say you are able to handle stress? A. Hiring managers are looking to see what coping techniques you can draw on to deal with stress. Sometimes from the answer, they can also determine whether you are prone to stress. When responding, some techniques for handling stress that

you may want to talk about include continually evaluating what s on your plate and prioritizing, communicating with your manager on what your priorities are, and making sure that you take a break to reenergize, particularly at lunch time. Q. What do you see yourself doing two or three years from now? A. Hiring managers want you to stick around. They realize that you will not be i n this position forever, and they want to make sure there s a desire to move up wi thin the organization as well as the right fit. They ask this question to see wh ether there s a growth path for you possible within the organization. As a desktop technician, natural growth paths are team leads, quality assurance, engineering positions, and entry-level development. Be honest about where you want to be in two to three years, and ask the interviewer whether they see your career path a s a possibility. Q. How do you learn new technologies? A. Learning is an inherent part of the job. Hiring managers one who enjoys learning technology on their own and who has k for training opportunities. Besides the traditional books get to include user groups, eLearning subscriptions, and IT uch as CramSession. are looking for some the foresight to loo and manuals, don t for professional sites s

Q. How do you prioritize tasks and manage your time? A. What hiring managers want to know is whether you have time-management skills. Everyone manages their time differently, but think about how you handle e-mail, when you check voice mail, how you respond to pages, when you research and docu ment, and how you pick up new trouble tickets. Q. Imagine the following situation: you receive three simultaneous calls from th ree vicepresidents who need assistance immediately. How do you manage these conf licting priorities? A. Obviously this is a trick question. What the hiring manager is trying to asse ss is how you set expectations with each of the individuals, knowing very well t hat you won t be able to assist all of them at the same time. They are also lookin g for how you will prioritize each of these incidents, including seeking assista nce from peers and supervisors in order to meet user expectations. Don t allow the tyranny of the urgent to divert you from managementestablished support priorities . Q. How would you handle a user who continually misdiagnoses their PC issues? A. By asking this question, the hiring manager is assessing your customer servic e skills. In this situation, you may want to discuss that the key is to not offe nd the user and turn them off to your support services. In handling this situati on, you would pay particular attention to ways you can build trust with the user and lead them to the right resolution to their problem. These components may include: Acknowledging the user s diagnosis Asking the user to reproduce the problem Finding a solution that works Q. How do you handle setting up new employees? A. This question is used by the hiring manager to assess your knowledge of commo n practices within the IT department, such as setting up new users. Obviously, t he IT department plays a critical role in the productivity of the new employee. The role of the desktop technician is to help ease the new employee into the res ources available to them and get them up to speed quickly. In responding to this question, you may want to talk about some of the tools you ve used in the past to help users acquaint themselves with their new environment. Some tool s that help are: A new-user welcome letter that is customized to the specific user with all their

relevant information including telephone extension, how to access voice mail, a nd how to log in. It might also include a FAQ on getting help. A Getting to Know Your Helpdesk document that provides an orientation to helpdesk service, such as how to contact the helpdesk, its hours of operation, what is an d what is not supported by the helpdesk, and answers to common new-user question s. Technical Questions Q. What questions would you ask A. This question is used by the lities. The following represent the end-user to help diagnose a to help isolate a user s problem? hiring manger to assess your problem-solving abi some of the common questions that you would ask situation:

When did the problem first start? Has the system ever worked properly? What was the last thing done to the system prior to the failure? Is the issue intermittent or ongoing/constant? Are there any error messages? If so, what are the specific error messages? Has any new hardware been added to the system? Has any new software been added to the system, including downloads from the Inte rnet? Has anything changed with the system (for example, has it been moved) since the issue presented itself? Has anyone else had access to the system? Are there any environmental factors that could be causing the issue? Have you done any troubleshooting on the system on your own? Have you checked all the cables/connections for a tight fit? Q. What are the main differences between the following operating systems? A. Unfortunately, most companies have not been able to standardize the operating systems used by users. It s always critical that you know more than just the curr ent version because there will always be a user who has a problem with an older version. By asking this question, the hiring manager is actually testing your kn owledge of different operating systems that you may need to support. The followi ng provides a concise summary of some of the major differences. Windows 2000 and XP Overall, XP is a minor update with Windows 2000 designed to get Windows 2000 tec hnology into the hands of consumers. The major changes include the following: Device driver rollback Remote control (single-user terminal services) New Start menu, control panel, and user interface elements Fast user switching Encrypted file system support for redirected folders Better support for roaming wireless networking Enhanced policies Credential Manager Personal firewall Q. What are typical virus sources and how do you prevent virus attacks? A. This is virus protection 101 just to ensure that you understand the basics of protecting against viruses. Possible virus sources include e-mail attachments, Internet downloads, and infected floppy disks. To prevent virus infections: Use anti-virus software. Perform regular updates to the virus software definition files and scan engines. Verify updates have succeeded. Perform regularly scheduled virus checks. Configure software to check all files, not just program files. Educate users on virus attacks, their consequences, and how to prevent them.

Know where all software came from. Do regular backups. Develop reporting mechanisms to inform server administrators of observed desktop infections and how these could impact the server environment (such as deletions or corruption of files on public shares, hidden payload files that might have b een uploaded to servers, and so on). Q. What are some of the guidelines you would recommend for implementing security at the user level? A. Security is a major part of the desktop technician s day-to-day responsibilitie s. As the closest point of contact to the end-users, technicians need to be savv y on the different methods for enforcing security. Some of the top techniques ar e included below. Anti-virus software: Ensure that all users install and regularly use anti-virus software on their PCs . Instruct users to immediately notify the helpdesk when they suspect they ve contra cted a virus. Password security: Instruct users not to give out their passwords. Instruct users not to write down their passwords. Instruct users to make sure their password cannot be easily guessed by using a c ombination of alphanumeric characters, including special characters (~ ! @ # $ % ^ & * ( ) + = [ ] { } / ? < > , ; : \ ` .). Instruct users to change their password if they think there is even a slight cha nce someone knows it. Instruct users to ensure their password is at least eight characters long. Instruct users not to use a variation of their user ID. Regularly change passwords on Administrator accounts on PCs (NT, Windows 2000 an d XP) Desktop security: Instruct users not to leave their workstation logged in overnight. Instruct users to enable screen savers that automatically lock their PC when the re is no activity on it for more than five minutes.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close