It has been five days. You sent your availability within the hour. You even offered three different time slots to make it easy. And now? Nothing.
Not a confirmation. Not a rescheduling request. Not even a rejection. Just silence.
This is the most common question I see from engineering candidates mid-job-search, and the answer almost never has anything to do with you.
What Is Actually Happening Inside Their Pipeline Right Now
The availability request is not a scheduling confirmation. It is a signal that you passed an initial filter. But the actual scheduling decision requires input from at least two people: the recruiter and the hiring manager.
Here is what the silence looks like from inside the ATS.
Days 1 to 3: Probably Normal
Recruiters are not waiting at their desk for your reply. Most manage 15 to 30 open requisitions at once. When you send your availability back, it sits in their inbox while they are working other pipelines. Three days of silence after you responded is not a red flag.
If you open up Ashby or Greenhouse on my screen right now, here is what is actually happening: the availability request goes out in batch to multiple candidates simultaneously. The recruiter is waiting to collect enough responses before looping in the hiring manager to pick slots. Your reply went in, but the batch collection is not done yet.
Days 4 to 7: The Hiring Manager Has Gone Quiet
This is where the silence shifts from "normal process delay" to "something changed." The most common cause at this window is that the recruiter is blocked by the hiring manager.
The recruiter sent your availability upward. The hiring manager has not responded. This happens for several reasons: the manager is in an interview loop for another candidate and does not want to parallel-process, they are on PTO without flagging it to the recruiter, or they have privately decided to wait on a referred candidate who is still in the pipeline.
The recruiter is not going to tell you any of this. They either do not have updated information yet, or they do have it and know it is unfavorable. Either way, the default behavior is silence, not proactive communication.
Days 8 to 14: A Hold or Freeze Is the Likely Cause
If it has been two weeks with no response to your follow-up, one of three things has happened:
Scenario 1: The role is on hold. Headcount freezes do not always get announced publicly. A budget review, a leadership change, or a team restructuring can freeze an open requisition mid-pipeline. The recruiter gets an internal instruction to "pause" all active candidates. The ATS status changes on their end, but nothing is communicated to candidates. From your side, the last thing you remember is sending your availability.
Scenario 2: An internal referral is being processed first. Most tech companies have a policy that internal referrals must be evaluated before external candidates advance. If a referral came in after the recruiter reached out to you, your file goes into a queue behind that referral. The recruiter cannot tell you this because it would reveal internal hiring prioritization.
Scenario 3: The position was filled. Not necessarily from this search. An internal transfer, a boomerang hire, or a candidate from a parallel search closed the role. The recruiter's priority immediately shifts to their next open requisition. Closing out pending external candidates falls to the bottom of the list.
The Honest Reality About Ghost Jobs in 2026
Recent hiring data puts it plainly: 18 to 27% of active job postings right now are what recruiters call "ghost jobs." Roles that are posted to build a pipeline, test the market, or satisfy a job board contract, with no immediate intention to fill them.
How Much Does a Machine Learning Engineer Make in 2026? Levels.fyi & FAANG Breakdown
If a recruiter reached out to you from one of these postings and asked for your availability, that outreach may have been triggered automatically by a sourcing tool. The recruiter may have run a search, sent a batch of availability requests, and then been told by their director that the role is on hold. The availability request was already out. The hold came after.
This is not a conspiracy. It is a pipeline management problem at scale, and candidates are the ones who absorb the friction of it.
A 2026 hiring study found that 53% of job seekers were ghosted by an employer in the past 12 months, up from 38% in 2024. Roughly 65% of applicants now experience some form of mid-process ghosting. The availability request followed by silence is the most common form.
Red Flags vs. Green Flags After an Availability Request
| Signal | What It Means |
|---|---|
| Reply within 24 hours with a calendar invite | Strong. You are in. |
| Reply within 48 hours asking for more slots | Normal. They are coordinating with the hiring manager. |
| Auto-confirmation email, no human follow-up | Medium. You are in the scheduling system but not confirmed. |
| Silence for 3 to 5 days | Mild concern. Follow up once. |
| Silence for 7 to 10 days after your follow-up | High concern. A hold or competing candidate is likely the cause. |
| ATS status unchanged since you applied | The role may be frozen or already filled. |
| Recruiter viewed your LinkedIn profile recently | They are still active. Send your follow-up now. |
| Recruiter has left the company | Your contact is gone. Find their replacement on LinkedIn and start fresh. |
The Follow-Up That Actually Works
Most candidates either follow up too aggressively (multiple emails in a week) or not at all. Both are wrong.
The follow-up that works does two things: it reconfirms your availability is still valid, and it makes it easy for the recruiter to respond without having to explain the delay.
Send this on day 5 to 7 after your initial availability response:
Subject: Re: [Role Name] - Interview Availability
Hi [Name], I wanted to confirm that the times I shared on [Date] still work for me. Happy to adjust if any of those slots have been taken. Looking forward to next steps whenever works for your team.
Short. No pressure. No "just checking in" opener (recruiters see that phrase and immediately know they owe you something, which creates avoidance rather than a response).
If there is still no response after 7 more days, send one closing message:
Stripe Technical Interview Guide: How to Pass the Bug Squash & Integration Rounds (2026)
Hi [Name], I know priorities shift in hiring timelines, so I will stop following up and assume this one is not moving forward for now. If the timing changes on your end, I would still be interested. Thanks for reaching out initially.
That phrasing removes the social awkwardness of having to reply with a delay explanation, and it re-opens the door without being desperate. Recruiters respond to this message more often than you would expect, precisely because it takes the pressure off them.
What You Should Be Doing While You Wait
The hardest part is the temptation to hold your schedule open and treat this as a live opportunity. The moment you sent your availability, you did everything you could do. The pipeline is on their side now.
Keep applying. Treat this as if you already received a rejection. If they come back, great. If they do not, you have not lost anything because you stayed active.
One concrete action: check the job posting itself. If the role has been removed from the company's careers page but your portal still shows your application as "active" or "in review," the role is almost certainly closed or frozen. That information tells you more than any silence does.
For the full picture of how ATS status codes work at specific companies, the application status guide covers what each portal status means from the recruiter side. If you are interviewing through Greenhouse or Lever, the Greenhouse status guide and Lever status guide break down exactly what each status means internally.