Free Tool · No Signup

How Many Hours Will This Interview Loop Really Cost You?

Add up screens, take-homes, on-sites, prep, and decompression across every company in your pipeline. Most job seekers underestimate this by 40–60%.

🎯 Per-company total 📅 Pipeline-wide 💡 Verdict + tips
Preset Loop
Interview Stages (per company)
Stage
Rounds
Hrs / round
Recruiter screen
Intro call
Hiring manager screen
Fit + culture
Tech screen
Coding / role skills
Take-home / project
Stated hours × 1.75
On-site rounds
Loop of interviews
Reference / final calls
Comp, offer
Overhead
Rusty on a topic? Use 2–3. Fresh from another loop? Use 0.5–1.
3–5 is the sweet spot for most job seekers.
Enter total travel hours per in-person on-site (0 if virtual).

Interviewing right now?

See culture-tagged jobs at companies with reasonable interview loops. Every posting includes what the process actually looks like.

Browse Jobs → See Companies →

How to use this calculator

Interviewing takes way more of your life than you think. Most people count only the hours on the calendar — the 30-minute recruiter call, the 4-hour on-site — and forget the invisible middle: the prep, the take-home overruns, the decompression after a bad round, the emotional labor of writing follow-up notes. Multiply that per company, multiply by every company in your pipeline, and you get numbers that explain why job searches feel exhausting.

This tool makes the invisible visible. Enter the loop structure for a typical company you're pursuing, add your prep-hour multiplier, and pick the number of active pipelines you're running. You'll get:

Why the take-home multiplier is 1.75x

Every take-home takes longer than the company says. The stated time usually reflects "someone who has done this exact take-home before, in the exact tech stack, with a clean environment, and no anxiety about whether it's good enough." That's not you. Reading the prompt is 30 minutes. Environment setup is another 30. The actual coding is what they claim. But then you write the README, test edge cases, second-guess your API choices, refactor, and add extra polish because you know your competition will. A 4-hour take-home is usually 6–8 hours. An 8-hour is usually 12–16. 1.75x is a fair mean.

What the verdicts mean

Under 40 hours/pipeline: Your process is lean and you can run multiple pipelines without burnout. Common for mid-market or well-structured startup interviews.

40–80 hours/pipeline: Normal for senior engineering roles at top companies. Sustainable if you protect your evenings. Watch out if you're also doing your day job — this is where quiet quitting starts.

80–150 hours/pipeline: Heavy investment. If you have 3+ of these running simultaneously, you're going to burn out. Consider dropping one and using that time on the two you care most about.

150+ hours/pipeline: A red flag. Any company that requires this level of investment for a single hire is either running a bad process or filtering for candidates without other options. If the role isn't a "dream job" tier, walk away.

When to drop out of a process

The economically rational move — if uncomfortable — is to drop out of an interview process the moment your marginal cost exceeds expected marginal value. In practice: if a company asks for a second take-home, or adds a fifth round of on-sites, or makes you jump through non-standard hoops (case studies, sample marketing plans, day-long "trial projects"), that's a signal to walk. Companies with the highest per-candidate investment often have the worst hiring track record, because they're selecting for compliance rather than talent. Save your hours for the pipelines where the company is respecting your time.

Find companies with reasonable interview loops

Our Culture Directory tags companies by process style. Many engineering-first companies publish their full loop upfront.

Interview Prep Content →

Frequently Asked Questions

How many hours does an average tech interview loop take?+
For a senior engineering role, expect 15–25 hours per company end-to-end when you include the recruiter screen, tech screens, take-home or coding exercise, on-site rounds, prep time, and travel/decompression time. Companies with take-homes and multi-round on-sites (like FAANG or top-tier startups) skew toward the top of that range. Simpler processes (mid-market SaaS, smaller startups) can be closer to 8–12 hours.
Should I count prep time as part of the interview investment?+
Yes. Prep time is often the largest hidden cost, especially for a first company or a role type you haven't interviewed for recently. A rough rule: 1 hour of prep per 1 hour of interview for a familiar role, 2–3 hours of prep per 1 hour of interview if you're re-warming up (e.g. system design after years of not doing it) or targeting a top-bar company.
How many companies should I interview at simultaneously?+
3–5 active pipelines at a time is a reasonable ceiling for most people. Fewer than 3 makes it hard to compare offers and generates less negotiation leverage. More than 5 typically means the quality of your prep drops off and companies notice — you start showing up under-prepared to interviews you actually want.
When should I drop out of an interview process?+
When the incremental time investment stops paying off. If a company is asking for a 10-hour take-home for a role you're lukewarm about, and you have three stronger pipelines competing for the same evenings, drop out. Companies with excessive process (5+ on-site rounds, multiple take-homes, extensive homework assignments) often self-select for lower-priority candidates.
How do I estimate the time cost of a take-home?+
Take the company's stated time estimate and multiply by 1.5–2x. A "small 4-hour" take-home is almost always 6–10 hours when you include reading the prompt, environment setup, actually building the thing, testing, writing the readme, and second-guessing yourself. If a company says 8 hours, plan for 12–16.
Are on-sites always in-person in 2026?+
No. Most companies still run "on-sites" as a virtual block of 3–5 back-to-back interviews on a single day. Some senior/executive roles require in-person visits, which adds significant travel time. If the on-site is in-person, add travel and decompression time (often 6–12 additional hours) to your estimate.
How does this calculator help me decide?+
By making the invisible visible. Most job seekers underestimate their total interview investment by 40–60% because they only count the interview hours themselves, not prep, take-homes, follow-up, and decompression. Seeing the true total helps you prioritize your best pipelines and drop out of processes that aren't earning their weight.