Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have to imagine that it is good advice for early in your career. When you’re applicant number x out of 1500 who all got good grades at a good school, have some good github projects, and do well at the leetcode, grating the interviewer by prematurely mentioning comp may not be your best move.


Fresh out of school, you're worth just about as much as someone you graduated with.

20 years into your careers, you may be worth 10x or 1/10 of that same person.

Why waste people's time? It's a waste of time interviewing for a place if you know they aren't offering anything close to what you'll be asking. And if you're making 2-3x the median salary for that job title, you should probably get a comp range up front.

I've been burned by this a lot. Don't talk comp, go through hours of interviews, taking afternoons off for in person interviews (in the before times), all to find out that their maximum for for the position is a 25% pay cut.


Right; I’m saying it’s value as advice tapers off as your career progresses




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: