Interviewing for Sysadmins![]()
by Dave Clark
Dave Clark is president and founder of MindSource Software Engineers, a technical talent company devoted to staffing for system and network adminis-tration. Dave is a former UNIX system engineer and administrator.
In my previous article (;login:, April 1999), I wrote about preparing a resume of qualifications for job hunting. In this article, I'll discuss how to handle the interview and other employment screening processes. The system administration field is different from other high-tech venues; the job hunting and interviewing processes differ, too. In particular, a small core of individuals with niche talents are given an inordinate amount of responsibility. In fields such as applications development, individuals are sometimes hired in groups. System administrators, by contrast, are typically hired individually to fill very specific roles. As a result, the screening and interviewing process for system administrators can reflect this search for individuality, personality, and disparate skill sets.
Get That Interview: HR, Recruiters, and Other Obstacles
If you wind up talking with an HR person or a recruiter prior to meeting the hiring manager, plan on taking a different tack. When interviewing with a nontechnical or nonhiring authority, figure you need to fluff up a bit to pass the exams. Too often, these folks don't screen well technically: the recruiter is eager to get anything that has ink on it to the hiring manager, while the HR person typically focuses on interpersonal skills and buzzwords rather than core technical competencies. Always keep in mind, however, as with any sale, you are best positioned when speaking directly with the decision-maker. Keep the interchange with HR and recruiters as short and direct as possible. Get as much information as you can from them (job description, salary, benefits), but keep your sights set on the real boss.
Pre-interview Planning and Hard Questions
Time Lines
Drug Tests
Psychological Profiles
We actually had an acquaintance who was asked a series of questions that bordered on the ludicrous: "Do you see the pond out there?" the interviewer asked. "If you were a duck, what kind of duck would you be?" Our fearless candidate responded without hesitation, "Whaddya mean what kind of duck would I be, what have you guys been smoking, anyway?" Although the story ends with our friend being escorted to the door, I maintain that the response was more appropriate than the question.
Security Clearances
Insurance
Background Checks
NDAs, Noncompetes, and Intellectual Property Rights
If you find legal-speak on an employment application and you don't understand it, don't sign it. You have the right to consult with an attorney. Consider asking for a photocopy of anything that you do sign. An important word on contracts in general: they did not come down the mountain on clay tablets. Although this may cause delays, if you vehemently disagree with something (in an NDA or your employment contract, for example), mark it up and see whether they agree to your changes. While parts of your contract, such as salary and benefits, may not have wiggle room, other areas, including scope of duties, training, or review periods, may be wide open. Be aware that employment contracts can be and are often altered; it's just that most people don't want to confront an authority figure. It's important that someone who makes such a request have a valid point. Also, senior staff can pull this off more easily than recent college graduates. The nondisclosure agreement usually concerns dissemination of proprietary information or trade secrets by employees and former employees. An NDA may also require you to testify or provide information for your employer in a legal case. Generally the information provided in the first interview will be unrestricted enough not to require an NDA. Take your time and think about it. Noncompete agreements concern an employee leaving a company and forming his or her own company using proprietary information gained while on the job. Noncompete agreements must be limited in geography and time. An employee has the "right to earn a livelihood," which often makes noncompetes hard to enforce. IP does stand for something else! Intellectual property rights include patents, designs, copyrights, and related "know-how" rights. If you suspect that a product or idea of yours may fall into this area, you should consult with an attorney. You can expect that a release of your rights will begin with a list of prior inventions. This is again a case where there is no harm in the delay caused by a thorough perusal of the document. The question often comes down to whether you are being employed as an inventor and developer or to perform more general duties. Most jobs for system administrators do not require this.
The Interview
The On-Site Interview
Because so much of how we come across is "impression" as much as technical competence, it's important to take some time to "look good." Depending on your geographical area and the type of job you're looking for, a suit may not be required, but it's never in poor taste to dress well for an interview. At the very least, dressing well conveys that you care about your meeting. Similarly, be prompt for your interview. If by some misfortune you must be late, take the time to call and inform the person you're going to meet of the necessary change in plans; always call in advance. Set personal goals for the meeting. Do you really want the job? Perhaps you want to go to an interview as a trial run, to polish your skills. As you move along in your career, you'll probably be asking more of these questions, and you'll be more discriminating when it comes to selecting the best opportunity. When you meet with the hiring manager, your resume may serve as the tool that guides the interview. If you didn't need the resume to get the interview, for example in the case of a word-of-mouth-referral, my advice is "don't confuse the process." A resume, good or bad, can be a hindrance at times: presenting information that was not requested may result in an objection. The same would be true for providing employment references (or copies of your source code) before being asked. But once you have the interview you should be prepared to furnish all of these, when requested.
Be Prepared
Last-Minute Advice
Toward the end of the interview, you might be asked whether you have any questions. If you do, it's appropriate to bring them up, in a factual way. Asking about the typical career path of the job is one thing; asking the manager how long until her or his job will be open is another! Always ask for the job. I can't emphasize this enough. Techies, especially, have a way of understating their interest in a position. If you can't muster the strength to ask, "So when would you like me to start?" then beat around the bush a little but do show interest, even if you think you did poorly or have doubts about the job.
Practice Makes Perfect
If you ever do feel you've "bombed" an interview, remember it's not the end of the world, and it may not even be your fault. If you are meeting with hiring managers who are inexperienced, their first few interviews may be rough.
Following Up
It is considered professional to follow up an employment interview with a letter expressing interest in the position. Following up after a poor interview might even get you a second shot. It always helps to tell someone that you are interested in the position. A follow-up contact is especially appropriate for a senior position for regular full-time employment with a large company, since it is construed as the beginning of a potential relationship. The letter should be short and to the point. With smaller and less formal companies a simple email may suffice. In this case, try to attach some information pertaining to the interview. Avoid at all costs using a formal response to cover up any errors you feel you may have made during the interview. Broaching the subject of your tardiness or technical questions you bombed will reinforce the negative. I generally don't advise phone calls unless the manager requests it, but use your judgment, be yourself, and show interest.
Conclusion
|
![]() Last changed: 14 Apr. 2000 mc |
|