Why would you need one filter for "qualifications > 1" and a second one for "qualifications > 4" when you could just apply "qualifications > 4"?
If you put a hard programming question as a requirement just to APPLY for a job, I don't think you would get any good candidates at all. It's just not worth the time. When you're applying for a job you have no idea if the company is going to be interested at all, and that's fine, because there are just so many variables involved.
They could have just found someone and not yet taken the ad down. They could be about to receive an application from someone even better than you. They (or their system) might have some inherent bias against you, maybe even accidentally (degree > bootcamp, US college vs Canadian college, etc.).
When you're applying for a job it's just not feasible to go around doing HARD programming questions every time, because for so many reasons out of your control the company might just ignore you. And that's fine, that's for them to decide. But it means doing what you're saying would be a terrible, terrible idea, and actually most likely get the worst candidates who don't have any other options but can find a solution to your problem online.
> They could have just found someone and not yet taken the ad down.
> They could be about to receive an application from someone even better than you.
> They (or their system) might have some inherent bias against you
> When you're applying for a job it's just not feasible to go around doing HARD programming questions every time, because for so many reasons out of your control the company might just ignore you.
> you have no idea if the company is going to be interested at all
Most of those responses are going to candidates the company would never even consider hiring, because the initial filter is so worthless.