Skip to main content

In Summary...

It was once told to me that when someone says "to summarize" (or something to that effect) you typically get 30 seconds of absolute focus. I honestly hope it's not because my presentation or discussion was so boring that they started mentally composing a list of items to get from the grocery store on the way home. But I digress...

Someone recently asked on LinkedIn how one can effectively negotiate a job offer, so I immediately responded that you need to communicate your value to the company as a basis for any negotiation. My answer started the gears in my head that perhaps a summary of some of the points that I've made so far in previous blog entries would be useful.

@You: don't think the following is a 30 second read, but "in summary" here are some things to consider when establishing a baseline of your value to a company.
  1. Stay relevant. I used the "@" sign not because I have a Twitter account (my wife says I will be the last person on Earth to sign up) but because it makes me look like I'm 23 and not that I have 23 years of experience. (Okay, 21 but what's 2 years among friends?) In all seriousness, you have to be on top of current trends in your areas of expertise so that you can have an intelligent conversation.

    Not too long ago, Delta sent me a notice that a minuscule number of miles were about to expire. What did I do? I applied them to subscriptions to Forbes, Fortune, Money, Fast Company, Inc, Entrepreneur and a few other related periodicals. I may not get to read them all every week but using the bathroom is now a much more educational experience. [Laughing]

  2. Businesses operate on the principle of value. In other words, no one cares what your job responsibilities were in previous positions. What were the results of your fulfillment of those responsibilities? That is what they want to know because ultimately the answer to that question can be translated into dollars and "sense."

  3. Your network is your best friend. When you've accumulated 15+ years of experience, unless you've had absolutely zero vertical movement in your career, 60-70% of the jobs that you'll get will be through connections you've made through the years. Many people that I once worked with are now C-level executives (or equivalent). You can bet your bottom dollar that I canvas my network in a huge way before I even consider visiting LinkedIn's Jobs section, Dice, HotJobs, etc. However, if you neglect it all of that "muscle" will turn to flab and you'll get little response from them; so be sure to reach out to the movers and shakers once in a while just to say "hi."

  4. No one can sell you better than someone else. The reason why you need to stay on top of your network is so that you can get your references in line. Choose quality references that not only can speak about your accomplishments and skills but can also rapidly establish their own credibility. For example, the references that I use are all C-level executives (or equivalent).

    Before you give out their contact information to anyone requesting it, send them a note and include the version of the resume that the potential employer is viewing; a brief description of the job you are seeking; and what you've told them so that they can corroborate (and even add to) what you said.

  5. "Amateurs practice until they get it right, while professionals practice until they cannot get it wrong." Use every opportunity to rehearse answers to anticipated questions during an interview. It should be like "muscle memory" when the question is asked, i.e. no hestitation. "Just do it!" to quote Nike.

  6. Do your homework. Before you meet with anyone about a potential job, ensure that you've googled the company, refreshed your memory on any job concepts that you may need to know, etc.

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...
Read more

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...
Read more

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...
Read more