Fordel StudiosThe job description says "full stack engineer." It means: you will own the React frontend, the Node backend, the PostgreSQL schema, the AWS infrastructure, the CI/CD pipeline, and the mobile app when we get to it. You will be the only person who understands any of these. You will be on call for all of them. The salary is the same as a specialist at a company that has not discovered the term "full stack."
This is not a versatile role. It is a cost-saving measure with a resume-friendly label attached.
When Full Stack Is Legitimate
There are contexts where genuine full stack ownership makes sense. Early-stage startups where the product is not defined enough to specialise. Teams where the stack is deliberately constrained — a single language across all layers, a monorepo, a deployment target simple enough for one person to own. Engineers who genuinely want broad ownership and make that choice knowingly, at a salary that reflects the scope.
The problem is not the role. The problem is the gap between what the title means in the legitimate case and what it is used to mean in practice. In the legitimate case, the engineer owns a narrow stack deeply. In the extraction case, the engineer owns a wide, complex, divergent stack shallowly, and is evaluated against specialists in each domain by employers who pay for one.
“Every hour a full stack engineer spends on infrastructure is an hour not spent on product. Every hour on product is an hour not spent on infrastructure. The breadth is a zero-sum game with your depth.”
The Career Damage Nobody Talks About
Engineers who spend three years in a full stack role often exit with shallow experience in multiple areas and deep experience in none. They can build a feature end to end, which is genuinely useful. They cannot make the kind of deep architectural decisions in any single domain that a specialist makes easily. At the next interview, "I did everything" is harder to evaluate than "I was the best React engineer on a team of twelve." Breadth is hard to prove. Depth is easy to demonstrate.
The engineers who thrive in full stack roles are the ones who use them deliberately — as a way to gain context across a system before specialising, or as a permanent preference for ownership over depth. The ones who stay full stack because they were never given the choice to specialise are the ones who emerge with a resume that covers everything and a portfolio that goes deep on nothing.
What Engineers Should Demand
If you are going to own a full stack, own a small one. A simple backend, a single frontend, infrastructure you could explain to a competent engineer in an hour. If the stack is large and complex, the scope should be commensurate with the team size, and the team size should be commensurate with the complexity. "We are a startup" is not an explanation for asking one engineer to do the work of four. It is a budget constraint being passed to you as a job description.
Negotiate on scope before accepting salary. The scope determines what you will learn, what you will ship, and what your resume says in three years. The salary is a starting point. The scope is the actual deal.
