OPINION: “Just tell us no”: Job applicants call out hiring ghosting

Candidates say being left waiting after interviews wastes time and can cost them other job opportunities. 

Job applicants are calling out companies that stop responding after interviews, exams, or other stages of the hiring process, saying a simple rejection email would be enough to close the loop.

And really, that is not a lot to ask.

The discussion shared on Threads criticized companies and HR teams for not informing applicants when they are no longer being considered for a position, which many say wastes their time and resources while leaving them wondering whether they are still in the running.

For applicants, silence is rarely neutral. It can mean a position has already been filled, an application has been set aside, or a company is still deciding. Without an update, candidates are left to guess, and guessing is a poor way to manage a job search.

Several applicants shared similar experiences, including one who completed an exam after receiving an interview invitation, provided an available interview schedule, and then received no further response despite following up.

That kind of silence becomes particularly frustrating after an applicant has already invested time in the process. An exam, interview, portfolio, teaching demonstration or other requirement represents work on the applicant’s part. Once a company asks someone to keep participating, it also takes on a basic responsibility to say when the process is over.

Another applicant said the rejection itself was not the problem, particularly after reaching the final interview, but the lack of an update left the candidate waiting without knowing whether to continue looking for opportunities with other companies.

That distinction between rejection and communication came through repeatedly. Applicants are not necessarily expecting every interview to end in a job offer. They are asking to be told when the answer is no so they can act accordingly.

Some applicants also described situations where companies gave a specific timeline for an update but failed to meet it, even after follow-ups.

A promised update that never arrives creates a different kind of frustration. It gives applicants a date to wait for, then leaves them chasing the company for information that should have been provided in the first place.

Delayed responses can affect an applicant’s job search because candidates may hold off on other applications while waiting for a position they particularly want.

That is where the problem goes beyond simple courtesy. A candidate who believes an application is still active may spend days or weeks waiting instead of pursuing other opportunities. The cost of that uncertainty falls on the applicant, even though the company controls the information.

Another applicant recalled being told after a teaching demonstration that the application had passed and that only the HR announcement remained, only to learn months later, after following up, that the application had already been closed.

Months of waiting only to discover that the process had ended is a particularly stark example of how costly poor communication can become.

Companies may have plenty of reasons for delays. Hiring decisions can change, positions can be put on hold, internal approvals can take time, and recruiters may be handling several vacancies at once.

But none of those reasons makes a brief update impossible. A message saying an application is still under consideration, the timeline has changed, or the position has already been filled can take minutes to send.

As companies continue to fill vacancies, applicants will still have to navigate waiting periods between stages, including the point at which a position is filled or an application is no longer being considered.

Companies cannot promise every applicant a job. They can, however, tell applicants when they are no longer being considered.

For someone looking for work, that simple message can mean the difference between waiting for an answer and moving on to the next opportunity.

READ: