I teach and mentor people who are early in their careers, and a lot of them keep a spreadsheet. One column for the company, one for the role, one for the date they applied, one for the response. Scroll that last column and it is almost entirely blank. Sixty rows, seventy, a hundred. Two of them say rejected. The rest say nothing at all, because nothing at all is what came back.
A resume goes into an applicant tracking system and gets scored against a keyword list nobody publishes. Maybe a person reads it after that, maybe not. The applicant is never told which. The listing stays up for another month, then quietly comes down, or reappears with a fresh date on it. No one ever writes back to say the search is closed, or that it went to someone internal, or that it was frozen the week after it was posted. The applicant is left to infer all of that from an inbox that simply stays quiet.
Silence is not a verdict, but it gets read as one
Here is what a few months of silence does to a person. They start doing the math on themselves. They rewrite the resume for the fifth time. They wonder if the degree was worth less than they were told. They wonder if there is something about them a recruiter can see and they cannot. Fresh graduates get this the worst, because they have no earlier job search to compare it to. This is the whole data set they have. If every application disappears, the only pattern available to them is the one that points back at themselves.
None of that self-judgment is warranted by the evidence, because there is no evidence. A non-response is not a score. It does not mean a hiring manager read the application and found it wanting. Usually it means no one closed the loop, and the applicant has been handed the job of inventing a reason where none was given.
A system that never closes its loop
I think about hiring the way I think about any other process that opens requests and is supposed to answer them. If you sent a request into a system and it never responded, not once, not even with an error, you would call that system broken. A hiring funnel that takes an application and returns nothing is doing exactly that, and it gets away with it because the person left waiting has no standing to file the bug.
It is the same failure I wrote about when I said that if your absence breaks delivery, your system is fragile. A process that only works while nobody inspects it too closely is not efficient, it is just failing somewhere the people who run it never have to look. With hiring, the failure lands on applicants, one silent inbox at a time, and they carry it a lot longer than the company assumes.
What it costs to close it
If you own a hiring process, or you run a team small enough that you still touch it, the fix is cheap next to what the silence costs. A real no instead of nothing. A short, even generic reason instead of nothing. An automated line that at least confirms the search is over. None of that slows a pipeline down. It just means deciding that a loop you opened is one you are responsible for closing.
Do it and people remember. Skip it and they remember that too. The graduate who got one honest rejection from you will apply again in two years. The one who got a hundred silences has already decided what kind of place you are.
The applicant cannot fix this, and it is not theirs to fix. The silence was a design choice made by whoever built the funnel, and it can be unmade at the same desk. Until it is, capable people will keep reading an empty inbox as a message about themselves, and getting the message wrong.
Tahir Shahzad
Tahir Shahzad is a Product Manager, Product Owner, and technology consultant with over a decade of experience helping startups and organizations build products people actually use. If you are working on a product problem worth solving, reach him at tahirshahzad.com/contact/
