Actually looking up comp data before negotiating changed everything. Stop guessing your worth.
For years I just accepted whatever number the offer had because I had no idea what was normal. This last cycle I spent an evening on levels.fyi and Glassdoor for my role, location, and level, and walked in with an actual range in my head.
When the recruiter asked expectations, I gave a number backed by data instead of a nervous guess, and they didn't blink — it was right in their band. Ended up about 12% higher than what I'd have blurted out a year ago. The data doesn't guarantee anything, but negotiating without it is playing poker without looking at your cards. Do the homework.
10 comments
- 0
AnonymousAnon One I took far too long to learn: check the data for the company's level, not just the job title. "Software Engineer" covers about two bands in most places, and asking a recruiter which level the role maps to is a completely normal question they'll usually just answer. I anchored against the wrong band once and left real money sitting there.
- 0
AnonymousAnon One caution on comp data: check which level the numbers are for before you quote them. I walked into a conversation with a figure that turned out to be for people with four more years than me, and it made me look like I hadn't done the research. Which is the exact opposite of the point.
- 0
AnonymousAnon This. Walking in with a real number from levels, Glassdoor, and a couple of peers changes the whole conversation from 'please' to 'here's the market.' The worst they say is no, and they almost never rescind an offer over a polite, data-backed ask.
- 0
AnonymousAnon This is the highest-ROI hour in the whole process and people skip it. Levels data plus one specific number turns a scary conversation into a factual one. Did you lean on public sources or actual numbers from people you know?
- 0
AnonymousAnon One tactical add: when you cite comp data, give a range and a source, not a single number — "levels plus a couple of recent offers I've seen put this band at X to Y." It reads as informed rather than demanding, and it's much harder to wave off. Knowing your worth only helps if you can say it out loud without flinching.
- 0
AnonymousAnon Adding to this: asking a recruiter point-blank 'what's the band for this level?' got me way better data than guessing ever did. The awkwardness of asking is worth thousands of dollars, and they fully expect the question.
- 0
AnonymousAnon Walking in with a real number and a source completely flips the dynamic — you go from 'asking a favor' to 'stating a market rate,' and it's much harder to wave off. levels.fyi plus a couple of Blind data points did more for me than any negotiation script. Which sources did you find most reliable for your range?
- 0
AnonymousAnon One more source people sleep on: just ask peers directly. I traded actual numbers with two friends at similar companies over coffee and it was more accurate than any site, because it was my exact market. Awkward for about ten seconds, then incredibly useful. Pay transparency only helps us — the taboo mostly benefits employers.
- 0
AnonymousAnon The other half people forget: knowing the range only helps if you can sit in the silence after you say your number. I did all the homework then immediately caved the second the recruiter went "hmm." Say the number, then stop talking. That pause is the whole game — whoever speaks first usually loses a few thousand.
- 0
AnonymousAnon Cannot upvote this enough. I'd add: don't just look at the number, look at the spread for your level so you know where "a bit high but reasonable" actually sits. And levels.fyi skews big-tech, so if you're at a smaller company, cross-check Glassdoor and anyone in your network — otherwise you're anchoring to Meta comp for a 20-person startup and setting yourself up for disappointment.