He went through and found that almost all the applications he was able to go through were absolute nonsense.
He then screened some people before a technical interview with the rest of the team and found over half of them either had no clue how to really write any code or were completely lying about any experience they've had.
We then had five interviews set up for the following week. None of them were a fit. We have a pretty straight forward set of real world examples for our programming questions and no one got them. Keep in mind, all the other engineers on the team had gone through these questions without issue in the past, and we're not particularly amazing engineers. The "trickiest" of them is essentially performing an in memory group by given to arrays of data that have relations to each other. These were all full open internet as well.
We decided to pause hiring for the next quarter. I think the main issue was the absolute flood of applicants that had no ability to fill the role, and filtering through that with limited man-hours while features still need to be shipped is really difficult.
Years ago, when I'd be part of engineering hiring efforts, we had a recruiter who would handle screenings, so I don't know if it's always been like this and we need to get better at screening, or if it's notably worse now.