Make Job Titles Simple Again

Mathijs Lemmers
8px Magazine
Published in
4 min readJul 29, 2019
Was having a hard time finding a cover image for this. So here is a designer limiting themself by picking an overly complicated job title. Photo by ROOM on Unsplash

Okay, so this is not going to be me telling you what you should call yourself. I know, that was what you were hoping for, right?

The thing is, lately I’ve been seeing a lot of discussion — primarily in the design community — about job titles. A hundred people doing the exact same thing could each have a very different title. Just from the top of my head: Web Designer, Front End Developer, UI Designer, UX Designer, UI/UX Designer, Interaction Designer, Web Developer, Web Programmer, Full Stack Developer. And lately these two have been very popular: Product Designer and Designer.

Designer, well that’s it isn’t it? We’re all designers.. why overcomplicate things with five-word-long job titles? We went from one side of the spectrum all the way to the other. And personally I think it’s time to step back and remember what job titles are for.

What are job titles for, Mathijs? 😁

I’m so glad you asked.

I’d say job titles — in our business in particular — serve two goals. And that might just be the problem. It’s both a way to let clients and colleagues know what you do.

I recently send out a poll to my very limited Twitter following (go follow me, please) and found that the majority thinks ‘Product designer’ is a confusing title. And I have to say I agree. I’ve searched for some time and still don’t know the exact meaning of the title. When I read a job title I just simply want to know what. that. person. does.

So, back to the problem at hand. A job title needs to be simple and clear so that potential clients know exactly what you do. But introducing yourself as a Webdesigner to other Webdesigners always leads to more questions. Do you only design websites or also build them? If you build them, do you only contribute to the Front End or also do the Back End? You can see how all these Job Titles have come into existence. Within certain communities you just need to specify what you do in more detail than elsewhere.

I’ve always considered myself to be a Web Designer. I design and build websites. It just seemed pretty straightforward to me. But there might just be another reason why we use all these different titles.

Inside the mind of a Web Designer

Yes, I design websites. But not like those other people design websites. No, no. You can come to me with a problem and I will find the perfect solution for your business. I’m not like those other people, calling themselves Web Designers, buying a Wordpress template on Themeforest and slapping your logo on top of it.

The need to distance yourself from so-called ‘quacks’ in the industry is understandable. I’m a firm believer in knowing your self-worth. Knowing where you stand in life doesn’t have to mean you have this huge ego or you feel you’re above other people. If you feel like your work is above average, accept that. This opens new doors like being able to help people who are just starting out more, writing guides or doing podcasts.

But does this change the fact that you’re a Web Designer? I believe it doesn’t.

Dude, is this going somewhere? 😕

I think so. It has to, right?

Let me clear my thoughts. For clients, let’s pick a title that actually describes what you do. A client doesn’t care what languages or frameworks you use. That person just wants to know whether you can build that what helps their business. And don’t make your title more complicated just because you feel the need to distance yourself from people that in your opinion stain the name.

Within Design Communities you’re just not going to get away with calling yourself a Web Designer. So you might just need to make it more precise. Let’s not confuse that with making it more… well… confusing. You might think ‘Product Designer’ sums you up perfectly. But it will get really tiring having to explain what you do every-single-time.

In conclusion

There really isn’t one. No conclusion. No single job title that will make everyone happy. So why did I write this article? I don’t know. To clear my mind? Start a good and healthy discussion, maybe? At least I think it is worth reminding ourselves what job titles are for.

You made it all this way? Let me know what you think!
I’m also not used to writing articles — in either Dutch, my main language, or English — so feedback is very much appreciated. I do like my feedback the 🍔 way. Oh gosh, that might just be my next article.

--

--