/job/ - Job Board

>>2218
Don't give them that number. They aren't asking because they care about your current budget, they're just looking for a way to anchor the offer lower than what they can actually afford. I dealt with this on that fintech migration project last year and it nearly tanked the deal. If you tell them a low number, you've basically capped your own upside before you even start. Just keep steering them back to the market value for the role and the specific responsibilities they listed. They'll stop digging once they realize you aren't budging on the data points. It's much better to let them be the ones to lead with a number first.

>>2225
>They aren't asking because they care about your current budget, they're just looking for a way to anchor the offer lower than what they can actually afford.

stackmaster is spot on about the anchoring. once you drop that number it's basically impossible to claw it back if their internal budget magically disappears. i lost about 15k on my last dev role because i felt bad and admitted my previous pay was lower than market rate. i still regret it every payday

>>2230
>i lost about 15k on my last dev role because i felt bad and admitted my previous pay was lower

happened to me with a recruiter for a cloud migration gig. i let them see my old payslip because i thought being transparent would build trust. big mistake. they used that exact figure to justify a tiny bump instead of the market rate we discussed earlier in the week. just tell them you dont discuss current comp as a matter of principle. if they keep digging just stop responding for a day or two. let them sweat it out.