UNIX for Dummies Questions & Answers

Thanks for the answer about the accuracy about the information.
Okay, so most people here seem to be putting the starting salary around $50 - $75k a year. What would you say would be the salary after 5 yrs or 10yrs? I thought the thing about making millions sounded a bit odd. That's why I was asking around here about the accuracy of the info. I know I read on a forum a few months ago some guy said he and other system administrators he knew were making about $75 an hour after working about 10 yrs. Where I read this I think the same person said to expect expect about $40 - $50 per/hr starting salary and that you can add about $3 an hour per extra years experience in the job. Does this info sound about right? Sorry for all the questions
Thanks for all the help though... I really appreciate it!

I'm not a Server Admin, but more of an Application Server Admin, J2EE application servers, but they all run on Linux so most of my day is spent on Linux. Most people, unless their contractor's, are paid salary. Because for the company it makes more sense to pay us salary, b/c they know they don't want to pay that quadruple time when a server breaks on Christmas day and you have to work on it for 5 hours, which would obviously be equivalent of getting paid 20 hours.

So most of the jobs will be salaried, and because of that, if you have a nice boss, they are usually very lenient with your on-site working hours. I tend to come in around 830-9 every day, take an hour lunch, and leave around 430-5(yes I know I have a VERY lenient employer), but then again, I still end up working a minimum of 45-50 hours because so much of our work has to be done after hours and on Saturday night at midnight.

Look here for salary info:

SAGE Salary Surveys

The stuff available to non-members is 2006 or older, but still will give you a good idea. Inflate all the numbers maybe 5-10% to make up for the 3 year old data and you'll be in the ballpark.

Thanks for the link... that has a lot of info in it. It seems according to that page after I inflated the salary by 10% I came up with a figure of about $91k(in the area I plan on living...Colorado). I'm in PA now, but I'm planning on getting my education here and probably living in a townhouse around here until I can save up enough money to put a downpayment on a home around Colorado Springs... and then I'd like to move out there.
My plan right now though is going to college for a 2yr associate's degree in web development and then after that's over, transferring my credits and finishing with Bachelors of Computer Science(so probably 4-5 years of school). After that, I would probably like to take get a certificate for a Unix course or something alike(not that it means too much... more just as a way to get in the door of an employer). I know I'm going to have to learn A LOT about Unix... so I was planning on starting now and learning as much as I can. I'm pretty much a newbie at Unix... so I have a lot to learn. Someone here(i think it was wempy) mentioned building my own linux o/s (linux from scratch). I'm actually planning on doing that too. Anyways, for everyone out there in the Unix Systems Administration field, how does this plan sound to you guys? Do you have any more suggestions on things I should do to work towards getting a position as Unix System Administrator?
Thanks again

Hey guys,
Just wondering, what does a Unix Systems Engineer do? I can't seem to find any information on it. Is it anything like a systems administrator?
Thanks

Hi Guys,

I am one of the non-existent female UNIX SAs (according one of the threads above ), and I am working in a global company as a Senior SA, based in UK.

I am since 22 years in IT, had a lot of different jobs before including IT Trainer, Windows SA, Hardware technician, Networker, DB developer and others.

I started in my current company when they introduced AIX 4 years ago, and I am a dedicated AIX SA, not touching any Solaris-, HP- or Linux box what is probably not the norm at all. I am as well not responsible for Web- or DB support - thats responsibility of other teams.

My jobdescription tells me I have a 35 hrs job - 9-5, 1 hr break and 23 days holidays - and I am meant to be oncall 1 week out of 6. That is what I am payed for and my salary is probably pretty average for my position in UK.

So far the theory

And here comes reality: I am primary responsible for about 200 AIX Servers and since I was starting that early, I am treated as the person-to-go for everything about AIX - so I am co-responsible for about 500 more AIX boxes globally.

I am working in a team with 2 other SAs + Teamleader (who keeps the paperwork away from me) - thanks to the recent personal reductions - so my team is now smaller than eg 3 years ago where we had to care about 15 servers.

All our servers are following strategic decisions, that are for some weird reasons changed about every 3 months - that means that I hardly have more than 2 environments setup after the same standards. About 25% of my servers are application servers, everything else is running Databases (oracle/sybase)

We have to cover 24/7 support for all our servers and that means we have always 2 persons oncall.

We have to cover everything that requires root access - installations, OS- and application upgrades, application support, trouble shooting, disaster recovery, system builds, capacity- and performance management, we are the primary port of call for our customers, project managers, architects and many other things.

A normal working day for me starts usually at 6:00 am from home with code releases and a quick health check on the most critical systems that needs to be reported to management before 8 am - and a quick catchup with emails.

Once the report is completed, I move to my office, another look into emails and working on voicemail and problem tickets.

Being in the office means being available - via phone, messenger and email - and for the hundreds of personal questions the DBAs, Webguy or any other team has. That means being asked permanently to do quickly this, have a look there. It means as well participating on countless conference calls regarding the next change, the next major upgrade, the next project, the next strategy or the next go live or the current production outage. It does NOT mean to get anything normal or planned done during normal business hours.

When everyone else is leaving the office around 5pm, I find the time to start any kind of planned work - like the patching of the uat or dev environment, the monthly capacity review of environment A, the hardware request for environment B or to commence the system build of environment C. I really cannot recall when I left my office last time before 7pm, usually its around 8.30, 9pm - sometimes much much later.

Weekends are occupied with Production work. Every upgrade, every install (scheduled by us or any other team), every migration, every disaster recovery test, every go live happens on the weekend.

All this doesnt include the countless hours spent solving major production issues like corrupted production databases, the unexpected slowdown of application x, or the hours and hours spend in conference calls for production outages where a lot of different teams have to do their part to solve the problem.

So my working-hours are ususally 100+ per week + oncall every second week.
Holidays are rather illusive, I have taken off (including weekends) exactly 4 days last year

And still, if you ask me, I really do love my job - and I really don't want to do anything else. I never had a job that challenging, that rewarding and with that much fun.

After all - and though the whole position is very technical, you still get in touch and have to cooperate with so many people every day, that it never feels that technical. And honestly - it never feels like having worked so many hours since time passes very fast as long as you're busy - and believe me you always will be

If you consider being a System Administrator you should ask yourself
- are you patient enough to deal with hundreds of seemingly stupid questions every day, explain the same things 10 times with different words until you're understood, spend hours on conference calls for production issues well knowing that its not the fault of your system at all
- are you willing to learn something new every single day in your life
- do you want to live a life never too far from a phone and an internet connection since there will be lots of occasions where you are called to do something only you could do

Kind regards
zxmaus

zymaus... thanks a lot for the info! i appreciate it! yeah ignore that princeton review part(that says 0% females in SA)... like one of the other people said on this forum... that looks really old.
wow! 100+ hours a week? i feel for you.
i'm still considering Systems Administration, but I'm also looking at Unix Systems Engineering... that also looks fun. I know what ever I do I want to do something Unix related. I think I've narrowed it down to Unix Systems Engineering and Unix Systems Administration. Anyone with some info on Unix Systems Engineering though I'd appreciate hearing from you too!
thanks again for the info zymaus... I appreciate it!