UNIX Hints & Hacks

ContentsIndex

Chapter 10: System Administration: The Occupation

 

Previous ChapterNext Chapter

Sections in this Chapter:

   

10.1 Three Levels of Administration

 

10.5 Preparing for an Interview

 

 

10.2 Functions of an Administrator

 

10.6 Types of Interviews

 

10.10 Working with Vendors: Sales and Maintenance Representatives

 

10.3 Finding a Job Working with UNIX

 

10.7 Being Interviewed

 

10.11 Working with Vendor Support

 

10.4 Preparing an Administrator's Résumé

 

10.8 Finding the Right Person for the Job

 

10.12 Working with Local Support Engineers

 

 

10.5 Preparing for an Interview

The average interview process can last from 30 minutes to 2 hours, depending on whether you are liked and have a chance at the open position. The longer the interview, the better your chances. Either way you look at it, you still have to be prepared. Each interview will be different. The companies you interview for are different. Also remember that interviewers have their own techniques for the interviewing process. Here are some tips that might help you relax and prepare yourself for an interview.

Know your résumé: Sometimes you may accidentally or inadvertently stretch the truth on your résumé. When you are being interviewed, you don't have a copy of your résumé in front of you, but the interviewer does. If you are beginning to exaggerate about certain things you have done in a past job, interviewers may try to catch you in a lie by asking a particular question that is answered on the résumé to see if you lying. If you tell the truth on your résumé, you have no reason to lie in the interview.

I fell into a trap once, whether it was ignorance, stupidity, or nervousness, I don't know. On one interview, years ago, I listed knowledge of Ethernet technology for various platforms. At the time, I had configured an Ethernet interface only in UNIX and on a PC, but I had Macintoshes listed on my résumé. The interviewer asked if I had ever configured PC/TCP on a Macintosh. You would think I would catch the trick question; after all, the first two letters of PC/TCP are PC, but I fell into in the trap and said, "Oh yes, it's easy. I do it all the time." A year later my boss told me he laughed so hard after I left. Yes, he was my boss and he gave me the job because I wasn't going to work with Macintoshes, only UNIX systems.

Know the company: Before you go to an interview, learn everything you can about the company, if you really want the job. In many cases, the interviewer will ask if you know anything about what the company does. They are always impressed if you have done your research. They also sometimes like enthusiastic fans of the company. Interviewers believe that the candidate will excel in their position if the candidate wants to be part of company and what the company is about. If you can find a way to convey this in your interview, you may put yourself into a stronger position to get the job over others.

You can find out all kinds of information on companies on the Internet. Most have Web pages that usually include a mission statement. If you cannot get the information off the Internet, make a simple phone call to the human resources department in the company. Tell them that you will be interviewing a position and want more about the company. If the company is in the business of selling products, you can be a little devious by contacting sales representatives, telling them you are interested in their products, and asking for some sales literature to be sent to you. A money hungry representative might send a catalog of the company's product line to you overnight.

Predicting the environment: It isn't difficult to predict the environment of open positions that you are applying for. If they are looking for Oracle, Informix, Sybase, and SAP, you can be almost sure that you would be supporting a system in a financial environment. If the systems are SGI based, the environment will be in some type of graphics shop in an engineering, animation, medical, or a science environment. Look at the applications and systems listed and the type of company. Someone in the human resources department might be able to tell you what the systems are used for in the environment you would be supporting.

Being quizzed: You can expect to be quizzed. Although it may not feel like a quiz, you will be asked about certain UNIX commands, how to configure something, what a certain UNIX script would look like, how you would do something, or your opinion on whether a specific set of procedures will actually work. Such questions will really test your knowledge and will require more than a yes or no answer. Interviewers want you to expand on these types of questions. Try and provide as much information as you can. If you cannot answer the entire question, answer as much as possible and be truthful when you do not know something. Most people that do interviews will not ask any questions they cannot answer. So if you lie, they will know. You will not be expected to know everything in every interview.

Know your stuff: Don't apply for a senior-level administration position when you are at a junior level. You will not get the job. Companies know what they are looking for today and will wait until they find the right candidate. This is why you have to look at all the details that you can find about the position before you apply for it and before you go into an interview. A phone interview first can work to your advantage. You can get an idea of what the company is looking for and be fully prepared for a second interview meeting.

Technical interviewers: When you're interviewed by technical people, these will be the people you will be working with directly. They will not only be quizzing you on your UNIX skills, but also making sure that they will be able to work with you. You need to watch them and take note of their characteristics, personalities, and mannerisms. You have to like them as much as they like you, or you won't get past the first month. Horror stories, system configurations, vendor help desks and response centers, and humorous user incidents are great icebreakers. Use conversations to relate to them on their level.

Nontechnical interviewers: You may be placed on one side of a table with five or six people on the other side to gang up on you. This does happen more than you may think. Don't be intimidated. Only two or three may actually be technical; the others are fillers, users, or managers who are there to watch your mannerisms and personality. Users will sometimes be involved to see whether you are a likable person and can support them. When in large group interviews, watch what you say. Interviewers might introduce themselves by name only. If you bad mouth users, you may get rejected fast. Insist on knowing what everyone does. You will look friendly and interested in everyone.

If you are interviewing with managers, directors, and sometimes vps, don't be intimidated. It is actually a good thing. They must like you a lot to ask senior management to take the time to talk to you. This indicates a relaxed environment with open door policies to management. Managers will typically ask more generalized questions to find out about the type of person you are and whether you would be a good fit in the department. Don't be anything but yourself if you meet someone from senior management.

UNIX Hints & Hacks

ContentsIndex

Chapter 10: System Administration: The Occupation

 

Previous ChapterNext Chapter

Sections in this Chapter:

   

10.1 Three Levels of Administration

 

10.5 Preparing for an Interview

 

 

10.2 Functions of an Administrator

 

10.6 Types of Interviews

 

10.10 Working with Vendors: Sales and Maintenance Representatives

 

10.3 Finding a Job Working with UNIX

 

10.7 Being Interviewed

 

10.11 Working with Vendor Support

 

10.4 Preparing an Administrator's Résumé

 

10.8 Finding the Right Person for the Job

 

10.12 Working with Local Support Engineers

 

 

© Copyright Macmillan USA. All rights reserved.