Recruiter here with a history of working as a developer
> but companies need to start specifying their salary
> range up front
The costs outweigh the benefits for employers (encouraging existing employees to ask for more money, losing candidates who will accept significantly less but wouldn't apply at a lower range, etc) -- so don't hold your breath.
> I've been having a lot of time wasted lately by
> getting through Tech Interview #1 or Homework #1, only
> to find out their max salary is laughable for San
> Francisco.
State it upfront when you submit your application, rather than "find that out":
"I am interested in roles paying above my current salary of $xxx,xxx only, and am looking for an improvement on that to reflect my increased experience and the risk of moving roles"
> Recruiters either don't know the range
Yeah they do.
> or lie about not knowing
"Could you tell me about offers you've previously made for this client?" They may also be lying about actually being authorized to recruit for the role(!!!) so consider asking them for a copy of the technical specification. If it's a larger company, ask what the salary banding and official job title for the range is, then head to Glassdoor.
> you have to submit a big packet of info (cover letter,
> history, resume, homework) before you can even talk to
> a human about salary
I had a hunch that roles like this weren't worth applying for when I was a developer. As a recruiter, this has been almost completely confirmed.