Timeline for "network engineer" terminology
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2013 at 21:16 | comment | added | Mark | What @nathangiesbrecht said also stands in some US states. IIRC South Carolina and Texas are both picky about folks claiming to be an engineer without holding a current PE certificate/stamp from their state. It made my dad so mad (Civil Eng. in multiple states) that I actually fought against being titled an engineer in one job to keep him happy. ;-) | |
| Apr 5, 2013 at 0:56 | comment | added | phoebus | @theCleaner is quite right. At the very large managed and cloud hosting provider Where I work, "systems x" and "network x" titles have a hierarchy of seniority that basically goes technician->administrator->engineer->architect. | |
| Apr 3, 2013 at 16:38 | comment | added | nathangiesbrecht | In certain areas, like Canada (I believe) the term "engineer" is actually reserved for people who have degree in engineering. | |
| Apr 3, 2013 at 7:51 | vote | accept | T. Webster | ||
| Apr 2, 2013 at 13:48 | comment | added | TheCleaner | HR also complicates this...as a lot of NetAdmins end up with odd titles such as Network Engineer III, Sr. Network Analyst, etc. simply based on someone's tenure and need for a title "upgrade" to fall into a certain salary range for HR. | |
| Apr 2, 2013 at 12:52 | comment | added | Chris S Mod | +1 Most commonly I find that an "Engineer" is an implementer, commonly a consultant (but not necessarily), who's focus is on getting whatever technology up and running in the first place; where an "Administrator" has ongoing responsibility for the technology which primarily includes maintenance, minor upgrades, troubleshooting, etc. But I've seen those terms used in other contexts, so you can't rely completely on these. | |
| Apr 2, 2013 at 8:16 | history | answered | Dan | CC BY-SA 3.0 |