|
|
|
|
|
by incognito_limey
2176 days ago
|
|
I think an additional piece to this, is to tell candidates what level they are interviewing for and the possible salary ranges, not total package, but actual base salary ranges. I just went through an interview process with AWS that wasted a lot of time for both sides due to them not being up front about the potential package. I had to push a fair bit to get any info, and finally had to politely tell them if the it's less the X I don't think it makes sense to move forward. Edit:
----- Additionally, they were unable to explain how after two interviews, what an additional 7 interviews in an onsite capacity would add/build on top of the first two. It felt like they were just putting me through a gauntlet without really understanding why. It saves both sides effort if you can make sure you are in general alignment before going too far into the process. |
|
After all, I know $X is what it will take for me to move enthusiastically and see it as good for my career trajectory, so if $X is over their salary range being coy about what I want just wastes my time.