Recently I spent some time interviewing and jumping between jobs, and compared to the amount of time I spent working at one company, I was spending a lot of time interviewing, preparing for interviews, and applying to companies.
Basically, my impression from being a high school programmer was walking in the door, being qualified, and being hired essentially in the same afternoon. After getting through college, it seems to be way more of a contest to win a job.
Similarly, I earned an internship at a high-profile company in New York City, which I didn't actually complete due to extenuating circumstances, but the impression I had from the interview and from a few days on the job was that the role was trivially easy and they were somehow scouting the absolutely most qualified and talented programmers in the country, anyway. This might happen to work out but something seems broken in this situation, too.
In this case, though, this team had only one position to fill and hadn't hired together before, so we needed to see a fair number of candidates in a batch so that we could collectively calibrate. That took more time than I wanted.
I definitely don't think we were too selective, though. Good developers can quickly improve both a team and a code base. Bad ones can harm both in ways that are expensive to fix. I think a lot of typical selection criteria are bunk (e.g., fancy schools, fancy companies on the resume), and I'm not always looking for amazing technical qualifications. But I definitely think it's worth time to find people who are great fits for the job.
You state that "a good programmer can learn a language quickly". I think most people who have experience with hiring developers disputes this. Learning a language is also one of the easier hurdles to overcome when moving into a new programming domain.
If you're hiring for a Ruby on Rails team, and you want to hire someone who has prior experience as a developer but has never touched Ruby in their life, you're probably not going to be too worried about how quickly it will take them to learn Ruby. The real challenge will be learning Rails, and then becoming proficient enough to work alongside the current development team and the pre-existing codebase.
Also, how do you approach hiring for mobile? That seems like a domain where language is important, since it's tied to the domain if you plan on native development (which you should). If you're hiring for an iOS position, are you not going to prioritize a candidate with prior iOS experience over one who has only done Android?
It's difficult for me to imagine a scenario where you would have to resort to a former Android dev unless you aren't willing to pay a fair hourly rate or salary, and you're going to bargain for the opportunity to learn in exchange for lower pay.
As to the mobile question, it would depend on the team composition. If I'm hiring the first mobile developer, then yeah, I'm going to look for somebody with a lot of experience. Probably the second as well. But for the third and after, I wouldn't put it as a requirement. As long as there are people around who can mentor, then I'd rather hire a strong developer with little mobile experience than a not-so-great developer with plenty of mobile experience.
https://www.codeforamerica.org/about/fellowship/
That's a great opportunity for people with a few years experience to stretch themselves, being part of a small team that has a year to research, evolve, and deliver a whole system.