IT Employment
I need to put together a job description for a network administrator. I have a very good Idea of what I need to include, however, I would like to know if someone has one already done that I can use as reference to make sure I do not miss anything.
Thank you
by cactus pete
by oz_media
I actually wrote my own. I justified it to my previous employer by saying at least that way he sees that I have a good understanding of the work needed and this way he can see exactly what I'm willing to bring to the table. I also wrote my own contract, as my job description was over and above what he expected, he didn't read my contract (just the dollars) and completely missed that I refused to work Fridays. He signwed it and I had a year of four day workweeks before I was politely asked to revise it next tmie around (at which point I quit and worked for his competitors).
So letting people write their own job description is something I learned in the mid 90's, it is a EXCELLENT way to get people to seriously think about what they can offer and for you to see what they are prepared to take on as a job description, obviously you can go over it and ammend it with them but it saves a LOT of surprises.
by sms-dc.com
You may want to try standard descriptions. Here is an example (taken from Salary.com):
Network Administrator (IT -- Networking)
Installs, configures and maintains organization's network. Builds networks and maintains external and internal web presence, administers the networks. Performs system backups on its internal and external web network servers. Designs and supports server system(s) and supporting software. May require a bachelor's degree in a related area and 0-2 years of experience in the field or in a related area. Has knowledge of commonly-used concepts, practices, and procedures within a particular field. Relies on instructions and pre-established guidelines to perform the functions of the job. Works under immediate supervision. Primary job functions do not typically require exercising independent judgment. Typically reports to a project leader or manager.
More than likely there will be more to the job description to this (I.E. weekly staff meetings, upgrade, and disaster recovery plans), but like a gentelman said eairler the best was to get an exact description is to have the canidate to write the job description.
Have a look at this link: The Network Administrator Site.
by majesty
by wordworker
Don't plop them down in front of a blank page and expecting a job description to come out -- netadmins aren't exactly notorious for being prolific writers, Oz you being an obvious exception! I suggest having the netadmin keep a diary or log of work performed over a three or four day period.
Yes it's a bit of a pain to stop and think, okay what did I just do? and then write a note in a document or an entry in a spreadsheet. BUT, if you don't go through that exercise, you will forget important things you do.
That log of work performed will give you a snapshot of what you REALLY do every day....which will make for a better job description.
by clindell
As the title states I am a Network Administrator at a job where I am on a contract and could go perm soon. I feel the offer is low at 50K in northern California and the north bay and the demands are extremely high and stressful. I am a one man IT shop for a small company and do EVERYTHING, not just computers and servers, but handle leases of all hardware and copiers and printers the installation and return of leased equipment as well as handle the phone switch (PBX) and voice mail system. Let?s not forget the Cisco VPN concentrator, Cash register systems, purchasing, I review billing on any IT related expense, Cell phones and the 24/7 on call phone support to the remote sales staff or the owners if needed.
Manage LAN/WAN, Windows NT and 2000 Servers, Window 2000 pro and XP pro workstations
Manage Company PBX phone switch and voice mail system
Exchange 2000 Email server with secure Outlook Web Access
Windows 2000 Active Directory administration
Cisco VPN Management
Help desk services for local employees and remote Sales staff and on call as needed
Company website management
Manage company software and licensing
Hardware and software purchasing upgrades and rollouts
Training of employees on new systems
Manage multipurpose copiers, printers and fax machines
Manage leasing of computer systems and multipurpose copiers
Manage all data, phone lines, IT contracts and billing
Manage all Cellular phone services and billing
Manage and maintain company tape data backup system
Advisor to Owners and COO for all data and IT needs
What am I ?
Thanks,
Clindell
by techsoeasy
by himatech
by nick
List the basic expectations. 24x7 shop. Show health logs of servers, vpn, firwall and license rollout to some manager, Maintain teir 3 for help desk, Backup logs and off site media storage listing... etc.. during the interview ask them how they would do that for each technology...
If your also hiring a technologist, include things that include thinking and risk taking. If the person is going to make decisions about your technology future, make sure you put it in there and during the interview... ask them to make some decisions to see if they can make them.
Do not put specifics about the OS or infrastructure, those change and the job posting will cover the current and near term position/positions.
Some positions are not technologist administration positons and others are "watch the screen" administration. Only the company making the appointment truly knows what type of Administrator they are going to hire.
I like to use personality tests. I had my whole crew take them first and then compared the top three candidates to ensure we were not getting someone with traits already solidly in the group.
Only the people at the company can decide what they really want for a position. If your looking to can a current admin, asking them to write one might invite creepy/crawly things onto your systems... write it yourself.
As someone else mentioned... google. But you'll have to make sure you consider your unique needs.
by rob
Systems administration
Organizations that rely on computing resources to carry out their mission have
always depended on systems administration and systems administrators. The
dramatic increase in the number and size of distributed networks of
workstations in recent years has created a tremendous demand for more, and
better trained, systems administrators. Understanding of the profession of
systems administration on the part of employers, however, has not kept pace
with the growth in the number of systems administrators or with the growth in
complexity of system administration tasks. Both at sites with a long history of
using computing resources and at sites into which computers have only recently
been introduced, systems administrators face perception problems that present
serious obstacles to their successfully carrying out their duties.
Systems administration is a widely varied task. The best systems administrators
are generalists: they can wire and repair cables, install new software, repair
bugs, train users, offer tips for increased productivity across areas from word
processing to CAD tools, evaluate new hardware and software, automate a myriad
of mundane tasks, and increase work flow at their site. In general, systems
administrators enable people to exploit computers at a level which gains
leverage for the entire organization.
Employers frequently fail to understand the background that systems
administrators bring to their task. Because systems administration draws on
knowledge from many fields, and because it has only recently begun to be taught
at a few institutions of higher learning, systems administrators may come from
a wide range of academic backgrounds. Most get their skills through on-the-job
training by apprenticing themselves to a more experienced mentor. Although the
system of informal education by apprenticeship has been extremely effective in
producing skilled systems administrators, it is poorly understood by employers
and hiring managers, who tend to focus on credentials to the exclusion of other
factors when making personnel decisions.
Understanding system administrators' background, training, and the kind of job
performance to be expected is challenging; too often, employers fall back into
(mis)using the job classifications with which they are familiar. These job
classification problems are exacerbated by the scarcity of job descriptions for
systems administrators. One frequently used misclassification is that of
programmer or software engineer. Although the primary responsibility of the
systems administrator is not to produce code, that is the metric by which
programmers are evaluated, and systems administrators thus classified often
receive poor evaluations for not being "productive" enough. Another common
misclassification is the confusion of systems administrators with operators.
Especially at smaller sites, where systems administrators themselves have to
perform many of the functions normally assigned (at larger sites) to operators,
systems administrators are forced to contend with the false assumption they are
non-professional technicians. This, in turn, makes it very difficult for
systems administrators to be compensated commensurate with their skill and
experience.
( I hope you take the time to read it, it really is accurate)
rob@reradke.com
by gwenb1
by jerman
Well put, brother (assuming Rob to be a male name). The generalist tag is the hardest to get across to employers, that and what can appear to be a lack of focus, but is really broad focus. I can rebuild an Exchange Server after a disaster, configure a router, troubleshoot a printer, automate repetitive tasks, integrate Macs into my network, throw a website up in an eyeblink while deciding which build of Linux to use on my new server.
Am I certified? No. In the past 4 years I've gone from NT4 to Win2K and on to Win2k3. I learn what I need to serve my employer's needs, not what Microsoft thinks I need to know. I don't have the time to waste on esoterica. And what would I choose to get certified on? I need to know operating systems, server build and management, desktop troubleshooting, security, printer maintenance, routers and switches... By the time I'm certified in one thing, my knowledge would be out of date in another.
"Apprenticeship" was my route too. Employers need to look at your past employment, ask about your skillset, even better: Just ask a prospective hire to solve a problem, live, perhaps a help desk referral. A real sysadmin lives for the challenge of a good problem. The solution of the given problem is not the object of interest to the prospective employer. Watch as your prospect focuses on the issue and gets interested. For that's the key. A good sysadmin never wants to stop learning something new. And each problem is just another lesson.
by vaxenguy
Well said Rob.
Please remember that this is true for nearly all the different O/S's that exist, except for legacy IBM mainframes, where the technical structure is more rigid and defined.
I, too, am a systems administrator. But my area of expertise is in VMS/VAX/Alpha areas. And your description hits the nail right on the head. There were no schools that could teach what I needed to know, no formal classware to take. The mentoring system was all that was available and I used it. I am a generalist in a specialist arena: I can write code, operate the hardware, modify the hardware, install/update/modify the system/application/network software, and assist users with there problems.
The number of professionals in my area of expertise is shrinking. There are few of us left. Getting a job for a VMS system administator is far harder than, say, one in the Windows environment. Too often, the job is considered on par with that of an operator or can be handled by a programmer. Even getting apprenticed to a Windows system administrator is harder---simply because the OS is different, although the basic skillset is the same.
I wonder how many managers realize that Windows NT was patterned after/created from VMS? By one of the writers of the VMS codeset?
by mxyzyptylk1
The NT nuc started at Carnegie-Mellon. The lines thru this industry crisscross all over the place. That doesn't mean one Admin fits all. If you're looking for an Network Admin with AD experience, a Sun Unix weenie ain't gonna cut it. Likewise, that new Linux server farm with the Juniper hardware isn't gonna be working too well for awhile if you hire an NT2K admin who worked on NT routers and firewalls. This is the stuff you SHOULD specify.
But then, yes: they should be able to recite their jobs from memory. The routine you can't forget, and the troubleshooting becomes traumatic enough that you never forget. There's also the concentration and guts required to work while 5 managers try to make you think they're contributing to the solution while they're poking you in the back and asking if the DNS was initialized properly.
Personality test? Most people know how to fake those before they're out of community college. The best Net admins I ever knew never talked, they just got the job done. There was someone else to sit in planning meetings while the solution was being implemented...
by smactastic
Funny thing is how true all your post are.
Expected to be a expert in everything.
Never being able to say i dont know.
Always searching for the answer.
Do it all by yourself because nobody else around your knows!
this describes me hahaha!
by larry1246
by cybergoyle
I am a sysadmin for a small company (290 employees, 4 locations) and I am virtually a one-man show. Like Oz_media, I am responsible for marketing, web design, promotions, etc as well as systems maintenance, upgrades, future technology decisions, user training, help-desk functions, on and on. My title in the company depends on who is asking.
I agree that you should have the person write his own job description, but not without some guidance. When I was asked to write mine, it was merely one sentence: "Whatever the company asks me to do". Although my employer chuckled at my response, it is quite accurate. We all do tasks that aren't part of our 'job description'. Therefore, it is important that YOU have a clear idea of what this person is responsible for and what his/her job duties should be.
I would suggest you start by creating a job description that includes this persons obvious tasks, whatever they are (system maintenance, help-desk support, etc). Then give the description to your employee and ask him/her to make any necessary changes that they feel more accurately describes their job duties, whether they add or remove tasks. Too often an employee's concept of their own job description will not agree with the employer's; many times leading to unhappy (read, unproductive) employees. Haven't we all heard someone grumble about doing something that 'isn't my job'? I've found that this method can help me communicate better with employees. Unfortunately, talented people who become unhappy with their jobs due to a perceived conflict in responsibilities will leave before you even learn of their discontent.
That's my two-cents worth on the subject. Good luck!
by matspr
Louis,you should talk to Cat...
cat@techtv.com
She will help you. Matt
by dumbuser
I'd look for a network administrator that has a customer-service mindset. Instead of seeing users as people who mess up "his or her" system, that person should view users as customers. Customer service is the #1 job of anyone, especially a network administrator.
Our network administrator is universally hated because he is arrogant and condescending. That only seems to inspire people to try to find ways to screw things up just to set him off.
by jvellek
by michaelpo
by cybergoyle
>> Our network administrator is universally hated because he is arrogant and condescending.
How would you feel if you instructed your workforce on how to use MS Outlook to send email, only to have them repeatedly call you asking why they never receive any email (because they open Outlook, look at the empty inbox, and close it again never waiting for outlook to retrieve the mail)?
Insanity can certainly appear to be arrogance :)
by jtnieves
by mojo435741
by pleinster
by deanaltman
Let us not forget your new IT guy needs to integrate VoIP and legacy equipment into the internal communication landscape!
IT and Telecom groups have been at war causing companies to spend more money on each group instead of having them work together to find a solution to their problems.
Unified Messaging platforms are the new wave because when you have different sites from a merger or a new location and the boss wants to send a message to everyone using his own voice, he usually has to set up a voice bridge (conference call) or equivalent. Now that same boss can simply compose a voice message and broadcast it via e-mail and let the employees play it over their PC. What if their is no PC? Now you can use the telephone to access your e-mails!
The world is changing and I believe the fastest way to change and work with it is to hire the appropriate personnel who can wear multiple hats without covering up their whole head. Use the combined budget of IT and Telecom to create a REAL converged/integrated communications network.
by ristau5741
this is my checklist of responsibilities, supposed to be done daily, more than not it ends up weekly
all network administrators should be performing all these functions.
?x Check Event Log on all servers, create help desk task for any issues found
?x Check free space on servers, disk quotas, file pollution
?x Create new directories, shares, security groups, new accounts, disable/delete old
accounts; Managing account policies
?x Verify backups are running & restore works as planned
?x Plug Security holes, Operating System and Applications
?x Exchange Management, including, users, logs, etc.
?x Check network connections, switches, hubs
?x Check router logs
?x Check Firewall logs
?x Check all server services are functioning
?x Check that network server and exchange server anti-virus definitions are up to date
?x Run chkdsk and defrag on all server disks
?x Monitor WINS replication
?x Monitor directory replication
?x DNS updates necessary
?x Monitor server RAM for run away processes/memory leaks
?x Monitor Network Traffic to keep an eye on performance
?x Update operating systems and applications with patches / new versions
?x Monitor web traffic to FTP site for indications of attacks
?x Install software for users
?x Train Help Desk and end users as needed
?x Monitor user email for corporate policy violations
?x Check print queues
?x Keep up on entering Track-It tickets for all server work performed
?x Make sure all apps are shared
?x Permissions and File System management
?x Implement new policy, permission, logon script, or schedule script modifications
?x Change active monitoring/alerting as needed
?x Reboot Servers as needed
?x Keep up to date on IT news and security issues
?x Evaluate software for Network Administration purposes
?x Performance monitoring/Capacity planning
?x Audit network for unauthorized changes
?x Continue planning for network future
?x Management of off-site tape storage and on-site tape storage
?x IT System vulnerability analysis
?x Network Documentation
by jody
by smactastic
by voytech
by oz_media
Just to be really nit picky, I think most employers know exactly what they want, a hard working individual who will help the company move forward while increasing revenue or reducing expenditures.
The problem is MOST employers have no It knowledge and therefore have no idea what they really need. It is the job of a GOOD net admin to be able to explain what they bring to the table. Anyone can fill shoes but can they make a new pair that's better than the first?
An employee wiht certs and a pulse is one thing, an employee that brings valuable knoweldge to the table and actually applies it is a needed thing.
Don't turn up and expect that you will be told what to do and how to do it. It is YOUR job to know how you can improve the company's operations and reduce costs while even producing revenue.
Anyone can fog a mirror, MOST can foolow directions, that doesn't make them a useful addition to the company.
by luze.koube
by mikewbc
I agree that you can probably "Google" for the basics - i.e. Monitor Logs, manage user accounts, back-ups, etc.
The hard part to come up with are the specifics to your organization. As the only tech. person in a non-profit of 50+ users, my job title is Network Administrator, but I have to have working knowledge of: all OS from Win 3.1 to Server 2003, Fundraising Software, Accounting Software, Switches, how to run cable, wireless, security software, ISDN, current hardware, legacy hardware, troubleshooting, and even data-base development. I also have to work with Microsoft employees to get software donated!
In some organizations, the basics will cover 80% of the job requirements. In others like mine, the basics are only 20% and the other stuff makes up the rest of my skills. Good luck - P.S, Send me an application!!
by oz_media
If I had it that easy as a network admin I would have stayed on as a F/T employee.
"Primary job functions do not typically require exercising independent judgment."
You mean like a drone? Good employee, for someone else's company maybe.
I don't know how or where these websites come up with these "standards" as every company and every net admin has a different job requirement and description based on the company's size and needs.
When I was a Net Admin, I also was in charge of ALL advertising, web design, promotions, marketing. Hardware purchases, VERY independant decision making etc. I suppose that based on the guidelines you had copied above, I was not really a net admin whatsoever, I guess my cards were a misprint.
by voldar
you were more like an IT manager rather than a "simple" Network Administrator. I should know better that, because I did the same things you said, but I was called "network admin". What about the jobs on "SQL administrator" etc.
What I face now, is the fact that many people here, in Montreal, consider that being network administrator you can not provide reliable desktop support - what a BS! I did that and even more - trained the users - but yes, once, someone came out to me with a question like: "Did you also provided desktop support also?", smilling at me like a ... (you put the word).
And yes, let me also say, it is better the "manager" or "a member of the team" to right down the "job description", at least, he is supposed to know what he realy wants.
by voldar
read right down as wright down.
And also, if someone is not able to "create" his own "job description", maybe he has to "study" more what he realy does at work.
by oz_media
I keep a complete log of ALL network activity, updates, onsite visits, tasks performed etc. ANY time an employer wants to revaluate me, it is as easy as faxing some docs and all is doen. Yuo want a JOB description, I just forward the same docs. You want me to justify my time, same documents.
It takes about 15-20 seconds after each task to quickly note it in breif (ie: updated AV on server sent out workstation updates or whatever.)
Now I have a rock solid system to rely on for my client's needs. They get a virus, I show them the server was up to date. They get SPAM I show them the anti spam reports etc. Done deal.
As for me being the exception: patronize, patronise, condescend -- treat condescendingly
Cheers M8
by wordworker
by oz_media
You say the Cyber quill pen, definitely NOT my stronog point, you should SEE me type! Well I guess you have on that end, I hammer away at great speed but my fingering is all out of whack and I look at the keys so I miss the typos. Funny enough, when I don't watch the keyboard, I type OK, just not confident and fast enough to get anything one in a timely fashion.
I thought you were being patronizing or sacrastic.
If you were just having a chuckle and my mass collection of typos, then I'll accept that. I like to speak my mind (No really!)and that's about it. Much of my babble is from sheer boredom.
by michael roark - ccna/da mcp 3csa
Without knowing what you expect the NetAdmin to support, there is no way to properly write a job description that will cover everything. Questions such as these below will assist us in providing requirements:
Do you have Databases to build/maintain?
Do you expect backup operations? daily/weekly/incremental/full/etc?
Do you expect PC repair and maintainence?
Do you expect network electronics configurations/installation?
How many users to support? (include expected web traffic)
Do you expect Web services development and maintainence?
Do you expect Network Cabling installation and maintainence?
Do you expect Security expertise, on both internal systems, firewalls, security devices, wireless access managers, internet filtering devices?
You could go on for days, but I have to get back to work. There is a huge difference in requirements for a NetAdmin of a small company, vs a Fortune100 vs. a Education environment. Please let us know, and we could probably help you a lot more efficiently.
Respectfully Submitted,
Michael Roark
by dadavis5th
A network administrator is often someone who tises from the ability to learn and adjust in a fast changing environment. I you use certifications or education as measures, you will eliminate the most talented candidates because learning by doing and being intuative and intelligent are more important than formal training. Experience in an environment closely matching your needs is the key. Understanding that often the exact match to need is not available or will cost more than you desire is also key in understanding this issue IMO.
If you want more detail, ask your last admin who left for their resume. Make sure that you have a thorough exit interview so if the tasks were to diverse required to be reasonable or the load was an issue with leaving, then you can make adjustments in your selection and in the actual job definition you apply to the employee.
Hope this helps,
Alston Davis
Network Integration Analyst
dadavis5th@mindspring.com
by voldar
I quote you (if permitted):
"A network administrator is often someone who tises from the ability to learn and adjust in a fast changing environment. If you use certifications or education as measures, you will eliminate the most talented candidates because learning by doing and being intuative and intelligent are more important than formal training."
I wish I can see more wisdom "thoughts" like yours on the recruiters/managers of our days.
by fluxit
Networkers today are becoming more like phone company repairmen. They are outsourced and show up in a radio dispatched van with thier gut hanging over thier belt, butt crack showing, and with a huge ego.
Thier job description follows:
Must possess a good driving record, positive social skills, and excellent problem solving abilities. Knowledge of networking a plus.
by oz_media
You corrected yourself with the use of wright as opposed to right.
I believe you meant 'write' as in to pen something.
I don't ususally make a habit of correcting grammar here, I'm not one to talk but I know it is something you are trying to pay attention to as it is not your first language. Please accept this without feeling I am taking a pot shot at your grammar, you know I commend you on your command of English.
as far as me being an IT manager instead of a netadmin, this all started when I was hired, they asked me to write out a job description and tell them what I could do for them. I then used previous knowledge to build promo and ads as needed, sales tools, taught sales techniques to their reps. etc. As always I found myself a Jack of all trades agai, I just can't seem to do ONE thing, I get too bored. So on my cards they just said Network Administrator but cheif, cook and bottle washer would have worked too. Personally I HATE titles, they are simply a way of segregating yourself from others. It's like companies that want you to call the boss Mr. or Mrs. instead of Jack or Jill, my theory is "get bent" you can use MY first name but I have to address you with some form of higher respect? Piss off, and who the hell do you think you are you stuck up idiot of a loser. People that run companies and put themselves ABOVE the staff who keep their company operating and productive are just way off base in my opinion and I simply will not work for them.
A manager at one of my current contracts is listed in my addy book as A**hole (uncensored) all my mail to him is addressed to A**hole, he lives with it because he knows I am not going to bow to him and kiss his butt like some of his employees do. At least he can determine my email from SPAM, they use real spoofed names.
Bottom line I guess, if you think you're all that great, you will work alone perpetually because nobody else is gonna but it.
by voldar
This is realy embarassing - sorry - when you make a mistake, it's human, when you make TWO on the row, well .. I say no more about me.
Of course Oz, I am not the all mighty, but well, I know what I know. Should I hide what I know to have a job? That was another discussion I wanted to start here, but well, ... I think is not the best timming.
by oz_media
You say to make two mistakes in a row...
Well, I often make two mistakes oer sentence for an entire post. People either get used to it or simply stop reading them, either way I had my say and couldn't care less how it is received.
Don't worry about it, ALL mistakes are okay unless you make them specifically to piss someone off, which I know you don't.
by voldar
less left brain in a male dominated hierarchical political environment would help. After the crash you think we would learn. Some left brain neutralizing and right brain trancing. Degrees and Diploma's are Neccessary but not Sufficient. Like the greatest Geometrical Theorems, those that are not both are not at all proofs. Of course if you really want to know how well someone will respond; Use Post It Notes. During the interview you tell them the entire network just went down and all you have are these Post It Notes ( a white board too). Could you build me some trees and binaries to keep the basic system (network) functions operating? The only reason networks exist is to fail. Just the opposite than the popular view. It is always about Disaster Recovery. Every day is the begining of a Disaster. If it went well you have been fortunate. What is your contingency plan? If the network functions well it is because the network functions well. Very rarely is it because of the administrator being good at the job. If the network fails it is certainly the admins fault.
Concentrate on disaster. Take down the network and see what happens. Can you rollover into a stable configuration. Good pilots read NTSB every day.
by louisg
Wow, I'm sorry I asked for help on this site. A simple I can not help would have done it for me. I do not have time to read all the nonesense that was posted.
Thank you anyway,
by voldar
I now understand why you are so lazy - not much brains, one question and some sarcastic remarks.
I hope you never expected things like:
"A network admin should do:
1. this
2. that
......."
and so on.
If this is what you were expecting for, well, maybe you should think moving to a new carrier. And for God sake, do it fast, and don't think about a carrier in computing or computers-related, as long as you are not able to use google to search for a simple "job description" item.
I'd ask from you too much if I?d say that YOU should create the job description by yourself, because you are the man "who does the work", but I think you don't even know what you are doing at work.
Have fun, Mr. Nonsense!
by oz_media
see you're getting the hang of this English junk no problem!
It's refreshing to see another peer who calls it as he sees it. People don't seem to be used to hearing the truth so much anymore.
By the way, 'carrier' is someone or something that carries something. IE: Mail carrier, carrier pigeon etc.
'Career' is the focused line of work you were referring to.
But your point is well made either way. ;-)
Have a good weekend!
OM
by jcalexandres
I think this will be the closest description about the Metwork Administrator job position:
Responsible of general network operation at all levels.
Administers all computer systems on a network.
Coordinates deployment of custom applications with in-house or outside developers.
Ensures network security.
Coordinates with other IT personnel researching, testing, and implementation of system upgrades of any type, providing decisions on aquiring the right equipment and software.
Determines the right estrategy to implement or execute a backup and recovery plan, including step-by-step documented configuration of critical business operation systems.
Coordinates IT outsourcing with suppliers and communicates with upper management to provide help on IT-related decisions.
Coordinates with upper management and other IT personnel, on implementing Internet content and access policy.
On-call availability on mission-critical business operation.
Provides trouble-shooting solutions when IT elements at the 1st and 2nd level are not successful.
Jorge C. Alexandres
Network Administrator
The Flower Factory
www.flowerfactory.com
by kudin
> There's also the concentration and guts required to work while 5 managers try to make you think they're contributing to the solution while they're poking you in the back and asking if the DNS was initialized properly.
Haha mxyzyptylk. Though I only have 3 managers poking my back during any crisis, there really wanted to be the first to push me to get the problem solve so that they would get the "name" as if they are the one who actually deserve the credit.
I don't care about the credit, I just care about my salary. FYI, if based from salary.com study, my salary is in the category of an operator though I take care of a data centre with about 18 servers and appliances (coming more soon) and using an open source NMS, with code modified for my environment.
And for the DNS, actually only 2 of my collegue that knows DNS is a very critical server in any organisation that run servers accessible to the Internet. In fact no one of my manager actually understand how the DNS works. Only one understand it and it is just because I took 1 hour to explain it to him.
> The best Net admins I ever knew never talked, they just got the job done.
Well, because it is difficult to make your so call "IT Manager" to understand the importance of what you are doing in IT... Of my 3 managers, one of them like to cut off my explaination by giving out stupid argument as if he knows what I'm talking about. For example, one day he asked me to pass monitoring servers and appliances to an end-user and teach her how to do it (without telling me to use any software/NMS to do it, it kind of manually using dig, hping, wget/IE, etc). Wow, even if she could do that, just imagine how much frequent she have to do it.
And that is why actually I can say, more than 70% of network admin or network-related admin in my country are underpaid.
>There was someone else to sit in planning meetings while the solution was being implemented...
Yeah, meeting, and then giving out minutes of meeting to the top management or to the employers and they will say, you have done your job. That's what I called "getting credits".
by voldar
In fact I am not proud for the fact that I had to say what I said, but when I see arrogant people who blame/diminish everybody's work but themselves, well, I can't stop to stand up and say what I think about them. If a statement as above never appeared, I'd never said anything about that person. Hmmm .. makes me think to the fact that "every bird dies by the way she sings" (I don't know if this has any correspondent in english, but it is very common in another language I spoke).
About carrier = career, well, a carrier means (or I am wrong?) also delivering services, isn't it? Anyway, yes, the better word was career.
by ohwell
by allisen
by acephale
Thanks lots of good info here.
My dilema is this, i am a student, i finish in a couple of months time in electronics engineering. I want to break into it and think that network/system admin is something i can do. Electronics is a bit dull. Anyhow all the agencies i apply for ask for at least one years experience. I have a home network and i run win 2000 and i tinker around with 2000 server too. im doing my mcse at the moment also. I need to blag the interviews to get a real job so i have the experience to get a job, it is a viscious circle.
So should i say that i was a support network admin role or what or just say that my first job i did everything. i dont want to be blown from the water in my first job you see
this is critical
any extra advice?
by jcalexandres
I basis of the experience you have, I will suggest you to apply for a job in IT at entry level, kind of A+ type, which is more related to hardware, once there you can work your way up the IT ladder, getting more involved with networking and the networking OS, which a lot of companies use Windows, Novell, or a mix of both and main frame schemes.
In these days a Network Administrator need to know routing equipment too, so get your self some lecture on TCP/IP, routers, firewalls, and VPNs.
Good luck! Maybe by now you already landed a good IT job!
Regards
by techsoeasy
If you search for the exact words that were typed as the subject of this thread, network administrator job description" you'll get at least 20 to 30 samples.
My answer was succinct.
by bobby_q_doe
This discussion is closed to new replies.
Sort by Trending