So when you apply for a job, it’s important to make sure your title doesn’t get you ruled out on the initial screening of your resume. Sometimes it is as easy as making your title “Software Development Manager / Software Developer”, in my last example.

I always think about all of the “VP’s” I’ve talked to at big consulting firms and how its meaning can be diluted by gradual title shifts in certain industries. That’s an obvious downside to this approach though I do still think it is the best.

I refer to myself as The HR Princess because many years ago I got a call from a corporate VP who asked me about the Plant GM I worked for, “Does he think that’s his little kingdom?!?” and I said, “Yes, he does, and i’m the HR Princess.” It certainly was well remembered. Those were the days of Camelot…LOL

If someone told me they were a “Bar Chef”, I would give them a blank look and ask for a clarification. I do understand that it adds a little bit of intrigue and can instill more pride in the same way that “Administrative Assistant” is much better than “Secretary” or “Clerk”, but if what someone calls himself or herself doesn’t actually explain what they do, then what’s the point in having it at all?

In my organization, we have problems with job titles and job roles. Your role is the function that you’re actually filling while the title refers to “VP” or “Shareholder” and there is nothing tying the two together. It makes things difficult for us sometimes, especially because employees don’t understand that these are two separate tracks to climb.