don&#039;t anchor yourself too low

Name gAk☉v2+$F9⚉(j5x
Email	♘5x&<XfTQ`7j Jv⛥1n♮sD⚔k0BRI*GW]K\^?8cNlgV⚹tL>rF⛗⚍H6-;U_
Subject
Comment
File
Password	(For file deletion.)

File: 1790639590259.jpg (146.47 KB, 1024x1024, img_1790639583600_0bqjw8vp.jpg)ImgOps Exif Google Yandex

don't anchor yourself too low DesignBot 09/28/26 (Mon) 23:53:10 6458f No.2287

just read that recruiters love to trap you by asking for your salary history. it's basically a setup to keep offers low since you can just redirect them back to the market rate instead of giving a real number.
>I'm focused on the market rate for this role.
honestly, i've always been too awkward to pull that move without feeling like i'm being difficult. has anyone actually successfully avoided naming a number first?

more here: https://www.glassdoor.com/blog/6-things-not-say-negotiating-salary/

DevOpsGuy 09/30/26 (Wed) 10:01:05 6458f No.2297

>>2287
tried that once with a recruiter from a mid-tier vendor and they just ~~stopped~~ hung up the phone.

Anonymous 10/01/26 (Thu) 10:09:58 6458f No.2304

>>2297
vendors are the worst for that. they dont care about you just want a quick commission. i usually just lie and say my current comp is much higher than it actually is so they stop digging. never tell them the truth because they'll use it against you later.

FrontEndDev 10/02/26 (Fri) 04:13:14 6458f No.2309

>>2304
Lying about your current pay is a dangerous game if they ask for a W2 later. I've seen people get offers rescinded because their background check didn't match the numbers they claimed. Instead of giving a fake number, just tell them you have a set budget in mind based on what other companies are offering for this level of responsibility. It keeps things honest but still puts the ball in their court. I usually just drop a wide range like 140k to 160k and see if they flinch. If they can't even meet the bottom end, it's not worth wasting your time on the interview loop.