1

Hey there Spiceheads! Hope those that celebrate Thanksgiving, had a good holiday week/weekend.

So I am not thrilled with the way management and the new IT management regime are handling things and I feel it is time to move on. Plus I would like to work closer to home.

But here is my dilemma. My title is Network Support Admin., and while I will handle data jacks, running cable, patch panels and punchdowns, our switches and servers are handle by Corporate IT and local IT has very very little access to them.

Yes I can handle password changes in our ARS system, which is AD, can add/remove a computer, but don’t handle OU’s, create groups, etc…

I basically work on moves, repairs, installs, images, etc., Can setup, change or remove a user or phone ext. in our voicemail system, move phones, but have to place a request with our phone support vendor for any adds/deletions, changes in our phone system.

And with that, I don’t do any real Network Administration. My previous director hired me with that title to justify getting more pay to get someone hired on.

So when I work on updating my resume and start sending it out for a new job, how do I justify the title/pay for something I really am not doing?

Not looking to outright lie on my resume or to a pending new employer. I know most will fib a little on a resume, and that is ok, but I feel this can hurt me.

The other thing that hurts me is lack of degree and certs. Been in an around It for over 20yrs. and enjoy the tech side of the work, just not into the crawling under desks and tight spaces when running cables and doing moves. Back and neck are not the best anymore and would love to move into doing more hands on Network Administration. I have some basic knowledge of it and willing to learn it if given an opportunity.

Sorry for the lengthy post, just looking for sound advice. Thanks Spiceheads.

25 Spice ups
2

Start by learning on labs and test devices at home and anywhere you can. But the title you have and what you do, do not match so you will need to change that title. Usually on a Resume you don’t need to place what you got paid, and that is only discussed in the interview.

2 Spice ups
3

You were support to network engineers, so network support admin sounds right to me :slight_smile:

I would still write NSA on resume, as you were hired as one and you would not lie about it. You can still look for jobs with your knowledge or something little bit more challenging, but can be truthfull about your shortcommings if you get to talk to them and tell them what knowledge you think you lack… Maybe it will be enough for them or maybe they’ll invest in certs with you.

Dbeato had it right, take your time, invest into some networking gear and old servers, think of fictional projects and start investing into your knowledge… You don’t need certs to look for new job, you need knowledge, certs you can take with new employer or yourself and then look for even better job :slight_smile:

1 Spice up
4

I’ve had the same problem with poor titles given by the company.

Now days I just call myself an I.T Generalist…

1 Spice up
5

If you use the title you’re given, you’re not lying. That’s why we talk all the time about how titles are meaningless here. Companies will hand out “systems administrator” and “systems analyst” titles like frickin’ Pez without any consistency from one to another.

The only people for whom that even matters are us. Actual IT pros who like to try to size each other up when we meet.

If you feel that your title is too inaccurate for what you have experience for and what you want to do, then leave it off. You worked at XYZ Corp. from January 20x6 to August 20y8, and here’s your list of accomplishments: 1, 2, 3, 4.

Lack of credentials for 20+ years in the business isn’t going to matter. By the time I finally finished my bachelor’s degree, I’d already been working in IT professionally for 18 years. I just completed my master’s degree in IT management (a business-focused degree, not a technical one) this past spring, and jumped ship to a data analyst position after 17 years at my previous organization starting as a field technician and moving up to an actual administrator of various servers and systems and “solution engineering.”

(a fancy way of saying “here’s a problem that nobody knows how to solve…figure something out, how much money you need, and how much time it’ll take…and put it in a Powerpoint if you can. We love Powerpoints.”)

4 Spice ups
6

Couldn’t have said it any better. You really don’t want to get caught in the ‘fake it til you make it’ at the interview.

1 Spice up
7

Why buy equipment when you can do labs through TestOut that are simulations of real equipment and the machines in the labs function like the real thing. The beauty of TestOut your access will last for a few years you can go over and over a lab until you feel comfortable to move on. Just don’t waste time on their cert’s no one recognizes them but TestOut I was burned trying to use their certs as credit trying to get one that is recognized I had to start from scratch.

TestOut

1 Spice up
8

If that is your official title where you work now then it is not lying by putting it on the resume. That is why the descriptive portion of the work history is used, to explain all the things for which you are responsible and any major projects you worked on.

4 Spice ups
9

Yeah, Companies do sometimes use the Job Title to an end, at my last job I went through 5 job titles in 17 years, from a humble “Computer Operator” to “PC Network Specialist”, “Network Administrator”, “Systems Engineer” then finally “Senior Systems Analyst”. However, at my current job I have spent 8 years with the title “Network and Server Technician” and I don’t see that changing much.

If you are good at the stuff you have stated, then I see no reason you won’t pick up the extra duties you havn’t covered yet quite easily.

3 Spice ups
10

I have been all of the following titles: Network Administrator, Server Administrator, Systems Administrator, Media Technician, Mainframe Operator, and a handful of others yet I have been doing almost exactly the same thing just with different users and different types of data. The title doesn’t seem to make much difference and is incredibly confusing in this particular industry. This is why you need to utilize the descriptive portion to the best of your abilities.

2 Spice ups
11

YASssssr.gif

12

The question to me is… what do you want to do? If you want to get into more of the networking stuff, use the title but “expand” on the duties, like “since our corporate IT is now handling all our switches and servers I normally work on…

” It explains what you do, and why you do that stuff with the title you have. However if you like the kind of work you do, or want to “start” in a similar position and work up… Word it more to the duties, “While they call me a Network Support Admin my duties focus on…”

I don’t think too many places focus on titles because lets face it anyone in the field for a few years has heard of things like “a paper MCSE” meaning a person with a cert but no skills. And we’ve likely all seen titles that make you scratch your head when you see the duties… “Sanitation Engineer, duties include scrubbing the toilet and mopping floors…”

Be honest enough to get in the door and follow up. For example, when I write a resume I mention “I used to hold these certifications” and mention that while they are expired it points to skills I learned, and areas of interest. Then mention I’m willing to re-certify if desired. I might also mention that my skills in X area are rusty, but I"m working on polishing them up again…

You get my drift. Don’t sell yourself as the great Network Admin, but if you want that type of work use the title (and online training) to get in the door.

1 Spice up
13

Your job title means less than nothing really. I guess it’s possible you can be overlooked by dumbwit HR on occasion but you should be fine to use the title they give you. Just be honest in the interviews and don’t lie to boost your knowledge. You will get caught up eventually.

My job title progression went like this:

Helpdesk (did what the title was)

Helpdesk Manager (also did what the title was)

System Administrator (Was the GOD of all things IT in a massive environment and did the work of 5 people by myself)

System Administrator IV (Same exact position as above just changed my title. No pay increase.)

Sr System Administrator (Same as above just another title change. No pay increase.)

Regional Technical Project Coordinator (Literally did nothing for 8 months. I’m still not sure what the hell this job was. lol)

Site Operations Lead (System Administrator for two clients. Both combined are a quarter the infrastructure size of the Sys Admin positions above.)

Now if you looked at my job titles it would look like I’ve progressed in leadership and responsibility but that is not the case. Those three middle job titles (which were the same position) were the most responsibility and took the most knowledge. My last two positions while probably a promotion in the job title sense are actually less work and less responsibility.

PS… I only have a AABA and a couple pointless certs to my name.

2 Spice ups
14

Take some time to start learning/training on Network Admin stuff. You have the title legally so keep it. Just close the gap by spending downtime and hometime learning.

15

Thanks everyone.

All makes sense and my plan, now that I have recently moved, is to study at home. A buddy of mine has some PC’S that I am picking up so I can set up a server add some VM, make a small network, so I can practice and familiarize myself with stuff I am lacking.

So the advice given pretty much is what I have been thinking, but it’s good to get that validation from others whom have gone thru similar situations.

Def will overhaul my resume so it fits better with the current title. I also like the ideas mentioned about explaining where I need to better myself and willing to learn it to move forward, especially in an interview.

Awesome advice and everyone seems to be on the same page with it.

1 Spice up
16

Thanks everyone.

All makes sense and my plan, now that I have recently moved, is to study at home. A buddy of mine has some PC’S that I am picking up so I can set up a server add some VM, make a small network, so I can practice and familiarize myself with stuff I am lacking.

So the advice given pretty much is what I have been thinking, but it’s good to get that validation from others whom have gone thru similar situations.

Def will overhaul my resume so it fits better with the current title. I also like the ideas mentioned about explaining where I need to better myself and willing to learn it to move forward, especially in an interview.

Awesome advice and everyone seems to be on the same page with it.