Compare cert salaries and plan your next career move
Paul Boz wrote: » Please take your time and learn the material rather than power-cramming to get eight tests in 12 months. No offense, but you don't even have a CCNA yet. What makes you think you'll even be able to pass the exams with only 45 days of study each? I spent eight months alone on the CCNP and its not because I'm a slacker or because I'm slow. Set your goals a little more narrow and you'll see them through.
networker050184 wrote: » If you think the CCSP will help you more then just concentrate on that. You are going to be spreading yourself pretty thin trying to get all these exams done. The goal should be knowledge, but I don't think that is why you want these certs. You are trying to run full speed into being a paper cert. You barley have any experience yet want every pro level cert under the sun. My advice would be slow down, learn something and take it one exam at a time.
dynamik wrote: » Well it's 15 months from now until the end of 2010, so the eight pro exams come close to being averaged out to one every two months. That's shortened a little since ICND2 is 12 days out, and I'll have to squeeze in CCNA:S somewhere, but I don't think makes things impossible either. It's just a challenge; if it takes an extra 3-6 months, so be it. I'm just going to keep plugging away and see where I end up
networker050184 wrote: » Have you ever stopped to think that maybe you are not a network engineer because you don't have the experience to be one not because you don't have the certs? Certifications are great to go along with your experience, but you are trying to fast track and skip that experience step. I'm not trying to be a jerk to you, but you need to keep your expectations in check and your goals realistic. If we thought your plan was great and realistic you wouldn't be getting negative feed back here. People that have been in your shoes are just trying to give you some sound advice. This is all my opinion and take it or leave it, up to you.
knwminus wrote: » networker and Paul are concerned that I may be setting my goals to high or chasing after something that will not be obtainable.
knwminus wrote: » But the thing is how can I get experience as a network engineering if I am not a network engineer? Riddle me that lol But yes I do know what you mean. really I do understand what you are saying. How did you get into network engineering?
shednik wrote: » I have to agree with the majority here...I have a little over a year and half of experience and I'm not ready to grab an NP or SP yet. Just learn don't worry about the piece of paper, you can rush through this and it will show even if you get the new job. Do you really want to move up when you're not ready and potentially embarrass yourself or worse cost the company alot of money because of a mistake due to inexperience? We've all made mistakes and it will happen, but without experience you may not be able to catch it or fix it. Just stay in the NOC for ATLEAST a year gain some experience and keep studying. If something comes up beforehand give it a shot but don't worry so much about those letters at the end of your name. You have a job already and want to move up in the company...try excelling at your current position(not saying you don't) but delivering excellent results will get manangements attention alot faster then a piece of paper trust me.
networker050184 wrote: » You get to be an engineer (and job titles are stupid, I'm more referring to the level of work being done rather than what your title is) by working with the stuff at a lower level for a while. I was in the military for six years doing networks and worked my way up from managing one router to an entire network over that time by proving my knowledge at a lower level and showing the aptitude to handle more responsibility. I wasn't working at this high of a level from the beginning. There is a lot of knowledge to be had studying for certifications, but its probably only about 25% of what you need to know to be a good engineer. The rest comes from working with the stuff and and learning how it really works, and not the perfect world book way. In case you are wondering, I started in my CCNP after having over six years working with this stuff and it still took me over a year. Sure I could have probably powered through and got it done in half the time, but I wouldn't have gotten out of it what I did.
networker050184 wrote: » IMO you are right where you need to be to get the experience needed to move up. Once you prove you have mastered your current position, you can ask for more responsibilities and the opportunity to move up. You don't just go work at the highest level because thats what you want. Those aren't entry level positions and no matter how many certifications you get you are still entry level in the networking world.
knwminus wrote: » Fair enough. I just don't think me (as far as knowledge) to sit here and ping, telnet, sho commands and then have someone tell me to route it. Sigh
Paul Boz wrote: » Man my old NOC job was basically this: Come to work, sit in front of some monitors / big LCD TVs and watch alerts from HP Openview and a few other system monitoring services. I also processed troubletickets from customers over night. I did ZERO network device configuration but I did learn how the devices interact and read the configs to see the real world implementations. You can PASSIVELY learn as much as your mind is willing to allow without ACTIVELY handling the equipment. Do you guys have a topology diagram available to you? If so, study that and make sure you understand why devices are placed where they are and understand what they do.
ColbyNA wrote: » Going from the CCNA to the CCNP is a huge leap, the material is exponentially deeper and without a lot of hands on experience it's difficult to pick it up quickly.
ColbyNA wrote: » It's great to have goals, but I've always tried to take things one step at a time and not plan too far ahead.
miller811 wrote: » How can you secure a network unless you know routing and switching first?
kryolla wrote: » Start volunteering to help out on projects even if it means on your off time and start poking around and ask questions to the upper level engineers you might get crap work that they dont want to do. This will show to management that you are willing to learn and after a couple of projects they will know if you are cut out to be an engineer or not. Thats what I did, I worked during the day and helped out engineers at night then when a slot opened up I was recommended. Just because you get a cert they might not bump you up or they might bump you up and then ask you to get the cert. My 2 cents
dynamik wrote: » especially when you're working with more knowledgeable people.
networker050184 wrote: » You two need to move your bromance over to PMs. That's what they are for
dynamik wrote: » We have an internal Jabber server and all our communication is encrypted with OTR. I'm not going to lie; things get pretty hot...
ColbyNA wrote: » I LOLed, hahahaha. When I worked with Networker109323290320932093290 we used to bullshit over Communicator all day. Usually making fun of coworkers.
veritas_libertas wrote: » They do have a tendency to follow each other from thread to thread
Compare salaries for top cybersecurity certifications. Free download for TechExams community.