I'm a Full-Stack developer at Google, which is fairly uncommon given the complexity of systems here.
The chief trait of a Full Stack developer, in my opinion, is often just growing into the needs of the team/moment. I've been weighted in different directions because that's where the product needed me; I'm currently the Front-End domain expert on my team.
Self-adulating thought leaders who throw shade at Full-Stack are themselves just really bad at using more than one language, let alone thinking about different parts of a large system.
(I'd also expect a Full-Stack developer to understand systems and resource provisioning/monitoring. Not just JS vs. Java.)
The chief trait of a Full Stack developer, in my opinion, is often just growing into the needs of the team/moment. I've been weighted in different directions because that's where the product needed me; I'm currently the Front-End domain expert on my team.
Self-adulating thought leaders who throw shade at Full-Stack are themselves just really bad at using more than one language, let alone thinking about different parts of a large system.
(I'd also expect a Full-Stack developer to understand systems and resource provisioning/monitoring. Not just JS vs. Java.)