What I need to know, be able to do - to be a good -> great network engineer - IT specialist [serious]

[Vintage89]

I know that 'information technology' is a powerful field in which there are many sub-fields such as programming or database management.

But I would like to know exactly what I need to learn and what I must be able to do to be a good or great network engineer.

Let's assume this format: Nnetwork engineer / IT specialist *
1. Beginner - network engineer: can design a network (e.g. in Cisco Packet Tracer), knows e.g. routing protocols, can connect x, y, z from scratch, can configure a computer or e.g. a WiFi access point, a single network device e.g. CISCO companies, knows what it is, e.g. ACL, etc. Can create queries for databases (insert, update, set, etc.) He knows a little bit about data protection :) He can put and install systems on virtual machines, e.g. Windows Server 2010 or 2016 and do something on them etc ... knows the basics of Linux / Ubuntu
2. Good - network engineer:?
2. Great - network engineer: ??
4. Master - network engineer: ???

e.g. you need to know x, y, z and understand it, be able to do x, y yourself and with the help of others 'z' (because it is very laborious - not because it is difficult :>)  have certificates: a, b, c | be able to configure from bases the most popular devices from CISCO, Netgear, ... etc.

* I am aware that the question mainly concerns computer networks but the IT profession <at least in my environment> is associated with "knowing" parts-of-everything or at least sub-fields directly in contact with the design / implementation / management of networks. ^ _ ^

something else ?

[Leo Laohoo]

---

@Vintage89 wrote:

I know that 'information technology' is a powerful field in which there are many sub-fields such as programming or database management.

---

The term "IT" is a BROAD definition.  It is like saying I'm a doctor or an engineer.  

---

@Vintage89 wrote:

Beginner - network engineer: can design a network (e.g. in Cisco Packet Tracer)

---

A beginner network engineer designing a network?  In school, yes.  In the real world, fat-chance and not-gonna-happen.  

This is not a "game" where one can just "level up" at a flick of the credit card.  

NOTE:  The line below is not aimed at the OP.

Cut-and-paste school work here (and hoping someone can/will furnish the answers) is not helpful.  CCNP does not stand for "Certified Cut N Paste".  

[Vintage89]

Tag - serious - means that I am not looking for 'junk' / xoxo / 'you know nothing Jhon Snow' / answers - I am looking for answers from people who with their experience and the amount of time spent in the field of computer networks - they know what they meet with 'every day' administration of large-complex networks - I am looking for a description of the right attitude - and knowledge (mind set) that distinguishes such people - and they are able to objectively / subjectively list the features and elements of their knowledge - and what this knowledge consists of (what abstract systems and definitions - and their practical usage in the years of their experience make up this).

[Mark Malone]

if your trying to find out someones ability as an engineer there specific level, best thing is to ask real world scenario issues that come up daily , many engineers face same type of issues and depending on how they handle them or understand how to tackle them in a real world scenario then that usually shows the level they operate at , anyone can pass a memory test so i always avoid asking questions like that , most engineers will also probably want to show you how to when explaining it , draw a topology , path flows , what they think may happen and how they would tackle it or avoid it . to me a good engineer can break down even a complex issue and show someone who is not technical what the issue is and how they will go about fixing it

if you want to know this stuff you have to watch all the videos read all the books and then LAB until you know it inside out its the only way and it takes a lot of time , dont try an be an expert in all fields, it wont work theres too much chose 1 or 2 and follow the paths specifically , like security or networking etc but then dont do voice , as a junior engineer you just do what ever your given but when you have some exams under you you can chose your path yourself

[Vintage89]

"to me a good engineer can break down even a complex issue and show someone who is not technical what the issue is and how they will go about fixing it "
Yes this is golden rule - on all 'fields' - if someone is unable to explain something simply - it means that they do not really understand it

[Vintage89]

but also: "anyone can pass a memory test so i always avoid asking questions like that"
can u set some sort of list of things that should be known - defintions of what - protocls, implements of smth, kind of checklist? - where I can check if i even heard of smth like this or know that smth %like% can appear in this work? It will be very helpfull for me.

[Mark Malone]

i dont really do lists mate , its not really what the forum is about but if you have a quick google you can find stuff very easily like this below what can guide you what to check

https://learning.naukri.com/articles/network-engineer-interview-questions-answers/