Skip to main content

Read between the lines

"Job titles don't mean shit," he said. (Okay, so maybe I took some "creative liberties" there. Sue me.)

I was a young kid with only a few years' of experience trying to claw my way up the corporate ladder by taking new jobs with more responsibilities. At that moment, I was arguing about wanting to pursue jobs that had specific titles with Ryan Abbott, a "wet behind the ears," junior recruiter at some no-name agency. (He is now, by the way, the Director of Recruiting at Tuttle and is one of only two recruiters that I trust completely).

Ryan's argument was that job titles vary from company to company but job responsibilities will always tell the true story. (A running joke from when I worked on Wall Street was that even the janitorial staff had the title AVP. Does this sound familiar in your company or industry?) During the interview process, the person asking the questions will be able to tell if you are a director level person in title only or in reality.

The beginning of a somewhat famous proverb goes like this: if you saw a man walking down the street in a finely made, Italian suit made of hand cut silk you'd immediately know that they bought it at a tailor.

The question that I pose to my audience this week is: do people know that are you a tailor? Can someone tell what you are capable of by looking at what you've done? And, more importantly, does it matter what titles you've held in the past?

Consider the following: never in my life have I held the title Technical Account Manager (TAM). But I have been a very successful one before by virtue of the fact that I was at one point in my career responsible for 57 accounts varying in size from very small to very large. In this company there did not exist a formally defined TAM role. Instead, the responsibilities of the role were delegated to my peers and me, and I did everything that you would expect from someone with these responsibilities.

So would I let the fact that I've never had the official title stop me from applying for these types of positions? Never. In fact, I am probably more familiar with this role due to the success that I enjoyed than I am with other positions that I had in an official capacity, so why shouldn't I pursue these types of positions?

The hat trick here is to sell yourself. Read between your own lines to determine the types of positions for which you are not only qualified but would excel in doing, and then include them in your stable of career possibilities for the road ahead.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ