What is Your Specialty and How do You Like it?

I am currently working as a Help Desk grunt for an MSP working to gain the invaluable experience that any IT career depends on. In 6 months I have broken ground and become proficient at level 2 support and am on the fast track to becoming a level 3 helpdesk/ Field technician. But I digress, I have made a resolution to get my security+ and CCNA in 2013 and double my salary (Set your goals high my mom always said) which, considering the pay that I receive now, will be hard but doable. Now that I have gotten a better peek in to the IT world and the different facets involved, I have been giving quite a bit of consideration as to what I would like to specialize in after getting my CCNA whether it be security, databases, VOIP, etc.
I was just curious as to what some of your specialties are as well as how you went about gaining knowledge in that area and how it has affected your career. I would love to hear from you guys and get some inside info on the different areas of the IT field...
I was just curious as to what some of your specialties are as well as how you went about gaining knowledge in that area and how it has affected your career. I would love to hear from you guys and get some inside info on the different areas of the IT field...
If you havin frame problems I feel bad for you son, I got 99 problems but a switch ain't one
Comments
Service Integration
Process Improvement and Redesign
Transition Management
Moving into Project Management and Security
I do like what I do, but I am really looking forward to managing a provisioning team rather than a support team.
So far, I like it a lot. It can be repetitive, but there are tons of opportunities to improve on the audit process (i.e. attempting to automate certain portions, improve on the system/device configuration guides, write/amend policy, etc...)
The project I'm currently on is ramping down so I'm seeing what will happen next. But usually it's a mix between managing all of our Windows VM's, as working with our "official" Info Assurance group on Windows policies, security, audits, etc (they realized early on I know my s**t so we've had a good working relationship and bounce ideas off each other).
I also dabble a little bit with project management and SCRUM.
My career path has led me this path because of the demand of where I live. If I had my dream job I would be doing more infosec type stuff but I don't live in a huge city so it's hard to come by. I started out by trying to learn everything: Windows Server, Linux, Unix, Infosec, Networking. I continue to try and learn as much as i can about all these things which I feel makes my decision making better because I understand the big picture.
I started out as a PC technician in high school. This helped me understand customer service as well as why we have jobs in the first place in IT. If we didn't have end-users what use would we have for any of this other stuff? No matter how high you climb on the "IT ladder" your end users are always the ones who use the technology. This key bit of information I feel has been extremely useful to have since the beginning.
While I was a PC technician I was in college and took a CCNA course. I studied like mad every weekend and day for a summer and passed it with a 517 (required a 515). This was in 2007 when there was no CCENT. During the same time I had obtained A+ and was working on MCSA 2003. Yes, I was pursuing 3 different categories (windows server, networking and still PC support). It was because I had all three categories that I was able to get my next job, after working 3.5 years as a PC tech.
I became a network technician at a small-mid size business with 500-600 employees (my first corporate experience). I was mostly half help desk (the only one) and half sys admin. I grew from half help desk half sys admin to full time sys admin and because of how the company was structured I ended up doing all Windows server administration, backups, some linux, Cisco ASA firewalls (VPNs), switches, implemented a SAN and VMware. Had I not had the knowledge from my studies (MCSA, CCNA, A+, Network+) I think it would have been very difficult to stay afloat.
After 4 years I outgrew the company and saw that I wasn't going to be able to go any further in my knowledge. By having the certifications and the 4 years experience I was able to get a job at a company that supports large businesses in the Silicon Valley. I was solely focused on network engineering at this job. I learned a lot but worked my ass off. After 9 months decided that the California culture (50+ hrs/week) wasn't for me and got my current job.
I now work for a large corporation and have been able to take advantage of some downtime and get a few certifications while I've been here (JNCIA, JNCIS, CCNP). My career has been a slow process of building up experience from projects and certifications. Certs don't substitute for experience but it sure makes it easier to get experience.
My opinion is that the certifications gets someone to look at you but you're the one who pushes yourself to build that experience. Self-study has worked great for me because it's usually cheaper than paying for a class, haha
Sorry for the novel, I wrote this because I feel that it would have been useful to me when i was starting out. Aside from that, I say you're on the right path man! PM me if you have any questions.
What are some early wins to look for in an Access Management Team?
Just curious you sound like you have a good idea.
I can give you the best advice I can give that I use to really understand subjects... That is, try to understand the PURPOSE behind why things are the way they are.
When asked (like in an interview of the thread I just last responded to) "What is the difference between routing and NAT?" then you could "answer" that question if you understand WHY there is routing and WHY there is NAT. Even if you don't know exactly how NAT is encapsulating packets, having the reason WHY NAT is around will be the ground work to help you expand your knowledge on the subject.
I don't really know a whole lot about NAT. But I can understand when network engineers are talking about how it is frustrating it is, I can see through my base knowledge of NAT, that it would be hard to track because you are trying through a trick process to hide the internal IP addresses as best you can at the same time keeping a way to get back to the original requester of the information. NAT came around to use non-internet routeable IP addresses on the LAN side as private addresses. Then when I want to drill into the subject more, I always relate it somehow back to the overall purpose. This builds a whole puzzle in my brain where I'm adding puzzle pieces one-by-one until I get the whole picture.
You may learn something!
I still have to do some help desk stuff so I'm not quite where I am and I really have some holes in my learning but I'm getting close to where I want to be and I love it.
Me too. Looking to lean UCCE/CVP in 2013.
CUCM SRND 9x/10, UCCX SRND 10x, QOS SRND, SIP Trunking Guide, anything contact center related
The bill payer is networks and IT consultation. It's also good
I think this background of how to approach problems, and presenting my ideas to peers has stood me in very good stead for working in IT. I am happy to take on work that I don't have any experience in, because I am confident that with in a short space of time I will be able present a clear and complete solution. It has server me well enough that I have moved from an entry level help desk position 5 years ago to the network consultant for the network insulation in a new world leading research lab among other things.
Success in IT is not about the volume of knowledge you know (although that helps), take any single field of IT and any sub field within that, and the volume of raw knowledge it contains will outstrip even the most experienced of engineers abilities. My chosen Direction with in IT is Core Networking and Security, although my experience and skills entend in to AD, Widows server, VMware, Voice, Wireless and indeed most areas in the IT world.