So. I'm not sure why? I try to refrain from diving into open discussions like this.
I think the short answer is to go on LinkedIn or Indeed, look up full stack developer, and see what is listed for requirements under Job Descriptions. It is sort of a catch-can topic for me because I can write a whole new post on "hiring" someone and Job Descriptions in the IT world. Hopefully sometime soon, I'll write a post on those subjects.
Below is my answer I posted. I thought I'd keep it here since I did write it. You can see the link below and what others have posted as an answer. What do you think, in a short description constitutes a full stack developer?
I think many people, even often employers, are missing the overall view. And yes. Some of the key points here brought up are valid. Full stack web developer IS in fact a lifestyle. And yes. Keeping up with the latest technologies IS a part of the job, BUT often loses sight of what a full stack developer really is.
1. The dawn of time. Full stack developer is another term or title. It really only became popular over the last 3–5 years give or take. For someone who in fact spent time learning Flash and Actionscript during it’s day, it is relatively new. I know. Buzz words are just that. They don’t necessarily mean squat. Full stack developer was a term thought up to describe someone who has a role and is capable of doing “the full stack.” Meaning Front-end work. Programming somewhat. Back-end work. And database. How these ALL work together and how to set up the entire stack. Mostly it had reference early to LAMP stack initially but lately it refers to any stack. Node MERN React even Python Go Ruby mostly anything with a database. How to set it up, how to maintain it, how it works. Thus stack.Anyone prior to the term might get frustrated simply because if you already worked the web there is a good chance you already were a full stack developer. Front back DB. Working a LAMP stack for example was not uncommon. But yes. There are just front end people. Or back end people. or just database people.
3. Do you need to learn new technologies? Yes. Can you know everything? No. It’s a never ending cycle. What IS important is that “on-the-job” you have enough experience to : Set up a Stack, install and maintain. Troubleshoot a stack, and make upgrades to that stack. Mainly many times a full stack developer has a deep understanding of all this and has the ability to troubleshoot and fix issues that occur during the life cycle. The best way to learn is through “doing” or being in situations that naturally occur or become problems on the job. Also, being able to just about handle any situation, whether it be troubleshoot a database, merge, migrate data. Troubleshoot code or write code. Write or design front end code. And make the stack work well. If you can handle a diverse set of issues without any advanced notice on a fly, you can definitely fall into the full stack developer title, which originally is what people where referring to. Having a full diverse knowledge of how the whole thing works. And it doesn’t stop there. Server management, client relations, working with other team members, deadlines, customer relations, things that don’t work.