When it comes to salaries, I'm not average

  • Comments posted to this topic are about the item When it comes to salaries, I'm not average

  • The bad part about this advice is that I've heard it from a whole lot of people and they're correct... they definitely not "average" .  They're actually quite a bit below average, which is pitiful to begin with according to the interviews I've conducted or have witnessed over the last decade.

    The first step in negotiating a salary is all that happens during the interview.  If you have to tell someone that you're not average, it's because you actually are "average" or worse and did nothing to prove otherwise during the interview.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Very good topic, Andy. I've often wondered how much I could make, given my education, training, skills and years of experience. I remember learning of Payscale and Saral.com years ago. I got onto Payscale to try and learn what I could make, in other locations. At the time I was looking at some senior developer jobs in NYC. I found that given my education, training, skills and experience that they pay range that Payscale gave me was, well let's say exuberant. We got to the point of talking about salary and I told them the range the Payscale gave me. I never heard back from them. Either they thought my requested pay range was way out of line, or they realized that they couldn't get this hobo from NM as cheap as they wanted to.

    Since then I've considered the estimated pay ranges reported by Payscale, and Salary.com, to be off by a lot. I'd love to know if others experiences using Payscale.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • First, the market for skilled labor, especially technical professions, is perhaps the best example of what is called by economists an "in-efficient market". It's the exact opposite of the stock market or retail stores setting prices for the same brand X widget. 
    http://www.businessdictionary.com/definition/efficient-market.html

    Even if you are an exceptional DBA, you may find it impossible to sell yourself as such to many prospective (or current) employers because they're simply not interested in an exceptional DBA. What they really need (or think they need) is someone to maintain the status quo or at least improve things to the point where users (at least the users they care about) are not complaining. It's like a restaurant trying to sell upscale $10 burgers to a customer base where the median household income is $32,000, and you're struggling to compete with the local McDonald's dollar menu. It's not that your burger isn't worth $10, it's just that you're in the wrong market.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • I really like the assertiveness of "I am not average". Simple and powerful. This is good advice for those mid / upper career level. 

    It is hard to sell for those with little experience but I think even they can benefit from this advice. After all a certain % of your team is going to be rockstars and the rest just keep the lights on. A young ambitious person may capitalize on this if they got the right stuff.

  • Eric M Russell - Thursday, June 21, 2018 10:01 AM

    First, the market for skilled labor, especially technical professions, is perhaps the best example of what is called by economists an "in-efficient market". It's the exact opposite of the stock market or retail stores setting prices for the same brand X widget. 
    http://www.businessdictionary.com/definition/efficient-market.html

    Even if you are an exceptional DBA, you may find it impossible to sell yourself as such to many prospective (or current) employers because they're simply not interested in an exceptional DBA. What they really need (or think they need) is someone to maintain the status quo or at least improve things to the point where users (at least the users they care about) are not complaining. It's like a restaurant trying to sell upscale $10 burgers to a customer base where the median household income is $32,000, and you're struggling to compete with the local McDonald's dollar menu. It's not that your burger isn't worth $10, it's just that you're in the wrong market.

    I hadn't thought of that, Eric. Very good points! And since I wasn't in NYC, it was impossible for me to have learned through local groups or contacts why negotiations suddenly ended. They may have lost someone who did average or even below average work, but were good enough to keep the lights on, so to speak. So I may have priced myself out of that job opportunity because of that. Thanks for the input.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • I have always thought of "average" as being the best of the worst and the worst of the best.  Having said that, I'd agree with the prior comments, each reflecting the various issues folks have encountered.

    Thinking about this process recently I have concluded that the current approach, as generally understood, is going to need to change at some point in the near future.  One of the reasons come from a great book I am reading, "The End of Tech Companies" by Rob Thomas.

    Note: A couple edits for clarity

  • Rod at work - Thursday, June 21, 2018 10:32 AM

    Eric M Russell - Thursday, June 21, 2018 10:01 AM

    First, the market for skilled labor, especially technical professions, is perhaps the best example of what is called by economists an "in-efficient market". It's the exact opposite of the stock market or retail stores setting prices for the same brand X widget. 
    http://www.businessdictionary.com/definition/efficient-market.html

    Even if you are an exceptional DBA, you may find it impossible to sell yourself as such to many prospective (or current) employers because they're simply not interested in an exceptional DBA. What they really need (or think they need) is someone to maintain the status quo or at least improve things to the point where users (at least the users they care about) are not complaining. It's like a restaurant trying to sell upscale $10 burgers to a customer base where the median household income is $32,000, and you're struggling to compete with the local McDonald's dollar menu. It's not that your burger isn't worth $10, it's just that you're in the wrong market.

    I hadn't thought of that, Eric. Very good points! And since I wasn't in NYC, it was impossible for me to have learned through local groups or contacts why negotiations suddenly ended. They may have lost someone who did average or even below average work, but were good enough to keep the lights on, so to speak. So I may have priced myself out of that job opportunity because of that. Thanks for the input.

    Just like the DBA market, there certainly is a bell curve for IT recruiters and hiring managers too. In the past, I've had some inexplicable experiences while job hunting as well, and sometimes it can seem if the job seeker has stepped into an episode of the Twilight Zone or become the subject to a "gaslighting" campaign.
    https://en.wikipedia.org/wiki/Gaslighting
    However, I always tried to maintain perspective, never allowing myself to extrapolate from one experience, because we really don't know what the hell is going on behind the scenes at the other end. Fortunately, I've never been out of the market for more than a few weeks. I think it has a lot to do with shrugging off the disappointments, staying positive, and knowing how to spot and work a good lead.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Eric M Russell - Thursday, June 21, 2018 11:44 AM

    Rod at work - Thursday, June 21, 2018 10:32 AM

    Eric M Russell - Thursday, June 21, 2018 10:01 AM

    First, the market for skilled labor, especially technical professions, is perhaps the best example of what is called by economists an "in-efficient market". It's the exact opposite of the stock market or retail stores setting prices for the same brand X widget. 
    http://www.businessdictionary.com/definition/efficient-market.html

    Even if you are an exceptional DBA, you may find it impossible to sell yourself as such to many prospective (or current) employers because they're simply not interested in an exceptional DBA. What they really need (or think they need) is someone to maintain the status quo or at least improve things to the point where users (at least the users they care about) are not complaining. It's like a restaurant trying to sell upscale $10 burgers to a customer base where the median household income is $32,000, and you're struggling to compete with the local McDonald's dollar menu. It's not that your burger isn't worth $10, it's just that you're in the wrong market.

    I hadn't thought of that, Eric. Very good points! And since I wasn't in NYC, it was impossible for me to have learned through local groups or contacts why negotiations suddenly ended. They may have lost someone who did average or even below average work, but were good enough to keep the lights on, so to speak. So I may have priced myself out of that job opportunity because of that. Thanks for the input.

    Just like the DBA market, there certainly is a bell curve for IT recruiters and hiring managers too. In the past, I've had some inexplicable experiences while job hunting as well, and sometimes it can seem if the job seeker has stepped into an episode of the Twilight Zone or become the subject to a "gaslighting" campaign.
    https://en.wikipedia.org/wiki/Gaslighting
    However, I always tried to maintain perspective, never allowing myself to extrapolate from one experience, because we really don't know what the hell is going on behind the scenes at the other end. Fortunately, I've never been out of the market for more than a few weeks. I think it has a lot to do with shrugging off the disappointments, staying positive, and knowing how to spot and work a good lead.

    Thank you again, Eric. My problem is I tend to think that if a job prospect goes south, its something I've done wrong. That's one reason why I find SQL Server Central and especially these forums to be useful. I can gain some perspective and realize there might be other reasons.

    Kindest Regards, Rod Connect with me on LinkedIn.

  • Jeff, you're right that a lot of us are average. That's not bad, it's the nature of things. My premise is just a little different and that's whether you let them frame the salary negotiation based on average salary (not skill). The average they are using may or may not be a good number, and that number may or may not be one that you can live with. There's no perfect way to evaluate either your skill level or what you're worth, but it's helpful to try to assess both before the interview and if they disagree, at least explore why (even if its on your own after the interview). The technique I propose isn't one size fits all, just designed to get you thinking about that conversation. Are you negotiating or just taking what is offered?

    Some companies don't want superstars...or more honestly, they usually don't want to pay for superstars. Or they don't know what they cost! 

    Rod, feeling that way is normal. Sometimes we miss the question, miss the cue to respond a certain way, seem to care about the wrong things (salary, benefits). Not all first dates lead to second dates! Is it you or is it them is hard to figure out.

  • Eric, totally agree on the market value. It's a heck of a game to figure out what you can make, harder than trying to figure out if you really negotiated a good deal on the new car.

  • Andy Warren - Thursday, June 21, 2018 3:10 PM

    Jeff, you're right that a lot of us are average. That's not bad, it's the nature of things. My premise is just a little different and that's whether you let them frame the salary negotiation based on average salary (not skill). The average they are using may or may not be a good number, and that number may or may not be one that you can live with. There's no perfect way to evaluate either your skill level or what you're worth, but it's helpful to try to assess both before the interview and if they disagree, at least explore why (even if its on your own after the interview). The technique I propose isn't one size fits all, just designed to get you thinking about that conversation. Are you negotiating or just taking what is offered?

    Some companies don't want superstars...or more honestly, they usually don't want to pay for superstars. Or they don't know what they cost! 

    Rod, feeling that way is normal. Sometimes we miss the question, miss the cue to respond a certain way, seem to care about the wrong things (salary, benefits). Not all first dates lead to second dates! Is it you or is it them is hard to figure out.

    I believe you missed my point, Warren. 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Andy Warren - Thursday, June 21, 2018 3:10 PM

    Jeff, you're right that a lot of us are average. That's not bad, it's the nature of things. My premise is just a little different and that's whether you let them frame the salary negotiation based on average salary (not skill). The average they are using may or may not be a good number, and that number may or may not be one that you can live with. There's no perfect way to evaluate either your skill level or what you're worth, but it's helpful to try to assess both before the interview and if they disagree, at least explore why (even if its on your own after the interview). The technique I propose isn't one size fits all, just designed to get you thinking about that conversation. Are you negotiating or just taking what is offered?

    Some companies don't want superstars...or more honestly, they usually don't want to pay for superstars. Or they don't know what they cost! 

    Rod, feeling that way is normal. Sometimes we miss the question, miss the cue to respond a certain way, seem to care about the wrong things (salary, benefits). Not all first dates lead to second dates! Is it you or is it them is hard to figure out.

    Funny, in an earlier post I was about to draw an analogy between job interviewing and dating.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Andy Warren - Thursday, June 21, 2018 3:10 PM

    Jeff, you're right that a lot of us are average. That's not bad, it's the nature of things. My premise is just a little different and that's whether you let them frame the salary negotiation based on average salary (not skill). The average they are using may or may not be a good number, and that number may or may not be one that you can live with. There's no perfect way to evaluate either your skill level or what you're worth, but it's helpful to try to assess both before the interview and if they disagree, at least explore why (even if its on your own after the interview). The technique I propose isn't one size fits all, just designed to get you thinking about that conversation. Are you negotiating or just taking what is offered?

    Some companies don't want superstars...or more honestly, they usually don't want to pay for superstars. Or they don't know what they cost! 

    Rod, feeling that way is normal. Sometimes we miss the question, miss the cue to respond a certain way, seem to care about the wrong things (salary, benefits). Not all first dates lead to second dates! Is it you or is it them is hard to figure out.

    Andy,

    I am going to very respectfully disagree that, "a lot of us are average."  Here's why, and I'd be delighted, should you think I am missing something if you'd let me know.  I think when many folks assert they are average that this is a way to avoid conflict.  I remember when in grade school that any kid that stood out was picked on.  "Poindexter", "four-eyes", "retard" and so forth.  The point being is we manage or control by having the power to exclude.  When we realize this isn't true, we start to discover what WE want to do or say or study to achieve.  And, some of us (thinking of my journey are dumb at times 😉 ) struggle more with this than others.  

    We "hide" in order to avoid exclusion.  We find that "being average" is a great place to express this.  

    I am a firm believer that everyone, in the sense of intrinsic value, is unique and that value exists regardless of anything else.  Call it Human Dignity, realized or not, but it's there.  There isn't a single one of us that does not at some point fall into some sort of statistical Bell Curve average of one sort or another.  But, I seriously doubt that anyone who manages to find this sort of hangout need to be too concerned about their data-related skills, even if nascent.  Not one.  

    I think we need to be reminded that, yes, I do not know "X", "Y" or "Z", to which I always add a mental addendum of, "yet."  Everything we know we have learned therefore if I do not know something I need to go and learn it.  Do I want to?  Am I interested and all of that as well.

    I think a lot of the schoolyard bullies that used putdowns for the purpose of control call themselves recruiters, managers, peers and maybe even pose as friends.  That's fine, while they may be in the process of abandoning their character I'll choose not to do so.  And, yes, many of my skills fall into the statistical average group, as well as below average for many skills and maybe a few above the curve.  Also, I am not inferring anyone here falls into any category.  I just take exception to the notion that some might allow someone else to use this vis a vis their career.  

    I'd be surprised if some didn't see this as a rant based on personal struggles I have had.  It is actually.  So?  You going to be a retard about it? LOL 😀

    I do not contribute much but this is one of the most civil and professional groups I have run across. I say that with 30+ years of being online. Not once have I not learned something here.

  • Assuming a normal distribution, most of us would of course fall within the range of what's typically considered "average".

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 15 posts - 1 through 15 (of 64 total)

You must be logged in to reply to this topic. Login to reply