Why design candidates get ghosted

A designer can spend hours preparing a portfolio presentation, have a promising interview, and then hear nothing. The silence gives them no reliable way to distinguish a rejection from a delayed decision or a role that has disappeared.

I used to interpret that silence mainly as a personal failure by the recruiter. In my original post, I reconsidered that assumption. A recruiter can be responsible for communicating a process without controlling its budget, priorities, or final decision. That does not make ghosting acceptable. It means fixing it requires looking at the hiring system as well as the person sending the emails.

This article does not use a prevalence estimate for ghosting or ghost jobs. The statistics quoted in my original post were not accompanied by enough source detail in the material available here to verify them. The practical problem can be discussed without pretending to know how often it happens everywhere.

Separate the silence from its possible cause

A role can stall because its budget changes, a hiring manager becomes unavailable, or the team revises what it needs. An internal move can change the vacancy. Interview feedback can sit unresolved because nobody has clear authority to finish the decision.

Those are possible explanations, not facts about any particular company. A candidate who receives no response cannot reliably infer which one applies. They also cannot know whether a posting was intentionally misleading or whether a genuine search changed direction.

That uncertainty is part of the damage. Without a clear update, people may postpone another conversation, keep time available, or repeatedly revise their interpretation of an interview. A short, honest message would let them make their own decisions with better information.

Assign responsibility before opening the role

When a company starts a search, someone should own candidate communication. That person needs a clear way to get updates and permission to communicate delays, changes, and closure. Responsibility without information is an invitation to silence.

The team should also decide who can pause or cancel the role and how that decision reaches the people running interviews. If recruiting learns about a budget change through unanswered messages, the communication problem began upstream.

I would make this part of the hiring setup rather than an administrative task to add later. The same discussion that defines the interview stages should define when candidates hear from the company and what happens if the planned timeline slips.

Give updates that help someone act

A useful update tells the candidate what is known, what remains undecided, and when another update will arrive. It does not need to reveal confidential internal details. It does need to avoid implying progress that is not happening.

For example, if the role is paused, say that it is paused. Explain whether the team has a date for revisiting it. If there is no reliable date, say so and make clear that the candidate should not keep their search on hold.

If an interview decision is late, acknowledge the missed expectation. Set a new communication date the team can actually meet, even if that date is for an update rather than a final answer. Then meet it. A repeated promise of “soon” gives the appearance of communication without providing useful information.

Close the process even when the outcome is uncomfortable

Rejecting someone is not a pleasant task, particularly after several conversations. But avoiding the message transfers the discomfort to the candidate and makes it harder for them to move on.

A rejection should state that the process has ended. Where the team can offer specific, job-related feedback, that can help. Where it cannot, it should not manufacture an explanation simply to sound considerate. Vague claims about personality or fit can leave someone with a new problem to interpret.

Closure also matters when the company cancels a role. A cancellation is not evidence that the candidate performed badly. Say that the hiring need changed rather than allowing the person to assume they failed an assessment that no longer led anywhere.

Make communication visible in the workflow

Good intentions are easier to sustain when the workflow makes unfinished communication apparent. Keep a record of each candidate's current stage, the last message sent, and the next date the team owes them an update.

Review that record alongside interview scheduling and feedback. A candidate waiting for a decision should not disappear simply because there are no more interviews to organize. If the search has an owner, closing those open loops belongs to that role.

A small team does not necessarily need a complex new system. It needs a shared view and someone who acts on it. The important question is whether the team can tell, at any point, who is waiting on them and what that person has been promised.

Protect your time as a candidate

Candidates cannot repair an employer's internal process from outside. They can ask how communication will work, who to contact, and when to follow up. At the end of an interview, confirm the next step rather than relying on a friendly closing remark.

If a stated date passes, a concise follow-up is reasonable. Mention the role and the expected update, ask whether the timeline has changed, and continue your search. You do not need to keep investing indefinitely to prove enthusiasm.

Silence is information about the experience of dealing with that company, but it is incomplete information about your ability. Resist turning it into a universal verdict on your work. A hiring process can fail to communicate for reasons you will never be able to resolve.

For teams, the standard is simpler: make the next step clear, tell people when it changes, and close the conversation when it ends. Respect for candidates has to survive an inconvenient decision.