Skip to main content

Here I Go Again

I found out recently that I am the victim of the recently announced layoffs at my current (as of the time of this writing) employer. More specifically, management was shuffled around and I went from being the protege of the person that hired me to last week's news since my new manager set goals for the group that do not match my background and experience. Last week I mentioned this with the promise of discussing how I am approaching my job search this time differently than last year, so here I am talking about this topic again.

Last year, the employment market was in much worse shape. In spite of this, I'm not allowing the relatively positive outlook to cause me to be lazy. Specifically, I am taking the following approach to my job search.

Do not wait. My wife calls me the King of Layoffs since I was also a victim of a massive reduction in force in 2008. (Yes, that's three layoffs in three years.) Fortunately, I found a new position rather quickly within BMC and averted any financial impact as a result. Last year, I had the attitude that it would be easy again and did not hustle like I should have. As a result, precious time was wasted when I could have and should have been using my connections within the company to attempt to land me a new position elsewhere.

This year, I immediately started canvasing the people with whom I have worked and had a positive impact to ask for their endorsements and recommendations. Introductions have been made internally and progress is occurring.

Make the call. It's embarrassing to say you're being laid off. It's even more embarrassing to say you're being laid off after having started only four months ago. It's the most embarrassing to say that you're being laid off for the third time in three years. Still, there is no shame in reaching out to people that you have connected with to tell them of your situation. I have done nothing wrong (in my opinion and in the eyes of those with whom I have worked directly) so while it is embarrassing, the prospect of being out of work again is more aggravating than enduring a little embarrassment.

Therefore, I have reached out to the movers and shakers that I know. I have spoken with a few C-level executives in my network and have had (and continue to have) meetings with them. Last year, when I was interviewing, I made it a point to break the relationship with hiring managers at other companies on good terms so I am hoping that the attempt to reestablish contact with them will yield positive results.

Sell yourself. I never know when I'll get introduced to someone with influence or the ability to hire me (internally or externally). Since I'm actively seeking out these meetings, it behooves me to ensure that I am prepared when they occur. I have rehearsed my own "value proposition" until I can pitch my worth in my sleep.

Remember: amateurs practice until they get it right, but professionals practice until they cannot get it wrong.

It is worth noting that none of those things would be possible if I had not done the following already:

Bust your ass. I apologize for using such a crude euphemism, but I have guaranteed that I have "positive equity" with my coworkers because of the degree of effort I have put forth in the short time I've been here. Part of this is due to the realization that my skills - as required by the person who hired me - are a bit specialized so I have a lot of catching up to do, but the bigger part is simply that I wanted people to see that I can hustle.

Keep in touch. I've stated before the importance of keeping your network refreshed, i.e. stay in contact with people that you have relationships with. I had coffee with the CIO of a Fortune 100 company last week after telling him of my current situation. I worked for him several years ago at a different company, and always remembered to email him once every couple of months. He may not have answered all of the time (frequently didn't, in fact) but he did not forget who I was. And since I busted my ass when I did work for him, he thinks highly enough of me to grant me 30 minutes of his time on a moment's notice.

All in all, I am cautiously optimistic that this year will be much different than last year. Still, I am not taking anything for granted so stay tuned to find out what fruits my labors yield in the coming weeks.

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