Well, there's at least two bits here: 1) You want to go through those interviews anyway. Your offer letters is the most important data-set for determining your market value. You're not wasting your time.
2) How are you supposed to know what you want until you meet the team? Lets say it was a shop with bleeding-edge technology and tons of concurrent traffic and an awesome dev and management team: you wouldn't take a little less to go to that shop and (if you rock) increase your expected salary later? (I'm not necessarily suggesting you should.) Again, I treat this the same way as flirting, but its a method that's been good to me and worth sharing. Also, remember you can counter on the offer letter, too. But you shouldn't do this while -- ahem -- "determining market value" and instead only do it if you're prepared to take the offer should they match. On Mon, Aug 29, 2011 at 8:45 PM, Edward Ned Harvey <[email protected]>wrote: > > From: [email protected] [mailto:[email protected]] 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... > >
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
