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

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 t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Overcoming Imposter Syndrome

Imposter Syndrome is a cruel partner in your professional journey.  If you're not familiar with the term, it is essentially the feeling that you do not belong in a particular profession or that you do not deserve a specific role or set of responsibilities.  (You may read more in the Wikipedia article .)  I did not hear the term myself until I participated in a mentoring group for young employees at my current job - some of the young employees said they had this, and I won't deny a bit of surprise when I read what it is. If you feel this way, you're obviously not alone.  A good friend of mine suffers from this in no small amount in spite of the fact that she's an upper mid-level manager at her company with an organization of approximately 40 people reporting to her.  She feels this way because she never completed college, but fails to realize that her hard work and dedication to being the best that she can be is why she has been repeatedly promoted through the ra...