What 223 Job Applications Taught Me About Hiring Filters

Write-up ·

Summary

Since I was laid off in January 2026, I've tracked every job application I've sent. As of November 10, 2026: 223 applications, 2 interviews, 82 rejections, and 95 applications with no reply at all after 30+ days.

The biggest pattern isn't fast rejection. It's silence. I've worked in IT for 17+ years, most recently in identity and access management, including access reviews for SOC 2 and ISO 27001. From that side, this looks like a familiar problem: an automated control that nobody is checking.

The numbers

My tracker is built from my email, which is the only channel employers have used to contact me. All figures are as of November 10, 2026.

Grouped bar chart of applications sent and replies received each month from January to November 2026. Applications: Jan 6, Feb 29, Mar 10, Apr 22, May 20, Jun 14, Jul 7, Aug 17, Sep 30, Oct 27, Nov 28. Replies: Jan 0, Feb 7, Mar 5, Apr 9, May 13, Jun 12, Jul 6, Aug 5, Sep 17, Oct 11, Nov 6. November covers Nov 1 to 10 only. 13 applications without a recorded date are not included. Horizontal bar chart of what happened to 223 applications: 132 no reply (59%), 82 rejected or closed (37%), 9 other replies (4%). 2 led to an interview.
Application outcomes as of November 10, 2026
OutcomeCount
Applications sent223
Interviews2
Rejected or closed82
No reply yet132
No reply after 30+ days95
Other replies (viewed notices, a recruiter call, a questionnaire)9

What surprised me is how few rejections were fast. Only 3 came within a day of applying. The median was about two weeks. Most applications go into a system and nothing ever comes back.

Why I think it's a controls problem

I found a few studies from universities and tech firms that back this up. The largest, from Harvard Business School and Accenture, surveyed more than 8,000 workers and 2,250 executives in the US, UK and Germany. Most employers in that study agreed that qualified candidates are screened out because they don't match the exact criteria in the job description. They know, and many keep using these filters anyway.

My best guess is that wording is a real trap in IT. Microsoft renamed Azure AD to Entra ID. Some postings say M365, others say Office 365, others spell out identity and access management instead of IAM. A filter set to match one exact term can reject someone who has done that work for years, just because they wrote it the other way.

Volume and ownership

In my experience, a lot of it comes down to volume and ownership. I see it daily on LinkedIn: a posting I'm interested in went live less than an hour ago and already shows 100+ clicks on apply, from people, bots or AI agents applying on someone's behalf. Many likely never finish. Still, it's almost enough to make me not bother. But I apply anyway. And matching my resume and cover letter to each one takes real time. Even with AI and a fill-in-the-blank template I created, I still proofread every one.

I suspect recruiters are handling more applications than ever, often with smaller HR teams, or with screening outsourced to agencies and third-party firms that don't know the role or the team. Automation fills the gap, but nobody owns the outcome.

Some places now require employers to disclose when AI is used to screen applicants. Ontario has required it in job postings since January 2026 for employers with 25 or more employees. But disclosure isn't oversight. New York City requires bias audits of automated hiring tools, and a 2025 state audit found that enforcement has been weak.

What I'd check

If this were an access control, I believe an auditor would flag it. Here's what I'd check first:

I don't think any of this needs new technology. It needs someone to look.

What I'm doing about it

I use each posting's exact terms and write both versions where they differ, like "Microsoft Entra ID (Azure AD)". And where I can, I look for a referral or reach out to the hiring manager directly.

Sources