>Last twice I've looked for a developer job, I got offered a position and was hired within 2 weeks.
His resume is the problem. Two immediate things: (1) His most recent job lists junior level work and (2) He is claiming 3 concurrent jobs over the last two years.
This shouldn't matter, chiefly because he has other work listed, so stopping at the first job post and forming an opinion makes the reader the problem. But also because people can sometimes take an easier job if they have life issues.
Secondly, these are consultancy gigs + 1 full time gig (or maybe it's part time) that could have a low hours/week commitment. He wouldn't be the first dev ever to moonlight.
Even if it were junior level work (trusting auth to be done correctly with junior engineers? LOL), he probably completed it faster than a junior engineer would.
His resume doesn't say he did auth. He used an open source library and made unspecified modifications to it. That's definitely something a junior level Dev could do.
"Or maybe it's part time". Exactly. A resume should give answers, not raise questions.
Expecting people to be charitable while reading resumes is unrealistic. A resume has to quickly demonstrate the applicants qualifications other wise it's trashed.
His resume is the problem. Two immediate things: (1) His most recent job lists junior level work and (2) He is claiming 3 concurrent jobs over the last two years.