The Screen-Week Prep Batch, Six First-Round Calls From One Shared Core

This guide is for anyone with six first-round calls at six different companies landing in the same week. It shows how to prepare for multiple interviews in one week by building a shared core once and a capped delta sheet for each company, logging the minutes spent on each, and checking after the week which delta items the calls actually used. One worked batch runs through the whole method, wrong turns included.

What is a screen-week prep batch?

A screen-week prep batch has two parts: one shared core of answers you build once, and one short delta sheet per company, each with a time cap and a minute log. The core holds everything every screen asks. The delta holds only what changes from company to company.

A recruiter screen is the first call in a hiring process. It is typically 30 minutes and is run by a recruiter or sometimes a hiring manager, who checks the basics before the hiring team spends any time on you. Screens are standardised, which is why the split works. Published screening guides list the same six topics: your background, why you're looking, what you know about the company, your salary expectations, your start date, and whether you're interviewing elsewhere. Most recruiters then add two or three questions specific to the role.

Only two of the topics need per-company work. That is the whole argument for the split: if you prep the other four six times, you are rewriting the same answer six times.

How much time should a recruiter screen get?

Give each screen about 45 to 60 minutes of company-specific prep, on top of a shared core of 2 to 3 hours. That puts six screens at roughly 9 to 12 hours in total. Published prep-hour figures are mostly advice with no method behind them, and none of them is a per-screen benchmark.

These are the figures people quote:

The poll is the closest thing to data, and even its distribution could not be traced to a primary source by one publisher that went looking. Here is what candidates actually report:

• 60% of the accountants in the AICPA-CIMA author's poll spend 4 hours or less, 28% spend 5 to 9, and 12% spend 10 or more.
• 27% of the 100+ professionals Cooper Lomaz surveyed spent over 4 hours on their last interview.
• In a Glassdoor community poll, 23% said they don't prepare and 33% said they prepare 1 to 2 hours.

Compare that with how long candidates actually spend in interviews. By Ashby's count, the hired candidate spends 2.4 hours in all of a business hire's interviews and 3.5 hours for a technical hire. Ten hours of prep per company is roughly 3 to 4 times the time you will spend in that company's entire interview loop, and a screen is only the first 30 minutes of it.

The batch budget

These caps come from published minute budgets. Himalayas allots 45 minutes for five STAR stories and 30 minutes for the intro and "why this role". Pluckjobs says a focused 60 to 90 minute session yields enough material, and I cap the delta at the low end of that because a screen is a short call.

That comes to 560 to 740 minutes, or about 9 to 12 hours for the whole week. Following the "prep every interview as if it were the only one" advice at 5 to 10 hours each would cost 30 to 60 hours for the same six calls.

Why the delta gets capped and the core does not

The pass-through rate settles it. Ashby reports recruiter screens passing about 35% of candidates, across 54 million applications and 93,000 jobs. HackerRank's survey puts the average at 34% of phone-screened candidates.

The cap is not the same for every call. Set it with two questions: how much do you want this company, and is the call confirmed?

Who is on the other end of each screen?

Find out who employs the person running each call before you prep, because an agency recruiter, an in-house recruiter and a hiring manager need different delta sheets. In Refolk's index of professional profiles, 7 of 25 sampled US Technical Recruiters work at staffing or consulting firms.

An agency recruiter works for a staffing firm that places candidates with client companies. An in-house recruiter (often titled Talent Acquisition Partner) works for the hiring company itself. That difference matters for your notes. An agency recruiter may be pitching you several clients, and what they tell you about the client is the agency's account of it.

What this means for a batch:

• In a US search, plan for at least one agency screen. At 28% of a small sample, it would not be surprising if one or two of your six calls ran through an intermediary. Treat that as a likelihood, not a forecast. Twenty-five profiles is a small sample.
• In a UK search, expect more in-house and hiring-manager screens. Refolk's index has about 30 times as many US Technical Recruiter profiles as UK ones. The UK sample shows in-house employers (Monzo 3, Meta 2) alongside Capgemini 2 and Randstad Digital 1.
• Check it yourself for each call. Look at the recruiter's current employer on their profile and at the domain their invite came from. If either one differs from the hiring company, it is an agency call.

How each type changes the delta sheet:

• Agency recruiter: record the agency name and the client name separately. Ask which client the role is with if they haven't said. Your "why this company" line may have to wait until the client is named.
• In-house recruiter: the standard delta applies, and the company-knowledge question is most likely to come up here.
• Hiring manager: spend more of the delta on the role-specific questions and less on company facts. The two questions you ask should be about the work itself.

The worked batch: six calls in one week

The batch below is a composite I use to show the mechanics. The caps come from the published budgets above, and the wrong turns are three failure modes the practitioner record documents. I describe the minutes against caps rather than as precise measurements, because the point is to show where to look in your own log.

Triage (Monday, 20 minutes)

There are six calls, labelled A to F, ranked by interest. Following Tanay Agrawal's cohort method, all the recruiter screens are packed into one week, with the least-wanted companies scheduled first so that the early calls double as practice.

• Call A, Tuesday morning. Agency recruiter, client cloud company. Low interest. Cap: 45 min.
• Call B, Tuesday afternoon. In-house recruiter. Medium interest. Cap: 45 min.
• Call C, Wednesday. In-house Talent Acquisition Partner. Medium interest. Cap: 60 min.
• Call D, Thursday morning. Hiring manager at the company I want most. Cap: 60 min.
• Call E, Thursday afternoon. Agency recruiter, a different agency. Medium interest. Cap: 45 min.
• Call F, Friday. In-house recruiter. High interest. Cap: 60 min.

Six screens in one week goes against the LinkedIn advice page that suggests no more than two or three interviews per week. That page has no data behind it, and screens are short and repetitive enough that batching them is the point. Later rounds are a different matter.

Core (Monday, inside the 2 to 3 hour cap)

I wrote the core as one spoken page: a 90-second intro, a "why now" answer, a single salary range, the start-date and other-interviews answers, and five STAR stories (situation, task, action, result). The stories are the deepest part of the batch on purpose, because every call can draw on them.

Deltas (Monday evening and before each call)

Each company got one sheet built from the template further down. The posting re-read produced the two or three role questions I expected. When your resume was tailored to each posting, the re-read is quicker: Refolk keeps the version you sent to each company and scores how well you fit it, and the gaps in that fit score are where the role-specific questions tend to land. Use those gaps to decide which STAR story goes on each sheet.

Wrong turn 1: the favourite was over-researched, then cancelled

Call D was the company I wanted most, so its sheet grew well past its 60-minute cap: product history, leadership, a long list of questions. The hiring manager cancelled on Wednesday and rebooked into the following week. None of the extra research was used, and by the rebooked call some of the news on the sheet was older. The log showed the cause plainly: I had spent past the cap before the call was confirmed 24 hours ahead.

Wrong turn 2: a fact said to the wrong recruiter

On Thursday afternoon, during Call E with the agency recruiter, I mentioned a product launch as a reason for my interest. That launch was on Call B's sheet, not on the sheet for E's client. The recruiter corrected me politely. The cause was having two sheets open in adjacent tabs, with neither showing the company name at the top.

Wrong turn 3: the agency's view filed as the company's

On Call A, the agency recruiter said the client was "hiring fast across the team". I wrote it in A's debrief as a company fact. It was the agency's pitch. That doesn't make it false, but it is a different kind of claim, and it would have gone into the next round's sheet as if the company had said it.

Debrief and audit (after each call, then Friday)

The questions on every call followed the standard topic list closely, with role questions added on top. In the audit, the items marked used were the "why this company" line, the two questions, and the core STAR stories. The items marked wasted were the extra depth on D's sheet and any company detail beyond a single dated signal. Next week's change: Call D's rebooked prep stays at 60 minutes, and the delta template loses a section.

How to run the batch, step by step

Run these seven steps in order. Each has a time cap and a "done" condition you can check off, so you can tell when to stop.

Which company facts are safe to say on a screen?

A company fact is safe to say if it comes from the company's own channel, is dated within 90 days for news or 6 months for press, and has been checked against the latest 10-Q if it is a number. No published procedure ranks sources for this, so treat what follows as a working rule assembled from the closest published guidance, not an established standard.

Each source proves something different. A 10-Q proves a number was reported. A newsroom post proves the company said something on a particular date. A review theme proves only that several people had the same experience, and quoting a single review on a call proves nothing.

Your "why this company" line is where stale facts most often slip in. If you sent a cover letter, its company paragraph is a reasonable first draft. Refolk drafts one per posting, so that paragraph already exists. Every fact in it still goes through the checks above before it goes on the sheet.

COMPANY: [NAME IN CAPITALS]   |   Agency (if any): [agency name or "in-house"]
Call: [day, time, length]   Confirmed 24h ahead: [yes / no]
Recruiter: [name], employed by [employer]   Role: [title from posting]
Cap: [45 or 60] min   Minutes logged: [running total]

1. Posting re-read (3 lines max)
   - Must-haves I match:
   - Gap they may probe:      -> core STAR story: [#]
2. One dated company signal
   - Fact:                    Source URL:               Date:
   - If numeric, 10-Q checked: [yes / n/a private]
3. Why this company (one sentence, says only facts in item 2)
   -
4. Two questions for them
   -
   -
5. Core items to pull for this call
   - Salary range: [from core]   Start date: [from core]

How does the screen-week batch go wrong?

There are seven documented ways it goes wrong, and each one looks like diligence while it is happening. For each, the useful question is what the false signal is and what check exposes it.

A long sheet looks like readiness. The audit column marked wasted is the real measure.

1. The cap gets ignored on the call you like best.
   • False signal: a long, detailed sheet feels like being ready.
   • Check: compare logged minutes with the cap. Count the delta items marked wasted for that call.
2. Over-researching a call that gets cancelled. At about 35% pass-through, roughly 65% of screens don't advance, and some never happen at all.
   • False signal: depth done early feels like time saved.
   • Check: was the call confirmed 24 hours ahead before you spent past the cap?
3. A fact said to the wrong recruiter. IQ Partners warns specifically against using information from one interview in another.
   • False signal: you remember the fact clearly, just not which company it belongs to.
   • Check: one sheet open per call, with the company name in the header.
4. Treating the agency's view as the company's. In Refolk's US sample, 7 of 25 Technical Recruiters sit at staffing firms, and an agency recruiter may be pitching several clients.
   • False signal: a confident claim from the recruiter sounds like company policy.
   • Check: write down the recruiter's employer, not just the client, and tag every claim with who made it.
5. Stale "why this company" facts. A growth press release or a careers-page claim gets repeated with no date on it.
   • False signal: it is on the company's own site, so it must be current.
   • Check: inside 90 days, and confirmed in a 10-Q if it is a number.
6. Reading too much into reviews. Reviews are more likely to come from very happy or very unhappy employees.
   • False signal: one vivid review feels like inside knowledge.
   • Check: look for a theme across 10 recent reviews, and never quote a single review on a call.
7. Using borrowed statistics to justify prep time. The "47% rejected for not knowing the company" figure comes from an older Accountemps survey of 150 senior executives naming the most common mistake, not a share of rejections. A dated Accountemps release gives 38% for the same question. The "54% research the company" figure is described inconsistently: one source says it is before the interview, another says before applying.
   • False signal: a big percentage makes extra research hours feel mandatory.
   • Check: cite only the dated Accountemps release or Ashby, and read either one as support for a short, accurate sheet.

What does the end-of-week audit change?

The audit turns six debrief rows into next week's caps. You mark every delta item used or wasted, compare logged minutes against each cap, and cut whatever the calls didn't touch from the template. Without the log, you can't tell prep that helped from prep that only felt thorough.

Use one row per call, written within 15 minutes of hanging up. A Glassdoor practitioner describes the same habit: handwritten notes during the call, then a debrief into their own spreadsheet.

Date | Company | Recruiter (employer) | Agency? | Cap min | Logged min | Questions asked | Delta items used | Delta items wasted | Claims heard (who said it) | Advanced?

How to read the audit:

• Logged minutes well past the cap and items marked wasted means the cap was right and you broke it. Keep the cap and enforce the confirmation rule.
• Delta items used on every call (usually the why-this-company line and the two questions) means they stay. Consider moving their structure into the core.
• Delta items never used should be cut from the template.
• A role question you couldn't answer well should become a new core STAR story, because the core gets used on every call and the delta mostly doesn't.

Once a screen advances, it leaves this batch. Second rounds are scored by round type in the library's prep-budget guide, and the debrief row from the screen becomes the first input to that round's prep.