Job titles can be confusing. If you’ve ever tried to hire a WordPress consultant to build you a website, or you’ve had inquiries about your services, you’ve likely encountered some level of confusion trying to decipher what an individual (or yourself) offers based on your title.
I’ve historically called myself a WordPress Developer. Other common WordPress or web centric titles I hear are Designer, Developer, Front-end Designer, Front-end Developer, UI Developer, UX Designer, IA Developer, Back-end Developer, Full Stack Developer, Consultant, Coach, Trainer, and so on. But what does it all mean?
I had a conversation at the WordPress Birmingham meetup with an attendee that said the “Designers” he works with do work in photoshop, and then do a large majority of the front-end code as well. I also know that there are some Back-end Developers that love to do front-end code, while others wouldn’t touch CSS with a ten foot pole.
Many people make their titles business-centric. I consider myself a Consultant with our clients at Infomedia. I think I bring more to the table than an ability to spit out WordPress websites. I help design workflows. I work with clients to define their needs. I help define scope. I sit in on marketing meetings. But I also love digging into PHP and solving programming problems.
So is it fair to define our skillsets narrowly? Aren’t I more than a “WordPress Developer”? I think so. The question is, what should I call myself that allows me to quickly establish my strengths without limiting my range of abilities too dramatically?
In the end, our clients just want solutions. They come to us because they have some notion that we can provide them that service. But it can still be important to define ourselves, even if it’s just to help us remind ourselves of our own definitions of ourselves periodically.
So what do you call yourself? Does it make any sense at all in comparison to the myriad responsibilities you carry?