If you have a job, then you can only interview on lunch breaks or after work. If you have a shitty job then you have incredibly short lunch breaks and get off work late. You'll miss a lot of interview opportunities.
You also might not have time to do the various different screener exercises that many companies require of junior developers to make sure you actually know how to do something more complicated than fizzbuzz
If you've got two juniors of similar skill levels, and one of them needs this job significantly more, that may also weigh in your hiring decision
For myself, it is easy to forget this reality. Once your career is bootstrapped the story changes so much. I've changed employers only 4 times in 23 years, one of those was an acquisition, and the other three times I only interviewed with four companies (total, not each job change). Since getting my first job, I've never not gotten the phone screen/onsite interview/job offer.
Ok that all sounds very braggadocio. Sorry.
But when I consider my first job search: over a period of nine months I sent out over a hundred applications, received several hundred rejections (some companies like to reject you once for each internal department that doesn't like you), and finally scraped a handful of interviews, some mealy mouthed "maybe if" not-quite-offers, and finally a real job offer. I also had the unbelievable arrogance to walk out of an interview because they used a 4GL and I wanted a real programming job (I was polite about it, I waited until lunch and just said that I didn't feel that I would be a good fit)
I'm actually on the other end of this, have had to design a few of those screener questions myself.
They're a pain but they do help with screening out those who can talk the talk but end up being overly confident spaghetti machines.
I know I'm missing out on people who are good but don't have time to prove it to me, but the cost of a bad hire is much more costly than missing out on a good one, and there are so many people to sort through
If you have a job, then you can only interview on lunch breaks or after work. If you have a shitty job then you have incredibly short lunch breaks and get off work late. You'll miss a lot of interview opportunities.
You also might not have time to do the various different screener exercises that many companies require of junior developers to make sure you actually know how to do something more complicated than fizzbuzz
If you've got two juniors of similar skill levels, and one of them needs this job significantly more, that may also weigh in your hiring decision