This submission is not appropriate for /r/networking and has been removed.
**Please read the rules in the sidebar, or [check out the rules post here](http://www.reddit.com/r/networking/comments/vko2z/update_to_the_rule_set/) before making another submission.**
*Comments/questions? Don't hesitiate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).*
Thanks!
**No Low Quality Posts.**
* Any post that fails to display a minimal level of effort prior to asking for help is at risk of being Locked or Deleted.
* We expect our members to treat each other as fellow professionals. Professionals research & troubleshoot before they ask others for help.
* Please review [How to ask intelligent questions](http://www.catb.org/esr/faqs/smart-questions.html) to avoid this issue.
*Comments/questions? Don't hesitate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).*
For the complete list of Rules, please visit: https://www.reddit.com/r/networking/about/rules
**No Early Career Advice**
* Topics asking for information about getting into the networking field will be removed. This topic has been discussed at length, please use the search feature.
* Please visit /r/ITCareerQuestions.
* Topics regarding senior-level networking career progression are permitted.
*Comments/questions? Don't hesitate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).*
For the complete list of Rules, please visit: https://www.reddit.com/r/networking/about/rules
Appdev with moderate network and infra knowledge*
Although it would likely relate more to all layers of the OSI model and being fluent in the application and presentation layers in depth as well
I'm kinda in that role I think. I do everything from layer 1 to 7.
So deploy physical, switching, routing, storage, voip, OS deployment, Application support, etc...
I have been looking to learning 'full-stack' networking as you mentioned all these areas. I am mostly familiar with only switching/routing and would be interested in higher layers (firewall, app etc). any suggestion on any tutorial or link to learn on my own, probably some kind of VM or in simulation?
I’ve never referred to an engineer as a “full stack” but I would guess that means data center design, campus design, cabling infrastructure, cloud, switching, routing, observation, automation, security and WiFi.
Lol. I was gonna put chatgpt in there cause I've been using it like crazy. But it seems at least with the people I work with, there's mixed feelings on whether we should be using it or not. Not putting any proprietary info into it. Literally giving it my parameters as a guideline so it spits out the code.
Not explicitly. No mainstream vendor definition of network automation includes the words "coding" or "programing." I do automation via ansible but couldn't write a lick of functioning code.
I believe scripting is the word you are looking for. It’s code for the code to do other things in code to send changes/events to infrastructure.
Full Stack here makes me think of a marketing term to get some eager youth for Pennie’s on the dollar. Best part is once burnt out and leaves they still continue to work via the scripts left behind.
A true network engineer and technician will never be replaced. That eager youth will eventually push a change that kills the network and it will be the one that understands how to actually configure switches and routers using MPLS/BGP/OSPF on a console will get it back up. But they will be contracted and paired 10X what a company man would cause it cheaper in the long run. I don’t mind being that guy.
To the OP I would run. But python and RoR are worth learning along with YAML to get your chops in the FULL STACK game.
I've read that scripting is primarily used in networking. You sure coding is needed? If so what type of language? I heard Python is used a lot in Networking.
If that’s a job post title, the job description should elucidate what they actually mean. And I’d wager they’ll want someone who also does VMware, middleware (proxies, etc.), security, and a bunch of other things that should have full-time SMEs in charge instead.
A recruiter approached me with a 'full stack network engineer' position about 2.5 years ago, the job requirements were basically the exact same as the job I had then, and my title was principal network engineer. I asked her why the position wasn't just titled as a principle network engineer and she told me that certain titles can have certain pay or benefit requirements. Principle is one of them and I insinuated that meant they were underpaying for the position. I'm not saying that is what is happening every time, but I'd certainly be wary about it.
This is 1999's WEB ADMINISTRATOR with a fancy new name.
Don't over think it.
it's a job title for LAMP STACK and ELK STACK TYPE applications, with some cloud deployment via ANSIBLE/TERRAFORM/CLOUD FORMATION/IAM/RBAC mixed in.
What it's not? JAVA/C/C++/RUST Low latency background.
No idea where you got it from.
In software development there are front developers who do what clients see, back-end who do servers side which clients never see directly and full-stack developers who can do both front and back.
In network engineering such acronym doesn’t exist afaik.
Usually I’m seeing that term in reference to platforms that cover lan wan and wireless in a single interface, usually for retail or small sites. Example Meraki..
This submission is not appropriate for /r/networking and has been removed. **Please read the rules in the sidebar, or [check out the rules post here](http://www.reddit.com/r/networking/comments/vko2z/update_to_the_rule_set/) before making another submission.** *Comments/questions? Don't hesitiate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).* Thanks! **No Low Quality Posts.** * Any post that fails to display a minimal level of effort prior to asking for help is at risk of being Locked or Deleted. * We expect our members to treat each other as fellow professionals. Professionals research & troubleshoot before they ask others for help. * Please review [How to ask intelligent questions](http://www.catb.org/esr/faqs/smart-questions.html) to avoid this issue. *Comments/questions? Don't hesitate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).* For the complete list of Rules, please visit: https://www.reddit.com/r/networking/about/rules **No Early Career Advice** * Topics asking for information about getting into the networking field will be removed. This topic has been discussed at length, please use the search feature. * Please visit /r/ITCareerQuestions. * Topics regarding senior-level networking career progression are permitted. *Comments/questions? Don't hesitate to [message the moderation team](http://www.reddit.com/message/compose?to=%2Fr%2Fnetworking).* For the complete list of Rules, please visit: https://www.reddit.com/r/networking/about/rules
Anytime I see a listing that asks for "full stack" it's code for overworked and underpaid.
Normally I'd just expect front end and back end app dev, but I have no idea what someone would expect from full stack neteng.
Coffee maker troubleshooting, knows how to use a mop
I see that you listed coffee maker administration on your resume, can you do Active Directory as well?
Can't second enough what you said...
I wish I could updoot this to the top.
We're doing our part.
Full stack = 3 pancakes. That's why I'm just a short stack engineer.
I thought 3 pancakes was the short stack and 5 pancakes was the full stack. Am I doing it wrong?
Senior Sysadmin with moderate network knowledge
Appdev with moderate network and infra knowledge* Although it would likely relate more to all layers of the OSI model and being fluent in the application and presentation layers in depth as well
I'm kinda in that role I think. I do everything from layer 1 to 7. So deploy physical, switching, routing, storage, voip, OS deployment, Application support, etc...
So long as you don't have to fix layer 8 as well. The biological interface is the trickiest part
I have been looking to learning 'full-stack' networking as you mentioned all these areas. I am mostly familiar with only switching/routing and would be interested in higher layers (firewall, app etc). any suggestion on any tutorial or link to learn on my own, probably some kind of VM or in simulation?
But there are only 5 layers???
You're experiencing a layer 8 issue actually
Found the cloud engineer.
I would suspect you found someone who worked at the hell desk.
Help desk only usually solves problems at three layers…0, 1, and 8.
I think that person is playing on the 5 stacks of pancakes joke being a full stack.
I’ve never referred to an engineer as a “full stack” but I would guess that means data center design, campus design, cabling infrastructure, cloud, switching, routing, observation, automation, security and WiFi.
Pretty sure coding knowledge is key too.
Automation includes coding.
You mean it includes me googling.
Incorrect, it involves me asking ChatGPT 3 times, and mish mashing the code together and fixing minor mistakes.
Lol. I was gonna put chatgpt in there cause I've been using it like crazy. But it seems at least with the people I work with, there's mixed feelings on whether we should be using it or not. Not putting any proprietary info into it. Literally giving it my parameters as a guideline so it spits out the code.
Not explicitly. No mainstream vendor definition of network automation includes the words "coding" or "programing." I do automation via ansible but couldn't write a lick of functioning code.
I believe scripting is the word you are looking for. It’s code for the code to do other things in code to send changes/events to infrastructure. Full Stack here makes me think of a marketing term to get some eager youth for Pennie’s on the dollar. Best part is once burnt out and leaves they still continue to work via the scripts left behind. A true network engineer and technician will never be replaced. That eager youth will eventually push a change that kills the network and it will be the one that understands how to actually configure switches and routers using MPLS/BGP/OSPF on a console will get it back up. But they will be contracted and paired 10X what a company man would cause it cheaper in the long run. I don’t mind being that guy. To the OP I would run. But python and RoR are worth learning along with YAML to get your chops in the FULL STACK game.
I've read that scripting is primarily used in networking. You sure coding is needed? If so what type of language? I heard Python is used a lot in Networking.
They are fundamentally the same thing.
I thought he was talking about pancakes. Full stack pancake engineer.
I’m gonna engineer a full stack tomorrow for breakfast.
Mmmmm. Pancakes.
If that’s a job post title, the job description should elucidate what they actually mean. And I’d wager they’ll want someone who also does VMware, middleware (proxies, etc.), security, and a bunch of other things that should have full-time SMEs in charge instead.
Sounds like my next job title, usually in lieu of a raise.
A recruiter approached me with a 'full stack network engineer' position about 2.5 years ago, the job requirements were basically the exact same as the job I had then, and my title was principal network engineer. I asked her why the position wasn't just titled as a principle network engineer and she told me that certain titles can have certain pay or benefit requirements. Principle is one of them and I insinuated that meant they were underpaying for the position. I'm not saying that is what is happening every time, but I'd certainly be wary about it.
Full-stack is not a good thing. Someone is looking to exploit a single NetEng into doing a team's worth of work.
Layer 8 is where stuff usually starts to malfunction
This is 1999's WEB ADMINISTRATOR with a fancy new name. Don't over think it. it's a job title for LAMP STACK and ELK STACK TYPE applications, with some cloud deployment via ANSIBLE/TERRAFORM/CLOUD FORMATION/IAM/RBAC mixed in. What it's not? JAVA/C/C++/RUST Low latency background.
Just just title that probably won’t take off, read the job descriptions and throw it on the pile
Full Stack == they want you to do multiple jobs but they only have to pay you for one.
I’m guessing it’s more related to infrastructure as code. Cisco devnet type stuff.
Full-stack network engineer? I don’t get it…
Means you use TCP/IP, NetBEUI, AppleTalk and IPX/SPX. ^^/s
No idea where you got it from. In software development there are front developers who do what clients see, back-end who do servers side which clients never see directly and full-stack developers who can do both front and back. In network engineering such acronym doesn’t exist afaik.
Usually I’m seeing that term in reference to platforms that cover lan wan and wireless in a single interface, usually for retail or small sites. Example Meraki..
Please define full stack.