We can use the term "full-stack developer" without having a definition, checklist, or example. In fact, I think it is pointless to do otherwise. We use the term

We can use the term "full-stack developer" without having a definition, checklist, or example. In fact, I think it is pointless to do otherwise. We use the term as a shortcut in a highly context dependent manner, and will followup with details and specifics afterwards as context demands. I don't think there is such a thing as a "full-stack developer"; instead I think there are developers who use the term "full-stack" to refer to their skillset and/or interests. Recruiters aren't trying to hire "full-stack developers"; instead they use the term to cast a reasonably appropriate net, and then verify key skills and aptitudes at the appropriate time. Also, "experience" and "full-stack" should be considered orthogonal modifiers. An inexperienced baker may not know how to bake some items; but that doesn't make them not a baker.