Finally time to leave help desk for Jr Sys Admin?

FortKnight

Hello. I need some advice again.

I've been at this help desk for the last 2 years and 7 months. It was a nice opportunity, but I could be making more ($34K currently... in Maryland) and doing more. After getting Security+, I took a closer look at my resume and what I've been doing at work. I'm also considering MCSA Windows 7 Desktop Admin and/or Server 2012 (I heard it's possible to get both?).

I would like to pursue a career in Systems Administration. Even though my official title is help desk, I think I may be doing a little Junior Systems Administration work right now: managing accounts in active directory; building, imaging, and deploying Windows 7 machines; a little bit of making mailboxes in Exchange; Server 2003 and 2008; a little VMware.

I have intermediate experience, but am in no way a master in any of these fields just yet. There's only so much I could do without someone calling every 5 minutes, but I'm learning something new every week.

I've been told that, in order to evolve, it's probably not a good idea to hop to another help desk, even if it is higher paying. I'd imagine a Junior Systems Admin job would be the half-way point between help desk and Systems Administration. Does anyone think pursuing a Junior Systems Admin position is a good idea?

WiseWun

You've answered your own question, anything IT beats help desk. Go for Jr. Sys Admin or even Sys Admin if you know your stuff.

xenodamus

Titles can vary, but it's a long jump from helpdesk to system admin in any organization I've worked in.

It's more common to see people go from helpdesk to desktop, where you have more opportunity to grow and triage issues that will require you interface with the system/network teams. That's the path I took, anyway. I was the "super desktop tech" who gladly took any responsibilities the system/network guys were willing to let me have. I eventually moved to that team after working underneath them for some time and proving that I was a capable, driven, fast learner.

The knowledge I gained from the MCSA and CCNA was a critical part of my growth during that time.

Jon_Cisco

Over two years is plenty of time in help desk. It sounds like you have a lot of opportunity to see and touch things. Now it's time to make a list of the things you learn and start comparing it to actual job ads.

While your employed it's easy to take a gamble and apply for a few jobs. If nothing else you learn a little more about the process each time.

Good Luck!

FortKnight

That's good to know. Thanks! I don't want to jump too far ahead too soon, but I also don't want to miss out on opportunities to learn new things.

The goal now is a Jr Systems Admin position, but after looking at some desktop support positions, I'd be willing to go for that too. Some seemed to be just help desk with a fancier name, but I'll just avoid those.

I chose to pursue MCSA next (and hopefully MCSE) because I was already spending a lot of time with Windows desktops and servers. I've considered studying for CCNA, but I'll hold off until I'm done with MCSA. The job has me working on desktops and servers more than networks. One thing at a time, I suppose.

RHEL

Smaller companies will have "sysadmin" positions which are essentially a glorified help desk. This is more of a jack of all trades type position and could be very beneficial if that's what you're looking for. This may get the "systems administrator" title under your belt, but beware it may negatively impact your chances of working for larger companies with higher end technology. Big companies want to hire people with experience in large enterprise environments, so it becomes a decision of perhaps getting a job as a sysadmin now in a small company vs taking whatever you can get to obtain exposure in a large, complex environment.

Sysadmin in small company -- servers, user troubleshooting, storage, networking, printers, etc etc etc
Sysadmin in large company -- typically only works with servers (windows vs unix). Large companies usually have storage admins, backup teams, networking teams, engineering teams, apps teams, etc. I've been a UNIX admin at three larger companies and only one of them had me doing things other than UNIX (IBM storage, TSM)

Monetarily and growth wise, larger environments will yield more opportunities and dollars.

Edit: my post is focused more along the lines of the "server admin" definition of systems administrator. ie, hardware, OS software, and things that run on said OS

FortKnight

So I guess a Systems Admin at a smaller company will have to do (and just become average in) everything without being able to concentrate in a certain area...

... whereas at a large company with multiple IT departments, one could just learn and master a certain field, depending on what department they're in, while still being exposed to a little of everything.

RHEL

FortKnight wrote: »

So I guess a Systems Admin at a smaller company will have to do (and just become average in) everything without being able to concentrate in a certain area...

... whereas at a large company with multiple IT departments, one could just learn and master a certain field, depending on what department they're in, while still being exposed to a little of everything.

Yup... There is so much to learn and continue learning about specific technologies that it'd be unreasonable to expect to keep up to date and be good at everything. Even within my UNIX group, we have team members who are subject matter experts in specific distributions of UNIX/Linux. For example, I'm more of an authority on AIX and RHEL whereas other team members know Solaris extremely well.

Being an expert in a specific area is good if you're sure that technology is widespread and will be around for a long time. You don't want to spend all of your efforts learning a technology that only exists at one employer or is soon to be phased out -- you'll end up screwing yourself. Its a pretty safe bet that Microsoft, Red Hat, IBM, Cisco, Oracle, etc will be around for a while.

If I were you, I'd scope out both small and large and then weigh out your options for the now and for the future. Good luck!

FortKnight

Thanks for the advice. I think I'll stay with Microsoft for now. It seems most companies are still sticking with Windows 7 for a while, so I'll work on the MCSA for it.

I've spent some time with servers at work. This may be a long-term goal, but I would like to become a MCSE for Server Infrastructure; I shall also focus my job search around that.

I'd also like to leave Maryland, so I plan on visiting North Carolina in a couple weeks before sending the resume down there.

iBrokeIT

Desktop support isn't that much of a step up from the helpdesk. Challenge yourself and go outside your comfort zone, go for the MCSA Server 2008 or 2012. You'll still need to get a client exam too.

Xavor

Before you jump ship to North Carolina, throw your resume out in the area to the recruiters. There's so many opportunities here for employment and you never know what will happen. If your background supports it, try to get a job where they will sponsor a clearance and your salary will double.

Do you have a degree of any sort?

I was where you are until recently when I got the break out of the JOAT position. If you go to North Carolina, there's always Red Hat if you want to learn Linux (you should learn some anyway as an admin).

FortKnight

I've been in Baltimore for all my life; hate it here, to be honest. I received a B.S. in Information Systems in Spring 2012.

I've considered getting a clearance (I don't currently possess any), but I've never even knew about them until after I left school. Clean record and all, but I guess I need to be sponsored for the higher level clearances. Sucks that a bunch of IT jobs in my area require them, but would it hurt to apply anyway?

Linux has always been interesting to me, but I have little experience with it. I guess Red Hat wants you to have years of Linux experience, so I'll focus on Microsoft for now. Maybe I'll pull out an old laptop, or better yet work with VMware.

gbdavidx

FortKnight wrote: »

I've been in Baltimore for all my life; hate it here, to be honest. I received a B.S. in Information Systems in Spring 2012.

I've considered getting a clearance (I don't currently possess any), but I've never even knew about them until after I left school. Clean record and all, but I guess I need to be sponsored for the higher level clearances. Sucks that a bunch of IT jobs in my area require them, but would it hurt to apply anyway?

Linux has always been interesting to me, but I have little experience with it. I guess Red Hat wants you to have years of Linux experience, so I'll focus on Microsoft for now. Maybe I'll pull out an old laptop, or better yet work with VMware.

FYI you can't get a clearance on your own - you have to be sponsored by an agency

FortKnight

Speaking of recruiters, I tend to get calls once a month from Teksystems, whenever a temporary CALL CENTER position emerges. About a year and a half ago, I gave them my resume just for the heck of it. Despite adding to the resume since then (and me telling them repeatedly I wasn't interested in non-hands-on phone support jobs), these call center positions keep getting tossed my way.

FortKnight

Last month, I went to Columbus, OH. I know, not a lot of IT there, but I thought it was a nice place with a couple opportunities. I am serious about getting out of Maryland, but I need to visit at least one more city. So I'm going to North Carolina this coming weekend (Raleigh first, then seeing my aunt in the triad).

I've seen a bunch of jobs I thought I could do, but they weren't a perfect match for my skills. They would, for example, have a list of about 7 requirements, and I would miss or have limited knowledge in one or two of them. I would also have skills they didn't necessarily require, but I don't know if they'll make a difference. Would it still be worth it to apply?

And, let's say I get the interview for the job. They are going to ask about that one skill that's lacking. How would you handle that question? I'm thinking that this is what did me in for the last couple interviews I've done.