Question:
Need a Network Administrator for a class project.?
Spyder
2014-03-28 08:36:17 UTC
I am currently seeking a Degree in Information Technology with a focus in network administration. For one of my classes I need to conduct an interview with someone in the field I am interested in, and thought I'd give this a try. If there are any Network Administrators that have aa few moments to answer some questions I would really appreciate it.

First state your name, and the company you work for.

1. What is your job title?
2. What are your responsibilities as (job title)?
3. How did you find your current job?
4. What is your favorite part of your job?
5. What is your least favorite part of your job?
6. How many hours do you work a week on average?
7. Would you recommend others to this line of work?
8. Did you at any point consider a different career path?
9. If someone wanted to go about getting a job similar to yours, what would you recommend for him or her to do?
10. What advice would you give to someone who was about to start work in your position/ line of work?
Three answers:
Ty Zang
2014-03-28 10:09:43 UTC
1. What is your job title?

It was Network Administrator, but now its a fancy Technical Support Service 3. Same thing.



2. What are your responsibilities as (job title)?

My main responsibilities are to support end users, the infrastructure, and to continue to update the current setup. I do anything from software installs, troubleshooting network issues, standing up new applications and servers, and much more. Some projects are like researching Patch Management software, and implicating it. I deal with Linux, Windows, and Mac OS.



3. How did you find your current job?

Internship out of college. I was set to go to a hospital but ended up getting a call from my resume being on some websites. This was paid!



4. What is your favorite part of your job?

Being able to learn new things every day. You will never not learn something day by day. Experience is everything!! You can have as many certifications as you want, but it is all about experience.



5. What is your least favorite part of your job?

To be honest, the end users. Everyone's ticket is "high" and when things break, you are the villain. Its a very unrewarding job in the eyes of employees. You are thought of when things break.



6. How many hours do you work a week on average?

40 hours but I am always on call so it can go up. It's not too common to have to work at night as we have multiple techs who take turns being on call. Most things can wait till the next day. Once you get multiple time zones involved, it can get annoying.



7. Would you recommend others to this line of work?

Yes, i enjoy it. It takes a lot of years to get good, so don't get frustrated right out of college.



8. Did you at any point consider a different career path?

This was my second choice after I gave up on multimedia. I would love to get paid to play hockey!



9. If someone wanted to go about getting a job similar to yours, what would you recommend for him or her to do? 10. What advice would you give to someone who was about to start work in your position/ line of work?



These go together. Look, everyone should go to a help desk for their first job. I started out at a ISP fixing peoples networking issues without ever seeing their screens, or being there. You develop the best skills here because you learn what to ask, and when to ask. You learn to be professional. It sucks but spend a year or 2 doing this. It will make getting a job so much easier!



Experience is everything!! I cannot tell you how many times I deal with people who have all these fancy certifications, but are horrible at their job. I just saw a Y! answer where someone above me dove into the craziest troubleshooting steps. His Sources were his cisco certs.. I solved the issue by asking the right questions. Don't skip the whole "is it plugged in" step. Most issues are user error.



Don't get frustrated. When you dive in after college, it will be overwhelming. I take my Net+ cert next monday, and I have been in the field/studying that cert for 4 years or so. I finally feel confident. Look into certs like A+ and Net+ because they are invaluable, but don't depend on being book smart. YOU WILL NOT UNDERSTAND THIS STUFF WITHOUT DOING IT. Look up professor messor / total learning / michael Myers books and videos. Best books



So get experience when you can, do a help desk, and try,fail, learn. Here is the Network + troubleshooting steps which, print them out, and place them at your monitor. Following these will get things solved



1) ID symptoms of the problem. ID the Scope of the problem. ID if anything has changed. Gather logs and information



2) Establish Probable Cause. What can cause these symptoms?



3) Determine if you need to escalate the issue.



4) Create an action plan/solution. ID any potential effects from this. What will this break? Either Repair it, Replace it, or Ignore it.



5) Implement the solution and test it. Did this break anything else



6) Document the solution!
Paultech
2014-03-28 15:47:20 UTC
1. Senior network Administrator

2. Manage & Analysis of windows servers/network

3. Started at bottom level within company and moved up.

4. Fault finding/fixing.

5. Having idiots think they know more than me or how to fix the issue, when they clearly have no idea

6. 40+Hrs with upto 20+ on call.

7. Only people who enjoy the challenge, and can deal with the stress of the job.. and enjoy working and learning all the time

8. Yes, being a professional poker play.

9. Attend College/university with course in networking, not computer science since that covers mainly programming and design. Or if at starting level, do eg in order A+, Security+, Network+, MCP's in Windows 2003/8, MSCA, CCNA/E/i/P.

10. Avbid ripping your hair out due to the stress you'll be under with people shouting at you to get it working faster. Keep testing yourself on different aspects of the work.
Krowten Nimda
2014-03-28 17:13:14 UTC
1. What is your job title?

Network Administrator



2. What are your responsibilities as (job title)?

Network maintenance of our wired and wireless networks on multiple campuses.

Network design and implementation

Troubleshooting

Information security

Provide technical support, mostly for other IT units, but sometimes for regular users.



3. How did you find your current job?

Started as PC Tech in the organization and worked my way up.



4. What is your favorite part of your job?

Working with new technology and continuing to learn more about the subjects I already know. I don't provide direct support much anymore, but its nice to know when I've help fix a problem for someone when I do.



5. What is your least favorite part of your job?

It can be stressful in a lot of different ways. Me and another guy are responsible for around 20,000 connections spread out across multiple locations around town, and that's it. This is a specialized field, so most people you work with (even other system admins) don't entirely understand the issues and it can be difficult to explain problems, or why a particular solution to a problem isn't ideal. Imagine trying to explain how TCP works to one of your relatives. Its about the same experience when trying to explain it to 80% of people who work in IT.



6. How many hours do you work a week on average?

Now I work 40 hours solidly. When I first started the network wasn't as organized and quite a bit went into day to day maintenance on top of new stuff, so I probably average 50-60 hours then.



7. Would you recommend others to this line of work?

Depends on the person. This job isn't particularly hard, but there are some qualities that a network admin has to have. I've met several other successful admins in the same market as me (higher ed) and noticed certain traits. First, you need to be able to work well by yourself and with a team. Both are very important. Most of the time your on your own, as no one else understands what's going on. At the same time, what's a network with nothing connected? So you need to be able to work with other people, most of whom don't understand what's going on, to get the requirements to make their application work on the network. You have to "own" the network, take as much control of it as possible. If you don't people just plug stuff in, stuff gets broken, messes are made, and you have to fix it. Some people might see it as arrogance, in which case you just need to soften your tone but not let up. I guess to sum it up, I believe a successful Network Admin needs to be intelligent, proficient, have good people skills, and confidence in theirselves.



8. Did you at any point consider a different career path?

No, I've wanted to do this since I was 14.



9. If someone wanted to go about getting a job similar to yours, what would you recommend for him or her to do?

9 and 10 look the same to me. I'm going to assume in 9 you are asking about what you need to start down the path and 10 is about looking for a job. I don't know how much a college degree is necessary for this job. It certainly doesn't hurt and you might pick up some knowledge that might be helpful indirectly, but most college programs don't have much that will actually teach you network administration. I only had 3 classes related to networking. Two were a look at how data communication occurs and one was basically a CCNA prep class, which we didn't really get that far into. I do apply some skills and knowledge from a couple other classes (such as project management), but I'd have to say 90% of the stuff I learned wasn't usefull. I'm NOT saying don't go to college, just sharing my thoughts.



Trade/Tech School can be a supplement or replacement to college. A Trade School will teach you the skills for network administration only, without having to take additional classes. For instance you can take a CCNA or A+ course at the trade school in addition college to get more job skills versus general knowledge. If you only go to a trade/tech school, you can take other related classes, such as computer repair, to get additional skills which are also useful and will probably get you that first job. Trade schools may be quicker and cheaper than a full bachelors degree. However, this might bar you from some job openings that require a bachelor's degree.



Certs are good for getting a job, but not much else. I'd recommend an A+ if you don't have any experience with tech support. It can get your foot in the door. If you want to do network administration most people will require CCNA, even if they aren't a Cisco network. The CCNA requires enough general knowledge of networking that's considered a defacto standard cert for network admins. I caution against getting more certifications without job experience. Too many certs and little experience can impart a sense that you lack focus.



Experience is the thing I look for the most. There's a lot you cannot learn in a class or a book. You probably won't get a job working on a network right out of school, unless you are already working in an IT organization. Networks are expensive and have become as important as electricity to a business. No network means no website, no orders, no email, no business, no money. They want people who know what they are doing.



10. What advice would you give to someone who was about to start work in your position/ line of work?

Start at the bottom and work your way up. Experience is key, no one is going to hand over the reins to their network infrastructure if the applicant doesn't have at least 5 years of real experience. If you think you are going to go to tech school, get a couple certs and get a job as Network Admin right away you are probably wrong. Its just like any other job really. You have to start at the bottom. If that means you are manning the phone at the help desk, that's what you do. Its still experience, and those skills learned in those early jobs are used forever.



Hope this helps


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...