I recently figured that I would call myself a website developer, emphasizing the website part heavily. It is because all other terms are somewhat vague.
Take UX engineers as an example. Does a UX engineer need to know SEO basics?
Take web developer, full-stack, and front-end developer positions. You couldn’t possibly tell what these positions imply. These terms are just too broad, and they assume too many things.
For me, it doesn’t matter which technology is in the background. I know my way around WordPress, Hugo, Jekyll, Eleventy, Hexo, Shopify, HubSpot, and whatever, but that doesn’t matter. What matters is that the final code should be the same. It should have functional code that could be processed by users, browsers, screenreaders, crawlers, and who knows what else. As a website developer, all I care about is that my sites are performant, optimized, and easily consumed.
Although I am not looking for a new position, I like to browse available jobs and read the requirements. Some companies do a great job explaining the role in detail. On the other hand, some companies don’t even state which team is hiring. For example, a front-end developer part of a product team has an entirely different job than one part of the marketing team.
I hope this is just my point of view and that the reality is better. But unfortunately, I somehow feel like it is the other way around and that the reality is actually worse.
Top comments (1)
Thank you for the food for thought.
Having started a new job recently I think employers don't even know the distinction between all of these roles, or at least have serious misconceptions. My conclusion is that in this world, everyone is just wingin' it.