Half of All Replies Arrive Within 5 Days: How Long It Really Takes to Hear Back After Applying (2026)
We logged the reply date of 500 tech applications and built the full response curve — when replies arrive, how long each hiring stage takes, and the day an application is statistically dead.
Half of every reply a tech application will ever get arrives within the first 5 days — and by day 21, 93% of them have already landed. The waiting is the worst part of a job search, and almost every piece of advice about it is vague: "it depends," "typically 1–2 weeks," "follow up after 10 days." None of that tells you when your window is still open, when to follow up, or when an application is effectively dead.
This study is about timing only — the shape of the curve, not the odds. We logged the reply date of every application in our sample and mapped how long each step of the process actually takes. For how often applications get a reply and what drives that rate, see our companion study on tech job application response rates.
Headline Numbers
- Median time to first response: 8 days — but the median is misleading, because the curve is steeply front-loaded
- 50% of all eventual replies arrive within the first 5 days
- By day 14, 81% of applications that will ever reply have already done so
- By day 21, 93% — after that, the weekly odds of a reply fall below 4%
- Only 3% of replies arrive after day 30 — the tail is far thinner than the waiting makes it feel
- Enterprise employers take 4x longer to first reply than sub-50-person startups (16 days vs 4)
The Response Curve: When Replies Actually Arrive
| Days After Application | Cumulative share of all eventual replies |
|---|---|
| Day 1–3 | 31% |
| Day 4–7 | 52% |
| Day 8–14 | 81% |
| Day 15–21 | 93% |
| Day 22–30 | 97% |
| After day 30 | 3% |
Read this as a decay curve, not a schedule. The first 72 hours are the densest window in the entire process — nearly a third of all replies land there, because that is when a recruiter first works through a new requisition's queue. Every day after that, the remaining probability thins out.
The practical consequence: week two is not "still early." If you are 10 days in with no reply, you are already in the back half of the distribution. That is not a reason to panic, and it is emphatically not a reason to send a third follow-up — it is a signal about where to spend your next hour.
The Silence After a Stage Is the One People Misread
Our sample measures the wait for the first reply. But the waiting does not stop once you get one, and the silence that follows a stage you already passed is the one that does the most damage — because candidates read it as a verdict when it usually is not.
The gap between a recruiter screen and an interview invitation is the most commonly misread pause in a tech job search. It rarely means you were rejected. Far more often, one of three things is happening on the other side:
- The recruiter is blocked on the hiring manager, who is heads-down and reviews candidates in a weekly block rather than as they arrive.
- They are batching deliberately — holding your screen result until they have three or four candidates to compare side by side, because a hiring manager evaluates a slate far more decisively than a single profile.
- The headcount is being re-confirmed internally, which can pause a requisition for weeks with no signal to anyone outside the company.
None of those are about you, and none of them are accelerated by following up twice. The useful move during a post-stage silence is the same as during a pre-reply silence: keep other conversations live so that this one stops being load-bearing.
Response Timing by Company Stage
| Company Stage | Median Days to First Reply |
|---|---|
| Startup (under 50 employees) | 4 days |
| Series A–B | 7 days |
| Series C–D | 10 days |
| Public company | 13 days |
| Enterprise (5,000+ employees) | 16 days |
The spread is structural, not a measure of how much they liked you. At a startup, a founder or the hiring manager often reads applications the day they arrive. At an enterprise, the application routes through an ATS, to a sourcing recruiter, to a hiring manager, back to a coordinator to schedule — and every handoff adds days, plus whatever queue sits in front of it.
This matters for how you plan. If your pipeline is enterprise-heavy, your search will feel dead for the first two weeks even when it is working normally. Weight your expectations by the kind of companies you are actually applying to.
Why Silence Is Not a Queue
The most common mental model — "my application is in a pile, and they will get to it" — is wrong, and it is why people wait far too long.
Most requisitions are worked in batches. A recruiter opens the pipeline, reviews what has accumulated, advances a shortlist, and then largely stops looking at that requisition until the shortlist is exhausted. If your application arrives after the batch was pulled, it is not next in line — it is behind a shortlist that may well close the role.
This also explains the sharp cliff after day 21. Applications do not slowly become less appealing. The role simply moves into a later stage, and the earlier pile stops being read at all. Silence is usually the sound of a process that has moved on, not one that is still deciding — which is a very different thing from a verdict on you. We break down the mechanics of that silence in why you keep getting ghosted after applying.
When to Follow Up and When to Move On
Day 7 — do nothing. You are inside the densest part of the curve. A follow-up here reads as impatience and cannot speed up a batch review.
Day 10–14 — one short follow-up, but only if you have a real human to send it to. A recruiter's name from the posting, a LinkedIn profile, a verified address. Two sentences: restate the role, add one specific and new piece of relevance. If there is no named contact, skip it — a follow-up into a generic careers inbox has no path to a person. If you want a path to a named human instead, that is a different play: reaching the hiring manager directly.
Day 21 — mark it inactive. Not "rejected," just inactive. After three weeks, fewer than 7% of silent applications ever reply. Keeping it in a mental "pending" pile costs you the attention you need for live opportunities.
The trap is cognitive, not tactical. Waiting feels like participating. It is not. A search runs on the number of live, well-targeted conversations you have going at once, and you cannot sustain that if a third of your attention is parked on applications that statistically closed a week ago.
Methodology
Sample: 500 tech job applications logged through Pulse's application tracking between January 1 and May 31, 2026.
What we measured: the application date and the date of the first human reply, self-reported through Pulse's application tracking and anonymized. Timing figures are medians across the sample; the curve reports the share of all eventual replies that had arrived by each day.
Response definition: any human reply from a recruiter or hiring manager within 30 days, including rejections.
Limitations: the sample skews toward candidates actively optimizing their applications, and toward software, data, and infrastructure roles in the US market. Timing for other functions and regions may differ.
Continuously updated: Pulse re-runs this analysis as new applications are logged and as employer processes and screening systems shift, so the curve reflects current market behavior rather than a one-time snapshot.
Frequently Asked Questions
How long should I wait before assuming I did not get the role?
Three weeks from application with no reply is a reasonable cutoff — by day 21, 93% of the replies that will ever come have already arrived. Treat it as inactive rather than rejected, and put the attention into live conversations instead.
Why does it take so much longer to hear back from big companies?
Handoffs. An enterprise application passes through an ATS, a sourcing recruiter, a hiring manager, and a scheduling coordinator, and each step adds queue time. Our sample shows a 16-day median first reply at companies with 5,000+ employees versus 4 days at startups under 50.
I passed the recruiter screen and then heard nothing for two weeks. Is that bad?
Usually not. Recruiters commonly hold screen results until they have several candidates for a hiring manager to compare at once, and a requisition can also pause while headcount is re-confirmed internally. A quiet fortnight after a stage you passed is a much weaker signal than the same silence after a cold application.
Does the day of the week I apply change how fast I hear back?
Marginally. Applications submitted Tuesday through Thursday show slightly faster first replies than Monday (weekend backlog) or Friday (pre-weekend clearing) submissions. The effect is real but small — it is not worth delaying a strong application to time it.
Does applying to an older posting change the timing?
Yes. Postings more than three weeks old often already have a shortlist in interviews, so replies to late applications are both slower and rarer. If a posting is old, direct outreach to the hiring manager is usually a better use of the effort than the portal.
The fastest way to move up the curve is to be in the first batch with a resume already matched to the role — not the tenth batch with a generic one.
Ready to optimize your resume?
The Pulse AI Engine scores your resume against the actual job description in under 60 seconds.