> I thought we were supposed to never answer this question.
As a candidate that's the first question I get, and as an interviewer it also helps a lot.
I understand the risk to abuse the info to low ball a candidate, but setting an expectation level as early as possible helps to better target the interview process and be more efficient when it won't work out.
If someone is asking for a CTO level salary but but we're seeing they'd fit an entry level position, it needs to be discussed at the second round, not at the last round after both sides spent 6h of overall process.
Having the info earlier also helps better target the interview, in particular to justify the person fits in the role. If you're only doing 2~3 interview, they better be well targeted.
As a candidate that's the first question I get, and as an interviewer it also helps a lot.
I understand the risk to abuse the info to low ball a candidate, but setting an expectation level as early as possible helps to better target the interview process and be more efficient when it won't work out.
If someone is asking for a CTO level salary but but we're seeing they'd fit an entry level position, it needs to be discussed at the second round, not at the last round after both sides spent 6h of overall process.
Having the info earlier also helps better target the interview, in particular to justify the person fits in the role. If you're only doing 2~3 interview, they better be well targeted.