Is the Full‑Stack Engineer a Myth? Why Hiring One Is Unrealistic

"Full stack developer" frequently appears in job postings, but Hello Pretty co‑founder and CTO Scott Hadfield recently wrote that the full‑stack engineer is a myth; even if not entirely, employers struggle to find such a person.

To illustrate his point, he presented a non‑exhaustive "stack" diagram:

Employers expect far more than a typical developer can deliver. A full‑stack engineer must understand each component deeply enough to make informed choices and explain them to management. The skill matrix expands yearly, adding new layers, making the search for a true full‑stack engineer unreasonable and, according to Scott, foolish.

Scott does acknowledge that some individuals possess full‑stack capabilities, and many impressive developers, designers, and project managers exist. However, many self‑described full‑stack engineers can list only about half of the components, let alone their interactions.

"I see almost all uses of the term full stack (especially in recruitment posters) actually mean employers are looking for 'amazing people'."

He further notes that a full‑stack engineer might not need to write code at all, acting more as a system architect or integration engineer, and that the term should specify which stack—web, mobile, etc.

In summary, Scott states: "The full‑stack engineer is a myth, not because such people don’t exist, but because the term is meaningless."

On Hacker News, the discussion highlighted differing views. User andrewstuart defined a full‑stack engineer as someone who can build and deploy a complete, working application alone, handling front‑end, back‑end, server configuration, and database design.

Other participants argued that operations should be a core part of development; without proper ops, deployments can fail and cause rework.

BadassFractal shared his experience: he does full‑stack work, covering Ops (AWS configuration and deployment), DB (PostgreSQL), back‑end (building a Rails‑like framework), and front‑end (DOM, Backbone, React). He admits he isn’t a core expert in any single area, and any specialist would surpass him in that domain.

Further comments suggested that while a person can be a full‑stack developer, they cannot be a full‑stack expert. Companies should accommodate both types, and focusing recruitment solely on expert‑level front‑end and back‑end developers wastes the broader capabilities of multidisciplinary team members.

Author: infoQ/谢丽 Original article: http://www.infoq.com/cn/news/2015/09/Stack-Ops