On Mon, Aug 29, 2011 at 11:45 PM, Edward Ned Harvey <lop...@nedharvey.com> wrote: >> From: ca...@petalphile.com [mailto:ca...@petalphile.com] On Behalf Of >> carlo >> >> I think the 20% rule is a good one, but ultimately I think its best to defer >> conversations about expected salary (especially if you're still in the >> HR/pre- >> screening bit of an interview, and not the technical bits yet) > > I find an approximate salary range up front is worth while for both sides to > know. Because it's a waste of time to go through all the interview process, > only to discover it was never possible... >
There is also the concept of setting expectations. Conventional wisdom says you should not disclose your "number" until they tell you theirs. More recent research has shown that the person who divulges their "number" first gets the upper hand in the negotiation as the initial number subconsciously sets everyone's internal barometer, even if the initial number would reasonably be considered too high. If you go way too high though, it's taken as an insult and you might not get anything. Also, please remember that as an IT person you are performing a highly skilled job, and often find it enjoyable. This leads many in IT to take lower salaries than what they are actually worth because they think it's somehow dishonest to charge a lot of money for something they like doing. You might be OK with this, but it seriously hurts everyone else in the industry and contributes to the perception that IT provides low value to a business -- mostly because you are allowing the Business guys to get away with it. -☙ Brian Mathis ❧- _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
