How best to proceed in the career of a network engineer?

People are so interesting 30 years very interested in being a network engineer. I only get higher (engineer-programmer). Almost finished the Network Academy Cisco then I will try to get the CCNA. The question is where next ССNP, SSE or develop will shift to SDN? Anyway 30 ku whether who will with no real practical experience. Still the guru of the fathers of the engineers give)! What is really valued in the market now?
September 19th 19 at 00:04
4 answers
September 19th 19 at 00:12
I don't think dying. the main thing is to get into the stream. started as office administrator, 10 years ago got into the isp. there is a year and a half was sent to SSN (although most is still learned, from friends/acquaintances/Google), visit the cisco expo. in General, there natahala. the isp was based solely on cats (core, distribution and aggregation). now you have to get somewhere where you can gain experience, because SNA/ssnp without experience is not very a lot of sense (after SNA often asked for solutions to life situations the teacher their - have they helped very little). but, the man with no Sert - rescued always (someone in a backbone isp)
September 19th 19 at 00:06
Almost finished the Network Academy Cisco then I will try to get the CCNA. The question is where next ССNP, SSE or develop will shift to SDN?
About the direction of education - I believe that all these magic SDN, which do nothing, and everything, is of course great, but the base (routing&switching) for normal operation is required, so you should concentrate on it. In parallel (but not at the expense of the database) - Linux/FreeBSD at the level of the unfolding and support of monitoring servers (nagios, cacti, zabbix), programming at the level of basic scripting (I suggest python, but then on your taste).

All these "cloud-based distributed fault-tolerant solutions" beautiful, still working. In the event of a crash abruptly requires someone who understands what lies behind the veil of marketing terms.

About the certificates. Better to spend the money of the employer than on your own. If you decided to pay yourself, then look at Juniper (JNCIA-JunOS and JNCIS-ENT) exams are less organized, in my opinion, much more correct and more convenient (cisco-bukvoezhka I have not found), documentation and tutorials on the Juniper website is also good.

Success!
September 19th 19 at 00:08
In my opinion - appreciated value.
At the interview, you can tell a compelling story about what went on courses and what problems were encountered. Can embellish a story that organized schemes do not stand on the Elbe, such as finding freelance orders on the stock exchanges of odesk type, fl..
September 19th 19 at 00:10
taking into account clouds and global automation is more of a dying region, hope soon all switches will be programmed and die Cisco with his "perfect" interface for people.
: separately. *need help to learn the buttons, and bookmarks - knock will help =) - Kaylah49 commented on September 19th 19 at 00:25
PIP you =) I want to work! ))) - Kaylah49 commented on September 19th 19 at 00:13
: well, you climb to a collapsing market, the administrator must, in a global sense, to die, of course will remain a common devops, but the market will shrink significantly in the coming years. - Everette56 commented on September 19th 19 at 00:16
back to this conversation in a couple of years =) - Kaylah49 commented on September 19th 19 at 00:19
while there is security, the need to isolate the network, and log them from each other. While there are so many curves and vulnerable protocols - network engineers need to be long.
How old is ipv4 and how much ipv6? And the second has not yet replaced the first.
Of course the GUI will replace the console control and people will just press the buttons. But the question will arise "who understands the protocols supposedly lacp, bgp, ospf, eigrp," and also encryption, static routing, and most importantly - the ability to understand what the problem is in the network, why is there something buggy or not pings.
Today, while there are so many protocols, especially the vulnerable protocols and network engineers are needed in any case. Ability to work in console IOS is not really a complicated thing, like the console of Linux. It is scary the first time is not clear, but quickly realize what was happening.
Another thing, when you're dealing with different protocols and you do not have enough knowledge to understand "what do those letters?".

Take the same windows as an example. The work it can almost everyone, but how many people know how to work with its snap-ins to work with GPO and other features, about which 99% of ordinary people even never heard of?

That's when there will be one common Protocol for the network transmission of data, standardized and provided for all, then we can talk about smart switches and routers that have one button for all occasions.

But when I take the same Mikrotik. The abundance of buttons, bookmarks and letters cause me more difficulties than the console. - dina_Predovic commented on September 19th 19 at 00:22

Find more questions by tags Computer networks