Interview Timelines: How Long
Hiring Really Takes
How many rounds, how many weeks, and how much of the wait is normal — broken down by company type, with sources, not vibes.
Published July 2026
Key findings
- Large MNC/FAANG-style loops (Google, Amazon, Microsoft, Meta) typically run 4–6 rounds and take 4–8 weeks application-to-offer; Glassdoor's aggregated data puts average process length at roughly 38 days for Google, 31 for Meta, and 28 for Amazon (all job titles blended, not engineering-specific).
- Indian IT services firms (TCS, Infosys, Wipro-type) run the fewest rounds — typically just 3 — and often decide within 1–3 weeks.
- Funded product startups and early-stage startups show the widest variance: 2–5 rounds and anywhere from under 2 weeks to over a month, depending almost entirely on how many people have to sign off.
- Industry-wide, hiring is getting slower, not faster: Greenhouse's 2025 benchmarks report found time-to-fill rose 37% from 2022 to 2025, and technical roles now average 17.6 interviews per hire, up 52% since 2021.
- A growing number of startups (Linear, Gumroad, and others) are replacing unpaid take-home assignments with short paid trials — a format shift that trades a few intensive working days for several weeks of drawn-out, abstract interviewing.
How many rounds, by company category
More stakeholders in the loop generally means more rounds. Named companies are included only where the round count is corroborated by public interview-experience sources (Glassdoor, candidate write-ups, prep guides) — see methodology below.
Large MNC / FAANG-style product co.
Google, Amazon, Microsoft, Meta
OA/phone screen + onsite loop (2–4 technical, 1 system design, 1 behavioral)
Indian IT services firm
TCS, Infosys, Wipro-type
Online aptitude/coding test, technical interview, HR/communication round
Funded product startup
Series A–D, e.g. fintech/consumer product cos.
Recruiter screen, technical/machine-coding round, system design, culture/HM round
Early-stage startup
Pre–Series A, under ~50 people
Founder/HM conversation, technical round or paid trial, sometimes a founder close call
Application to offer: total elapsed time
Ranges reflect the spread seen across public candidate reports, not a single guaranteed number. Individual timelines vary with role seniority, hiring urgency, and scheduling availability.
| Company category | Typical range | Notes |
|---|---|---|
| Large MNC / FAANG-style | 4–8 weeks | Meta and Amazon loops can compress to 2 weeks if scheduling is fast; Google often extends due to team-matching after the loop. |
| Indian IT services firm | 1–3 weeks | High-volume hiring with standardized rounds; decisions after the HR round are often communicated within 10–15 business days. |
| Funded product startup | 2–4 weeks | Widest variance of any category — a fast-moving Series B team can close in under 2 weeks; a process with multiple stakeholders can stretch past a month. |
| Early-stage startup | 1–2 weeks | Fewest approval layers. A founder who wants to hire you can go from first call to offer in days. |
Razorpay is a documented outlier worth naming: Glassdoor-aggregated candidate reports put its average hiring process at roughly 19.6 days, with some SDE roles closing in as little as 2 days and other "Software Engineer"-titled roles taking up to 45 days — illustrating just how much internal role and team can shift the number even within one company.
Interview processes are getting longer, not shorter
This is one of the more counterintuitive findings for candidates hoping AI tools and faster hiring software would speed things up. The opposite has happened, largely because application volume has exploded — and companies have responded by adding filtering stages, not removing them.
+37%
Rise in time-to-fill, 2022→2025
Greenhouse 2025 Hiring Benchmarks report, 6,000+ companies
17.6
Interviews per hire (technical roles)
Up from ~11 in 2021 — a 52% increase, per Greenhouse
3×
Growth in applications per hire, 2021→2024
Per Ashby's talent trends data, driven partly by AI-assisted mass-applying
Take-homes are giving way to paid trials — and that changes the timeline
A traditional unpaid take-home assignment can run 4–40 hours of a candidate's own time, spread across days or weeks around a current job — convenient to schedule, but a weak signal. It tests whether someone can produce a polished solution alone, with no time pressure and no collaboration, which is not what the actual job looks like.
A number of product-focused startups have moved to short, paid trials instead. Linear has publicly described paying candidates as contractors for 3–5 days to work directly in the real codebase; Gumroad has described running 4–6 week paid contract trials against actual roadmap items for some roles. The logic, in the words of teams that have adopted this: a short working session teaches you more about how a candidate thinks, communicates, and handles ambiguity than several more rounds of abstract interview questions — and it's an honest preview of the job for the candidate too.
The net effect on total timeline is usually positive for the candidate: a 3–5 day paid trial typically replaces two or three separate interview rounds and the multi-day gaps between scheduling them, rather than adding to the process. The tradeoff is a heavier time commitment concentrated into one block instead of spread thin — which is easier to justify when it's paid.
How long is normal to wait before assuming a rejection?
Silence doesn't always mean no — but these benchmarks are a reasonable point to stop assuming the best and start treating other opportunities as your priority.
After an online assessment / coding test
High-volume ATS filtering at large companies means OA results often batch-process on a schedule, not individually.
After a recruiter or HR phone screen
If a recruiter gave you a specific date and it passes silently, one follow-up at the 5–7 business day mark is reasonable before assuming a pause.
After a technical/onsite loop
At large companies this is where hiring-committee review and team-matching (particularly at Google) add real, non-responsive delay that isn't necessarily a rejection signal.
After a final round / founder conversation
The shorter the chain of people who need to sign off, the faster this should resolve — a startup stalling here for over a week is itself informative.
Sources & methodology
The figures in this report are synthesized from public candidate-review and timeline-tracking platforms — primarily Glassdoor's aggregated "interview experience" data, published candidate accounts and prep guides (e.g. IGotAnOffer, Educative, Prepfully), Greenhouse's 2025 hiring benchmarks report (6,000+ companies analyzed), and Ashby's talent trends research on startup hiring. These are self-reported and directional, not exact — a company's true internal average is rarely published, and individual experiences can deviate substantially based on role, level, urgency, and interviewer availability.
Where we could not verify a specific company's round count or timeline against a credible public source, we deliberately reported the pattern at the company-category level instead of attributing a precise number to a named company. Named-company figures in this report (Google, Amazon, Microsoft, Meta round counts and Glassdoor process-length averages; Razorpay and Zerodha timeline/round data) are drawn from multiple corroborating public sources; broader claims about Indian IT services firms, funded startups, and early-stage startups are presented as category patterns rather than single-company figures.
This report will be updated periodically as new benchmark data is published. Last reviewed July 2026.
Timelines are only half the story — the process itself looks very different depending on who's hiring. See how founders hire engineers for what actually happens inside a founder-led loop, including why speed-to-offer is treated as a competitive weapon rather than a courtesy.
A slow process is sometimes a company problem — but a resume that doesn't survive the first screen never gets a timeline at all. See common resume mistakes engineers make to make sure you're not adding weeks to your own search before round one even starts.
Rounds and weeks are only one axis of the wait — see our companion report on average response rates by company for the data on how long companies actually take to reply at each stage.
Interview timeline FAQs
How many interview rounds are normal for a software engineering job?
It depends heavily on company type. Large MNC/FAANG-style companies (Google, Amazon, Microsoft, Meta) typically run 4–6 rounds: an online assessment or recruiter/phone screen, followed by an onsite-style loop with 2–4 technical interviews, a system design round, and a behavioral round. Indian IT services firms (TCS, Infosys, Wipro-type) typically run just 3 rounds — an online aptitude/coding test, a technical interview, and an HR/communication round. Funded product startups usually land in between at 3–5 rounds, while early-stage startups often compress to 2–4, sometimes replacing a round entirely with a paid trial.
How long does it take to get a job offer after applying, on average?
Based on aggregated Glassdoor data, the total hiring process (application to offer) averages around 38 days at Google, 31 days at Meta, and 28 days at Amazon — though these are blended averages across all job titles at each company, not engineering-specific figures, and individual experiences vary widely. Indian IT services firms often move faster on paper (1–3 weeks) because of standardized, high-volume processes. Funded startups show the widest variance — anywhere from under 2 weeks to over a month, depending on how many people need to sign off on the hire.
Are interview processes getting longer or shorter industry-wide?
Longer, on average. Greenhouse's 2025 hiring benchmarks report (analyzing 6,000+ companies) found time-to-fill rose from about 43.6 days in 2022 to nearly 59.7 days in 2025 — a 37% increase. The same data shows technical roles now average 17.6 interviews per hire, up 52% from roughly 11 per hire in 2021. The likely driver is a sharp rise in applications per hire (partly from AI-assisted mass-applying), which pushes companies to add more filtering stages rather than fewer.
Why are some startups replacing take-home assignments with paid trials?
A classic unpaid take-home can take candidates many hours to complete and only tests whether someone can produce a polished solution alone, with no time pressure and no collaboration — a weak proxy for the actual job. Companies like Linear and Gumroad have publicly described running short paid trials instead — a few days of contract work on the real codebase or roadmap — which gives a much richer signal on how someone thinks, communicates, and handles ambiguity, while paying them fairly for the time. Because a paid trial replaces several rounds of abstract interviewing with one immersive block, it can shorten total elapsed time even though the trial itself takes a few working days.
How long should I wait after an interview before assuming I've been rejected?
As a general benchmark, most candidates hear back within 1–2 weeks, with a median response time around 6–7 days for a single stage. At large MNCs, allow more slack — 1–3 weeks after an onsite loop is common because of internal review committees and, at some companies, team-matching. At startups, a well-run process should update you within a few days to a week at each stage; if a startup goes quiet for more than 1–2 weeks after a final round with no explanation, that itself is a meaningful signal, either about a stalled decision internally or a deprioritized role.
Do bigger companies always take longer to hire than startups?
Usually, but not always. Large companies have more approval layers (hiring committees, team matching, HR coordination) that add structural delay. But a motivated startup founder or hiring manager can also drag out a process by juggling other priorities, and Ashby's startup hiring research notes that as companies scale, timelines actually become more consistent even if not always faster — the tradeoff shifts from raw speed to predictability. The most reliable rule is: fewer decision-makers in the loop generally means a faster, more predictable timeline, regardless of company size.
Skip the black hole
The fastest timeline is the one
with the fewest people in the way.
Switchly's AI parses your resume and routes your application straight to the founder, CTO, or hiring manager — no recruiter screen, no ATS queue, no guessing where you stand.