Slashdot Mirror


How to Hire a Linux Administrator

Skapare writes "Hiring a good system administrator can be difficult. Hiring one while converting to Linux may take someone with special skills. Tom Adelstein is exploring just what is needed, and what should be avoided, in an article at Linux Journal about Linux System Administrators. I say hire more than just one."

23 of 62 comments (clear)

  1. I know whats needed by FidelCatsro · · Score: 2, Funny

    All you need is my contact information ,and a cheque for atleast 50,000 euros per year.

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
    1. Re:I know whats needed by EnronHaliburton2004 · · Score: 3, Funny

      Yeah, but unfortunately for YOU, Mr. Castro, your Visa was rejected.

    2. Re:I know whats needed by Anonymous Coward · · Score: 5, Funny

      Our Policy is not to hire dyslexic third world despots for IT positions.

    3. Re:I know whats needed by jd · · Score: 4, Funny

      Agreed. Policy dictates that they should be confined to managerial positions.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  2. Find a Linux Sysadmin on Slashdot? by xmas2003 · · Score: 3, Funny
    Advantage: knowledgeable in open-source, etc.

    Disadvantage: Spends a lotta time on /.

    --
    Hulk SMASH Celiac Disease
    1. Re:Find a Linux Sysadmin on Slashdot? by superpulpsicle · · Score: 3, Interesting

      While that sounds funny, I have found more solutions to technical problems from /. than anywhere else on the planet.

      Especially software recommendations, which I can't get enough of. Seems like someone dig something good up everyday.

    2. Re:Find a Linux Sysadmin on Slashdot? by IO+ERROR · · Score: 2, Funny

      Funny, that. I just applied for a position internal to my company, and somehow I hope the hiring manager doesn't read /. or he'll see the last 24 of 735 flamebait and trolls I've posted. And that'll pretty much ruin any chance of getting the job.

      --
      How am I supposed to fit a pithy, relevant quote into 120 characters?
  3. Interview questions by prostoalex · · Score: 2, Informative

    Shameless plug, it's my site: Linux Interview Questions

    THe questions were forwarded by recruiters and companies, pretty much all of them in the US, except the first one, who was located in India.

    1. Re:Interview questions by dago · · Score: 2, Insightful

      Well, the question would be more like "Can you find the incorrect answers on this website ?"

      Here are the first two (easiest) ones :

      "Q: What is HTTP Tunneling
      A: HTTP Tunneling is a security method that encryptes packets traveling throught the internet. Only the intended reciepent should be able to decrypt the packets. Can be used to Create Virtual Private Networks. (VPN)"

      "Q: What is the difference between a soft link and a hard link?
      A: A symbolic (soft) linked file and the targeted file can be located on the same or different file system while for a hard link they must be located on the same file system."

      --
      #include "coucou.h"
    2. Re:Interview questions by Piquan · · Score: 4, Insightful

      Not a big fan of several of the answers. The first batch of questions has some things that are quite wrong (virtual memory is implemented by time-sharing?!?) and there's no comments correcting them. At least the one that starts with "ls -ltra" has comments, although the main page doesn't make that clear.

      One problem with providing answers to interview questions is that it's almost useless. If the interviewer knows the correct answers, then they don't need it. If the interviewer doesn't, then the questions must be crafted to only have one correct answer (eg, "What does UDP stand for?"), and such questions are often teh suck. Otherwise (still discussing the case when the interviewer doesn't know the problem domain) you end up with situations like the windows/unix filesharing question, in which the interviewer expects to hear NFS while many respondants would reply SAMBA. Open-ended questions, such as "what does [technology] do" are the worst in this scenario. So I don't think that providing answers helps.

      Beware also of "opinion" questions, such as "what is the main advantage of symlinks over copies". The question on your site says that permissions are shared, while I think that the main advantage is that modifications are shared. Somebody coming from an embedded systems background may well have good reason to say that the main advantage is disk space.

      I guess my point is, it's perilous to interview for Linux folk if you don't know enough Linux to deal with a variety of correct answers.

    3. Re:Interview questions by SpaceLifeForm · · Score: 2, Informative

      I have to argue about the first one above (HTTP Tunneling). Just because you tunnel traffic does not mean that it is encrypted.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    4. Re:Interview questions by Master+Bait · · Score: 2, Insightful

      Better questions:

      Q: If you didn't know what HTTP tunneling is, how would you find out?
      Q: Describe in single words only the good things that come into your mind about your mother...
      --
      "Only in their dreams can men truly be free 'twas always thus, and always thus will be."
      --Tom Schulman
    5. Re:Interview questions by tchuladdiass · · Score: 2, Insightful

      The thing I noticed (other than the wrong answers) was that a lot of the questions are aimed at a potentially different target. For example, why would you be asking a linux admin any dba-related questions? Also, the questions specific about various apache versions should be aimed at a web administrator (which falls under the applications group, not the sys-admin group, at least in a larger organization).
      I'd prefer to see a list of questions that pertain to the more non-technical aspects of system admin, such as proper change control procedures, importance of using well-tested and documented solutions, and reasons not to impliment something "just because you can". I may be getting cynical in my old age, but I've spent way too much time on cleaning up previous hot-shot admins' "handy work".

  4. Personality by Anonymous Coward · · Score: 5, Insightful

    Don't forget to look for personality.

    Too many geeks spend so much time in front of the computer they forget how to deal with people.

    I'd rather hire a less-technical person with good person skills then a more-technical person who cannot hold a converation. Since the Linux admin is basically a internal support person for the business, a good personality, decent communication skills, and the ability to turn a low-level human concepts to create a technical solution are always very important. The ability to chat over a coffee or beer is essential in any workplace.

    Many technical skills can be learned very quickly. Personality is learned in a lifetime.

    1. Re:Personality by Anonymous Coward · · Score: 3, Insightful

      What you really want is the best of both worlds. So hire an ubergeek and let him live in the server room. Then hire a moderately technical person with good people skills to act as a firewall between that guy and the outside world.

    2. Re:Personality by EnronHaliburton2004 · · Score: 2, Insightful

      Your typical geek is not interested in Politicking. He can be polite, but not interested in engaging in chit chat for the sake of chit chat.

      Politicking is not required to have a personality.

      The group will function better if the geeks and non-geeks are able to bond a little bit.

      If you're the nice but quiet geek who sits in the corner, I'm not sure you'll survive for long at many of the companies I work at.

  5. Nicknames by Profane+MuthaFucka · · Score: 5, Funny

    Don't wait until he signs the contract to ask him what his funny nickname means and how he got it. I'm serious about this. Under no circumstances should you EVER hire an admin who answers to the name of "jizz". Truse me.

    --
    Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
  6. Hire more than one?! by Improv · · Score: 2, Interesting

    In my experience, that's a recipe for disaster. In my old workplace, there were four of us, and there were constant power struggles. Eventually, things got better when some of us left, or so I hear.

    --
    For every problem, there is at least one solution that is simple, neat, and wrong.
  7. I KNOW this stuff by czarangelus · · Score: 2, Interesting

    I've been using Linux as my primary or secondary OS at home for 3 years, and I easily know all the questions on that site. I'm wondering how to make that translate into an actual job, given that my degree is (going to be) in the field of Philosophy and I have no real experience administering computers in a professional setting. Are there certifications? Where do you start to get experience? Help, I'm going to need a job when I get out of college!

    --
    When a true genius appears, you can know him by this sign: that all the dunces are in a confederacy against him.
    1. Re:I KNOW this stuff by russellh · · Score: 2, Insightful

      Join a startup company. Of course, you have to find one, or start one, but they love people like you. Being a low-budget environment, you get to do everything, with real responsibility, from sysadmin to programming and answering the phones (or whatever. Startup companies can't afford to hire sysadmins. They can usually only afford generalists. You can then emphasize whatever it is you want on your resume.

      As for finding one, well... luck probably. you have to know people in that world. Or know those who know people doing it.

      The other thing you could do is volunteer (ie for free) for a non-profit org to get experience while you do whatever other job you have. Like startups, they have little (or no) budget for people like you, but they probably desperately need technical help.

      --
      must... stay... awake...
  8. Selecting a syadmin by Anonymous Coward · · Score: 5, Funny

    First, look over your potential new sysadmin from a distance of a few feet. What you're looking for are any major defects.

    Contrary to popular belief, a good sysadmin isn't just skinny or fat. Any body shape will do fine, so don't spend a lot of time here. Just feel him or her in his midsection and verify that the flesh is soft and supple. Firmness in the stomach area is a sign that this sysadmin has been exercising rather than reading product manuals.

    Count the legs and arms: a good sysadmin should have two arms (with hands with five fingers each: sysadmins do a lot of typing), and two legs. However, if your sysadmin has less than two legs and comes with a set of wheels, he will do just fine. Two arms are absolutely necessary though!

    Next, come in a little closer. If you detect the aroma of old floppy disks, throw this one out, it's not fresh. What you want is an aroma of unwashed armpits mixed with the smell of microwaved CD-R fumes.

    Look your sysadmin in the eyes. If he or she looks at the floor, that means the reflexes are sharp.

    Finally, take an alphanumeric pager and wave it in front of the sysadmin. He or she should instinctively take the pager and strap it to his or her belt. If the pager is rejected, a firm "NO" will usually suffice, however a salary increase and/or further training is sometimes necessary.

    Once you've selected your new sysadmin, take him or her to your server room and let him roam freely. Be sure he has a clean box to put empty Mountain Dew cans in.

    If you have sysadmins already, you may want to keep them in separate cubes for a few days. Then, put them in the same room for a few hours each day to rub scent glands and discussion Gentoo USE flags. In some rare situations, disgreement over which boot loader to use may result in fights, be prepared to separate them.

    Congratulations on your new sysadmin! He or she should bring you several months of smoothly running systems, until burnout or employee turnover sets in.

  9. Typical Linux anti-MS attitude. by PygmySurfer · · Score: 2, Insightful

    In general, a Linux system administrator has an easier time working on Microsoft and UNIX operating systems than the other way around.

    It's phrases like this that make me question the validity of the whole article. The prejudice many Linux users have against Microsoft alone would be enough to keep them from trying to administer Windows systems. On the other hand, I think most UNIX admins would have an easy time admining a Linux system.

    1. Re:Typical Linux anti-MS attitude. by ChibiOne · · Score: 4, Insightful

      As elitist as it may sound, in my experience (as a Linux Admin for an ERP consulting firm, sometimes I'm asked to provide training for the client firm's tech staff) this is actually true. The reason may be that a Windows admin has spent so much time with the GUI that memorizing/using the command line may seem like a daunting task. I'd say it's not a matter of competence, but rather a matter of attitude.