Four scenarios - what might have been going on
Scenario one: shifting priorities.
The company posted the listing, and then something happened. Strategy change, reorg, budget freeze, a new department head who wants to "first see how things look." Applications wait for "a better moment." The better moment didn't arrive for five months.
What does this say? That decision-making processes are slow or opaque. That no one owns the open position and no one asks "what are we doing with this?" every week.
Scenario two: no process owner.
Someone posted the listing in the system. Someone else was supposed to handle applications. Nobody knew exactly who. Applications sit between HR and the hiring manager, neither feels responsible for follow-up. Classic "not my priority."
What does this say? That clarity of ownership is a problem. That "everyone's job is no one's job" - and that applies to recruiting too.
Scenario three: hiring freeze with no communication.
Recruiting went on ice. Maybe budget reasons, maybe organizational. But nobody informed candidates. Nobody removed the listing. Nobody sent a "we're sorry, we're pausing the process, we'll be in touch when things change."
What does this say? That external communication - specifically communicating difficult information - is a challenge in this organization. If saying "we can't right now" is hard in recruiting, how does it work with clients? With partners?
Scenario four: the application got lost.
Most mundane: the system swallowed it, the inbox got full, the email went to spam. Nobody checked. Discovered eventually.
Worth remembering what ATS systems actually do - this was covered in the earlier piece on AI and CVs. An ATS can "swallow" an application because of missing keywords, an incompatible file format, or a parsing error. The candidate received an automated confirmation and assumes the application arrived. Technically it did - it reached the system, not a human. 152 days might be exactly that: application technically accepted, practically invisible.
What does this say? That tools and operational processes aren't well managed. That there's no verification system.
Each scenario is plausible. None of them is "they're bad people." All of them say: "something here isn't working." And each one points to something different.
Candidate experience as a culture indicator
Recruiting is a candidate's first real collision with an organization. Not the "values statement" from the job listing. Not the beautifully written employer branding on Glassdoor. A real collision with the processes, people, and priorities of that company.
How do they write their listings? How quickly do they respond after an application? What do they do with your CV? Do they keep the timelines they set for themselves? Do they say "we'll get back to you within a week" and actually do it?
This is a sample of the organization.
If a candidate waits 152 days for a reply - I have one question: what does post-project feedback look like there? What do decisions look like? What does the annual performance review and salary conversation look like?
I'm not assuming every aspect of the organization is the same. But the correlation between candidate experience quality and internal culture is too strong to ignore. Companies that respect candidates' time generally respect employees' time too. Companies that treat applications like forgotten pizza - well.
The question "what does onboarding look like?" after 152 days isn't snarky. It's a genuine question - because if the recruiting process looks like this, it's worth knowing what to expect next.
Should you reply after 152 days?
I got the message. What to do with it?
Option one: yes, reply. Not because you have to, but out of curiosity or cautious openness. What does this company want now - five months after the listing? How do they explain the delay? Do they address it at all? Is the role still the same as it was? The information is free and might be valuable - or confirm that it's better not to get involved.
Option two: no, don't reply. Respect your own time. Over 152 days your context has changed. You have different projects, different priorities. The energy it takes to have that conversation has an opportunity cost - it could go somewhere better.
Option three: reply with one question. Not "thank you for reaching out, happy to chat." One specific question: "How long does onboarding take at your company?" or "What has changed in the role over the past five months?"
The answer to that question - both its content and the response time - will tell you more about that organization than an hour-long interview.
I went with option three. I replied. I heard nothing more.*
*Maybe that's also a diagnosis.
What a candidate can do - besides waiting
Proactivity has its limits. But there's a boundary between patience and passive waiting for something that may never come.
After two weeks from application - one follow-up. Short, no apologies for reaching out. "I sent my application X days ago - want to confirm it arrived and ask for an approximate status on the process." That's normal behavior, not pushiness.
After four weeks without a reply - a conscious decision: do I stay actively interested in this, or do I move my attention elsewhere? That's a decision. Not giving up, not quitting - conscious energy allocation.
After eight weeks - this specific hiring process probably no longer exists in the form you knew. You can confirm that with one email. Or not - and spend your time on something that's actually happening.
Waiting 152 days in hope with no signal of life is not a strategy. That's hope masquerading as a plan.
This is the middle part of the recruiting series. Earlier: how AI writes CVs and ATS reads them - and what that means for the whole system. Up next: why I stopped reading CVs before interviews - and what that changes.
One question to close: does your company know what its average response time to applications is? And does anyone even measure it - and if they do, does anyone look at it?