TL;DR: Ashby's 2026 Talent Trends data shows a 40-day median time-to-hire for technical roles across the platform. Active startup pipelines move faster — 2 to 4 weeks application to offer is realistic. At high-volume AI labs, add 2 to 4 weeks of initial screening queue time. Silence at each stage has a specific meaning; this guide breaks it down by day range and stage.
Ashby's own 2026 Talent Trends Report, analyzing over 109 million applications and 247,000 jobs through March 2026, puts the median time-to-hire for technical roles at 40 days. Business roles run 30. Technical hiring takes twice the interview hours and one additional interview event compared to non-technical roles on the platform.
That number spans every company on Ashby — from 20-person seed startups that interview in two stages to frontier AI labs with 6-round loops and committee review. Where you land in that 40-day median depends almost entirely on which company is running your pipeline, not on the platform.
Here is the stage-by-stage breakdown, what the silence at each point actually means from the recruiter's side, and the exact benchmarks by company type.
The Stage-by-Stage Ashby Timeline (2026 Benchmarks)
The table below represents realistic timelines based on 2026 hiring cycles across companies using Ashby. Ranges reflect lean startup teams on the short end and high-volume AI labs on the long end.
| Pipeline Stage | Lean Startup (under 500 employees) | AI Lab / High-Volume (OpenAI, Anthropic) |
|---|---|---|
| Application to first contact | 3 to 7 business days | 10 to 20 business days |
| Recruiter screen to technical screen | 2 to 4 business days | 5 to 10 business days |
| Technical screen to onsite or final loop | 3 to 7 business days | 7 to 14 business days |
| Final loop to verbal offer | 5 to 10 business days | 7 to 14 business days |
| Verbal to written offer | 2 to 4 business days | 2 to 5 business days |
| Total: application to written offer | 2 to 4 weeks | 5 to 10 weeks |
One thing that drives the outliers: automated scheduling. Ashby's internal data shows their automated scheduling workflows run 26% faster than manual scheduling. Companies that use Ashby's scheduling automation move candidates through stages noticeably faster than those still running calendar coordination by email. If your recruiter sent you a self-scheduling link, you are in an automated pipeline and can expect tighter inter-stage windows.
What the Silence Actually Means at Each Stage
This is the part most articles skip. Day 3 silence does not mean the same thing as day 12 silence, and the reason depends on where you are in the pipeline.
After Application: Days 1 to 7
Your application is in a queue. On the recruiter's Ashby dashboard, applications feed into a review stack sorted by source (referrals are pinned at the top), AI relevance score, and submission date.
Working inside engineering hiring pipelines, the pattern is consistent: recruiters at lean startups batch their resume review in sessions, typically once or twice a week. If you applied Monday and the recruiter's review session is Friday, you sit at day 5 before anyone has opened your file. That is not a slow pipeline. That is a normal two-person recruiting team with 12 open roles.
At high-volume AI labs, the initial queue is longer because applications per hire remain elevated above 300 in 2026 across the platform. "In Review" in Ashby can mean an AI relevance score put you in the manually-reviewed shortlist, but the recruiter has not reached your name yet.
What to do: Nothing until day 10. Then one professional follow-up email.
After Recruiter Screen: Days 1 to 5
The recruiter has a call with you and submits internal feedback. In Ashby, this shows up as a scored note attached to your profile, visible to the entire hiring team.
What is happening on the recruiter's side in this window: they are getting alignment with the hiring manager on whether to move you forward. At most lean startup teams, this conversation happens the same day or the following morning. The decision is simple: the recruiter either has the authority to move you themselves, or they send the hiring manager your profile and scorecard and wait for a reply.
The wait at this stage is almost always a hiring manager response lag, not recruiter delay. Most hiring managers at high-growth startups are context-switching between product work and hiring simultaneously. A 48-hour response lag from a hiring manager who is heads-down on a release is not unusual.
What to do: Wait 5 business days. Then one email to your recruiter asking for a status update.
After Technical Screen: Days 1 to 7
This is where the timeline starts to stretch for the first time. After a technical screen (coding challenge or live coding round), the recruiter needs:
- Written feedback from the interviewer
- A calibration conversation with the hiring manager
- Scheduling of the next stage (often 3 to 5 interviewers across the onsite loop)
Step 3 is where time goes. Even at a fast-moving 200-person company using Ashby's automated scheduling, aligning 3 to 5 interviewers for a single-day loop typically takes 3 to 7 business days. Ashby's scheduling automation helps surface open slots faster than manual coordination, but availability constraints are real.
What to do: Wait 7 business days. Then follow up with your recruiter with specific questions: ask whether there is anything else you need to provide and request a rough timeline for the next step.
After the Final Interview Loop: Days 1 to 10
This is the stage candidates most consistently misread.
The debrief notes reviewed across engineering pipelines tell a consistent story: the window between final round and verbal offer is not dead time. Here is what the internal process at Ashby-using companies looks like during this window:
| Day Post-Loop | What Is Happening Internally |
|---|---|
| Day 1 to 2 | Each interviewer submits written feedback and a score in Ashby. No decisions yet. Scores are independent. |
| Day 2 to 4 | Recruiter schedules a debrief sync. Panel scores are reviewed. Disagreements between strong hire and hire ratings are discussed and resolved. |
| Day 4 to 6 | Hiring manager makes a hire or no-hire call. If hire: headcount approval requested. Comp band confirmed against current budget. |
| Day 6 to 10 | Verbal offer prepared and extended. Written offer package drafted. |
| Day 10 and beyond | Headcount hold, active calibration discussion, or a close call that needs a second review. Follow up at this point. |
Candidates who wait silently past day 14 without following up sometimes lose out because another candidate accepted an offer while they were waiting. Do not be that candidate.
What to do: Follow up at day 10. Email your recruiter directly and ask for a sense of the timeline. If you have a competing offer, mention it now.
By Company: How Ashby-Powered Pipelines Actually Move
The same platform, very different speeds. Here is what the pipeline looks like at the most common Ashby-using employers in 2026:
OpenAI
OpenAI uses Ashby and runs one of the highest-volume engineering pipelines in tech. Application to first contact regularly runs 2 to 4 weeks. The debrief process after a final loop involves a cross-functional review that adds time. Many candidates report a 3 to 6 week total process from application to offer.
One thing that accelerates the OpenAI pipeline significantly: referrals. Referred candidates are flagged in Ashby and jump the manual review queue. If you know someone internally, a referral before you apply cold is the single highest-leverage action available to you. For a detailed breakdown of what happens after each OpenAI interview stage, see the OpenAI interview response time guide.
Anthropic
Anthropic's use of Ashby is notable because they often do not surface a candidate portal at all. Status updates arrive exclusively by email. The absence of portal visibility is a configuration choice, not a negative signal.
Anthropic averages a 20-day response time from application to recruiter contact for engineering roles, but that average hides significant spread. Research roles can run 3 months. The team matching phase — specific to Anthropic's process — adds 2 to 4 weeks of complete silence that candidates consistently misread as rejection. It is not. See the Anthropic interview response time guide for the full team matching breakdown.
Notion
Notion runs a structured Ashby pipeline with a recruiter screen, a take-home or live coding screen, and a 3 to 4 round loop. Total timeline from application to offer typically runs 3 to 5 weeks. Notion is a product-first culture — the behavioral rounds carry more weight than the pure algorithmic screen. Post-loop, most candidates hear back within 5 to 7 business days, which is among the faster turnarounds at a company of Notion's size.
Figma
Figma runs one of the fastest post-loop turnarounds in the industry: 3 to 5 business days from final round to verbal offer. Total process from application to offer spans 3 to 5 weeks. The catch: Figma's pipeline filters heavily on what they call the "multiplayer" mindset — engineers who treat interviews as collaborative sessions rather than solo performance tests. Candidates who code silently through technical rounds are rejected at a higher rate regardless of output quality. For the full breakdown, the Figma interview response time guide covers each stage in detail.
Ramp
Ramp's Ashby pipeline includes a pre-application puzzle (a lightweight technical gate built into the careers page) before a human touches your application. The pipeline itself runs 2 to 4 weeks from application to offer for SWE roles. The CodeSignal OA is the highest-attrition stage. Post-onsite, most candidates hear back within 5 to 10 business days. See the Ramp interview response time guide for what happens during debrief.
Linear and Vercel
Linear is notable for including a paid 2 to 5 day work trial as a final stage. Because the trial is a significant commitment for both sides, earlier stages are front-loaded with filtering. Total timeline runs 3 to 6 weeks. Vercel operates a lean, founder-aligned pipeline that typically runs 2 to 4 weeks. Both companies run through Ashby, and both prioritize candidates who are demonstrably users of their own products.
The Two Things That Speed Up Any Ashby Pipeline
Across every company above, two factors consistently compress the timeline:
Referrals. Ashby tracks application source at the platform level. Referred candidates are surfaced differently in the review queue than cold applications. At high-volume companies like OpenAI and Anthropic, a referral from a senior engineer is the most reliable way to get a human to read your resume in the first week instead of the third.
Scheduling responsiveness. Ashby's automated scheduling links show up in email and become stale if candidates do not book quickly. Files get deprioritized when a candidate waits 4 or 5 days to book an available slot while the recruiter is moving 6 other candidates simultaneously. Book within 24 hours of receiving a scheduling link unless you have a specific conflict.
Ashby vs. Greenhouse vs. Workday: Timeline Comparison
Candidates frequently ask whether the ATS platform determines how fast they will hear back. The platform does not drive speed — the company does. But company type correlates strongly with ATS choice, and that correlation produces a real pattern:
| Platform | Typical User Profile | Application to First Contact | Total Process Range |
|---|---|---|---|
| Ashby | High-growth startups, AI labs, Series B+ | 3 to 20 business days | 2 to 10 weeks |
| Greenhouse | Mid-market tech, Series C to pre-IPO | 5 to 15 business days | 3 to 8 weeks |
| Workday | Enterprise, Fortune 500, banks | 14 to 30 business days | 6 to 16 weeks |
| Lever | Mid-market, agency-heavy pipelines | 5 to 14 business days | 3 to 7 weeks |
| iCIMS / Taleo | Large enterprise, government contractors | 14 to 45 business days | 8 to 20 weeks |
The Workday gap is structural. Enterprise companies using Workday have multi-tier approval chains, centralized HR review before any hiring manager contact, and job requisition processes that can stall a new role for weeks before it reaches the recruiter's queue. Ashby companies, by design, do not have those layers.
If you want to understand how to read the status signals in Ashby specifically, rather than just the response timeline, the Ashby application status guide covers every portal status from "In Review" to "Archived" and what is actually happening on the recruiter's side when each one appears.
Follow-Up Schedule That Works Across Ashby Pipelines
The timeline that does not irritate recruiters and keeps your file visible:
| Stage | When to Follow Up | How |
|---|---|---|
| After application | Day 10 with no contact | One brief email to the job posting contact |
| After recruiter screen | Day 5 with no update | Email your recruiter directly |
| After technical screen | Day 7 with no next-step | Email recruiter; ask for timeline |
| After final loop | Day 10 with no update | Email recruiter; mention competing offers if relevant |
| After verbal offer | Day 2 with no written offer | Email recruiter; confirm expected timeline for written offer |
One follow-up per stage. Not two. Recruiters running 15 to 20 active pipelines simultaneously see every email. The ones that get responded to fastest ask a clear, specific question rather than expressing general anxiety about the process.
If you have a competing offer with a real deadline, communicate it the moment you receive it. A concrete deadline changes the internal approval sequence. Recruiters can escalate headcount approvals when a real deadline exists. They cannot escalate on your behalf without one.
FAQ
Q: How long does Ashby take to respond after you apply?
The response timeline depends entirely on the company running Ashby. Lean startup teams typically make first contact within 3 to 7 business days for active roles. High-volume AI labs like OpenAI and Anthropic often take 10 to 20 business days. Ashby's 2026 Talent Trends data shows a 40-day median time-to-hire for technical roles across all companies on the platform.
Q: Does Ashby send rejection emails automatically?
Only if the company configured automated rejection workflows. Many lean startup teams have not done this, meaning an Archive action produces no email to the candidate. If your status has not changed for more than 3 weeks on an active role, treat it as a soft rejection and keep applying.
Q: Why is my Ashby portal not showing status updates?
Many companies using Ashby choose not to surface a candidate-facing portal, or configure it to show minimal status changes. All meaningful updates arrive via email from an ashbyhq.com address or from the company's own domain. Monitor your inbox, not just the portal.
Q: How long after an Ashby recruiter screen before hearing back?
Most companies turn this around in 2 to 5 business days. Lean startup teams are typically faster at 48 to 72 hours. High-volume pipelines like OpenAI and Anthropic may take 5 to 10 business days as recruiters batch decisions.
Q: What does 10 days of silence after an Ashby final interview mean?
It is within normal range. The debrief cycle typically runs 3 to 7 business days. Headcount approval may add another 3 to 5 business days. At day 10, one professional follow-up email to your recruiter is appropriate and expected.
Q: Is Ashby faster than Greenhouse or Workday for candidates?
The platform does not determine speed — the company does. That said, companies using Ashby in 2026 tend to be lean, high-growth teams with simpler approval structures. The practical result is that Ashby-using startups move faster than enterprise companies on Workday, which can take 4 to 6 weeks for initial screening alone.
Q: How long does Ashby take to extend an offer after the final interview?
Most Ashby-using companies extend a verbal offer within 5 to 10 business days of the final round. The bottleneck is the internal approval chain — headcount approval, comp band review, and equity sign-off — not the platform.
Q: What companies use Ashby ATS in 2026?
OpenAI, Anthropic, Notion, Figma, Ramp, Linear, Vercel, Plaid, PostHog, Deel, and hundreds of other high-growth tech companies. It is the dominant ATS choice for Series B and above companies that have outgrown basic tools but do not want enterprise-level complexity.