[etjossem]

It bears mentioning that the "Designer" and/or "Front End Developer" in a small startup team will usually end up wearing several of these hats.

Larger teams can afford the level of specialization described here, but a smaller company (or a small internal team) may have a technical front-end developer who produces prototypes and live code, plus a non-technical designer who does everything else on the design side. If it's a really tiny team, there might be a single person who rapidly produces mockups and scripts for usability tests, then turns around a few days later and starts writing HTML/CSS/JS based on their findings.

I wish there were a better word than "unicorn" for people with a wider band of responsibilities. "Full-stack UX" sounds a bit silly too.

[sanderjd]

Also, in that same startup, the same person writing the HTML, CSS, and JS is very likely also writing the server communication and building the production infrastructure, making the entire "front-end" distinction rather moot. Honestly, even in larger companies, the front-end/back-end specialization makes little sense to me. If you can write a good front-end javascript application, it's very likely you can write a good back-end in pretty much any stack.

[wclittle]

I totally agree. Most startups have one or two people wearing all 5+ hats (which is OK, of course). I've found it especially helpful to think about these different roles when building out the team (and, in earlier stages, considering if there is sufficient coverage amongst the founders).