A front-end designer ... lives in a sort of purgatory between worlds:
- They understand UX principles and best practices, but may not spend their time conducting research, creating flows, and planning scenarios
- They have a keen eye for aesthetics, but may not spend their time pouring over font pairings, comparing color palettes, or creating illustrations and icons.
- They understand the importance of backend development, but may not spend their time writing backend logic, spinning up servers, load testing, etc.
Hello, my name is Geoff and I am a web designer. At least, that's what I tell people I do for a living, because it's what most people understand.
The truth is, I am a front end developer. If you read this blog with any sort of regularity, then I don't even need to bother explaining that job title.
Or do I?
The following is a guest post by Lara Schenck. I heard her tell this story at a CodePen Meetup in New York. I saw an awful lot of nodding heads. It's a fact that there is some trouble in this industry with job titles, descriptions, interviewing, and that whole rigmarole. Check out this story from Lara, then follow her, as I'm sure this isn't the end of this discussion.
There are loads of job titles in our industry. The opinion on their usefulness range from harmful (i.e. leads to “not my job” syndrome) to vital (i.e. people change companies sometimes and need common language). Since they are out there and we use them, there should be some consistency to their definition. Perhaps we can get closer to nailing that down.
Let's light this fire, shall we? This is all debatable, of course.