• 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)