# The Thin-Prep Interview Standard, Graded Ready Before Each Call

*You will grade any upcoming interview pass or fail against a fixed minimum-readiness bar in about fifteen minutes, per call.*

- Canonical URL: https://www.refolk.ai/candidates/guides/thin-prep-interview-standard
- Pillar: Applying at volume
- Format: Standard
- Published: 2026-09-26
- Last reviewed: 2026-09-26
- Reading time: 15 min

You have several interviews this week and cannot spend ten hours on each. This standard defines the least prep that still counts as ready, states it so two people grading the same call would reach the same verdict, and gives you a checklist to verify it in about fifteen minutes per call. It is written for a job seeker running an active pipeline across many companies at once, where over-investing in any single interview quietly starves the rest.

## Why the published prep advice does not scale

The top-ranking prep advice contradicts itself, and that contradiction is exactly the gap this standard fills. Indeed recommends five to 10 hours per interview and, in the same body of advice, tells you to prepare each interview "just as you would if it were the only one you had." Run that across five calls in a week and you are looking at 25 to 50 hours of prep for interviews that each last under an hour. It is unusable at volume.

The disagreement runs deeper than one source. Cooper Lomaz bands prep into minimal at 3 to 6 hours, solid at 10 to 15 hours, and deep at 15 to 20+ hours for competitive or senior roles, and cites experts who recommend 10 to 20 hours per company for high-level or technical positions. Monster, by contrast, publishes a fast plan that totals about four hours. These are not small differences; the deep end is five times the fast plan.

The way out is not to pick a number. It is to define a floor: the minimum evidence each task must produce for a call to count as ready, and the checks that prove it. Below the floor, you are gambling. Above it, you are spending time you do not have across a pipeline.

**60% - Surveyed professionals who spend four hours or less preparing for an interview**

Only 12% spend ten hours or more, so a graded four-hour floor describes what most candidates already do.

Thin prep is not a corner cut. It is the market norm made verifiable. About 60% of surveyed professionals prep four hours or less and only 12% reach ten hours, so a fixed sub-four-hour floor describes the realistic baseline rather than an aspirational ceiling. A separate survey found only 27% spent over four hours on their last interview. The standard here simply makes that common practice gradeable.

## What "ready" means: the definition of done

Ready means the call clears a fixed floor of five evidence tests, each producing something you can point to, not a feeling. If you cannot point to the artifact, the call is not ready, regardless of how prepared you feel.

The floor is built from the tasks whose absence gets people rejected, front-loaded ahead of the tasks with diminishing returns. Two of the cheapest tasks carry the most rejection risk. Company familiarity and having questions ready are both named deal breakers, and each costs under an hour. Answer rehearsal, by contrast, hits diminishing returns fast at five to 10 minutes per question. So the floor spends its scarce minutes on the deal breakers first.

Here is the floor, stated as pass conditions:

- **Company connection.** Three to five talking points, each tied to a specific line in the job posting. Not trivia: a link between what the company does and what the role needs.
- **Story bank.** Three quantified stories for a thin call, six to eight for a full loop, each spoken aloud at least once.
- **Questions to ask.** At least three, none of them answerable by a quick web search.
- **Interviewer look-up.** Each named interviewer checked, with one connection point noted.
- **Logistics.** Link or location, time zone, and resume copies confirmed.

> **Rule:** The floor is evidence, not effort
>
> A call is ready only when each of the five tests points to a concrete artifact: talking points on the sheet, stories spoken aloud, written questions, a confirmed interviewer, confirmed logistics. Time spent without those artifacts does not clear the floor.

Notice what is deliberately absent. There is no requirement to memorise the company's full history, no requirement to rehearse every possible question, no requirement to build fresh material per company beyond the talking points and questions. Those are the parts that do not scale, and the evidence does not show they move the outcome once the floor is met.

## What the published guidance actually prescribes

The published prep-time numbers span a five-fold range, so treat them as the ceiling you are undercutting, not the target you are hitting. The table below is the full spread from the ranking sources, which is worth seeing plainly before you decide how far below it you can safely sit.

| Source | Minimum | Recommended or typical | Deep or senior |
| --- | --- | --- | --- |
| Indeed | not stated | 5 to 10 hrs | not stated |
| Cooper Lomaz | 3 to 6 hrs | 10 to 15 hrs | 15 to 20+ hrs |
| Cooper Lomaz (experts) | not stated | 10 to 20 hrs (technical) | not stated |
| Monster (fast plan) | ~4 hrs total | not stated | not stated |

The task-level numbers explain where the hours go. Company research alone is quoted at one to five hours; interviewer look-up at one to three hours. The floor compresses both hard: 20 to 60 minutes for research, about ten minutes for the look-up. That is where most of the savings live, because both tasks have a clear point of sufficiency. Once you can connect the company to the role and name one thing about each interviewer, more hours add little.

> Spend your scarce minutes on the deal breakers first, because the cheapest tasks carry the most rejection risk.

## The bar shifts by stage, not by company

Match the prep budget to the stage of the interview, because a recruiter screen and a final panel test entirely different things. Treating them the same is the most common way people misallocate effort across a pipeline.

A recruiter screen runs 15 to 30 minutes and is a triage call, not a deep technical evaluation. It validates qualifications, gauges interest, and confirms logistics. Heavy technical prep for a screen is wasted; what it needs is a clean motivation answer, a salary range, and a couple of questions. A hiring-manager round goes deeper into role fit, past work, and how you think through real problems, so it needs the story bank mapped to the posting. A panel or final round assesses how you work with different stakeholders and is increasingly a scorecard-driven decision, so it needs a distinct question per interviewer.

#### Prep effort by stage, thinnest on top

1. **Recruiter screen** - 15 to 30 min triage - three talking points, salary range, two questions
2. **Hiring-manager** - role fit and problem-thinking - three to six stories mapped to the posting, three questions
3. **Panel or final** - scorecard decision on stakeholder fit - six to eight stories, a distinct question per interviewer

*The recruiter screen needs the least; the panel needs the most, because each tests something different.*

The stage-by-stage floor, stated as pass conditions:

| Stage | Runtime | What it tests | Floor evidence |
| --- | --- | --- | --- |
| Recruiter screen | 15 to 30 min | qualifications, motivation, logistics | 3 talking points, salary range, 2 questions |
| Hiring-manager | ~45 to 60 min | role fit, past work, problem-thinking | 3 to 6 stories mapped to posting, 3 questions |
| Panel or final | ~45 min | stakeholder fit, scorecard decision | distinct question per interviewer, 6 to 8 stories |

This is why the same fifteen-minute grade produces different verdicts for different calls. A screen with three talking points and two questions passes. A panel with the same evidence fails, because one prepared question for five interviewers does not clear the bar.

## The story bank is what makes this scale

Six to eight flexible stories, built once, carry across your entire pipeline, and that is the single mechanism that makes a fixed floor affordable at volume. Because the same stories can answer most behavioural questions by shifting emphasis, the marginal prep cost of each additional interview falls sharply once the bank exists.

The recommended bank is six to eight stories covering ownership, judgment, teamwork, communication, prioritization, adaptability, and failure. For a thin call you can run on three. Each story must quantify its result: "increased sales by 20%" beats "improved sales." A story without a number is a claim without evidence, and it reads as one.

The check that separates a real bank from a false one is spoken practice. Say your answers aloud rather than reviewing them in your head, because spoken practice reveals awkward phrasing that silent review hides. A bank that has never been spoken is a list, not a bank.

**STAR story card, one per story in the bank**

```
Situation: [one line of context, when and where]
Task: [what you were responsible for]
Action: [what you personally did, the decisions you made]
Result: [the quantified outcome, e.g. cut processing time 30%]
Covers: [ownership / teamwork / failure / prioritization / communication]
```

*Fill one card per story. Reuse across companies by re-pointing the last line to whatever competency the question asks about.*

Build these cards once. Then, per interview, the only new work is the company pass, the interviewer look-up, three questions, and logistics. That is the entire per-call cost after the first, which is what lets you clear a crowded week without any single call exceeding its budget.

If reconstructing quantified stories from your own history is the slow part, [Refolk](/candidates) writes your resume from your work history and scores how well you fit each posting, which surfaces the achievements worth turning into story cards instead of making you dig for them.

## The procedure: grade one call in fifteen minutes

Run these eight steps in order for each interview. The first pass builds the artifacts; every later call reuses the story bank and only repeats the company-specific steps. The whole floor fits inside four hours for a first full loop and roughly fifteen minutes to verify a call once the bank exists.

#### Thin-prep procedure, per call

1. **Log the interview** - Create one document per company as a study sheet, and capture date, time, format, and key contact.
2. **Confirm stage and interviewer names** - Label the round as screen, hiring-manager, or panel, since the stage sets the bar, and note any interviewer names shared in advance.
3. **Company research pass** - Skim site, news, and posting, and write three to five talking points each tied to a line in the job description. Target 20 to 60 minutes.
4. **Interviewer look-up** - Open each named interviewer on LinkedIn and note one connection point. The floor is a single check, about ten minutes.
5. **Story bank check** - Confirm three quantified stories for a thin bar, or six to eight for a full loop, and reuse the same bank across companies.
6. **Rehearse aloud** - Say your top answers out loud once, spending five to ten minutes per question, to catch awkward phrasing.
7. **Prepare questions to ask** - Write at least three specific questions about the job, team, or culture. For a panel, write a distinct question per interviewer.
8. **Logistics check** - Confirm the link or location, the time zone, and that you have resume copies to hand.

#### Where interviews are lost before they start

| Stage | Figure | Note |
| --- | --- | --- |
| Calls in pipeline this week | 5 | every one graded against the same floor |
| Cleared company + questions floor | 4 | the two named deal breakers |
| Story bank spoken aloud | 3 | silent review does not count |
| Fully ready by the standard | 3 | logistics and interviewer checked |

*The floor front-loads the tasks whose absence gets candidates filtered out.*

## How this goes wrong: failure modes and false positives

Most failures here are false positives: the call feels ready and fails a specific check. This section is the most valuable part of the standard, because a floor that cannot catch a false positive is not a floor. Grade against each check below.

### Company research done, but disconnected

The trap is memorising trivia you cannot connect to the role. Failing company-specific questions reads as uninterested or unprepared, and candidates who are not reasonably familiar with the company are told they do not deserve to progress. The check: can you state three talking points, each tied to a line in the posting? If your facts float free of the role, the research fails even though it happened.

### Story bank full but silent

A bank that looks complete on paper but has never been spoken is a false positive. Silent review hides awkward phrasing that only surfaces when you talk. The check: were the stories spoken aloud at least once? If not, they do not count.

### Questions exist but are Googleable

Three questions on the page is not the bar; three questions that could be asked of any company is a fail. Questions must be nuanced and well-researched, and you should never ask for information easily found online. The check: could any of your questions be answered by a quick web search? If yes, replace it.

> **Watch out:** Generic questions read as no questions
>
> Having no questions prepared is a named deal breaker, and three interchangeable questions signal the same disinterest. Tie at least one question to something specific about this company or this interviewer.

### Same prep reused across companies

Reusing the story bank is correct. Reusing the company research and questions is not. The check: does a separate document exist per company? Prepare for each interview separately at the company level even while sharing stories.

### Panel treated like a screen

One question prepared for a five-person panel is a false positive that a screen-level grade would pass. The check: for a panel, is there a distinct question per interviewer? A panel is a scorecard decision on stakeholder fit and needs breadth a screen does not.

### Over-investing in one call

This is the failure the whole standard exists to prevent. The check: did any single interview exceed its time box? If one call ate the hours the other four needed, you failed the pipeline even if that one call was excellent. The 60% who prep four hours or less are the realistic baseline; treat any call that blows past its budget as a defect.

### Stories not quantified

A story without a number is weaker than it feels in your head. The check: does each story quantify its result, in the shape of "increased sales by 20%"? If a story has no figure, it needs one before it counts.

## Verify before you walk in

Run this checklist in the last fifteen minutes before each call. If any item fails, the call does not clear the floor, and you either fix the item or accept the gap knowingly rather than by accident.

#### Ready-to-walk-in checklist

- [ ] One document exists for this specific company
- [ ] The stage is labelled screen, hiring-manager, or panel
- [ ] Three to five talking points each tie to a line in the posting
- [ ] Stories are quantified with a number in each result
- [ ] The story bank meets the stage bar: 3 for a screen, 6 to 8 for a panel
- [ ] Every story has been spoken aloud at least once
- [ ] At least three questions are written and none is Googleable
- [ ] A panel has a distinct question per interviewer
- [ ] Each named interviewer is checked with one connection point noted
- [ ] Link or location, time zone, and resume copies are confirmed
- [ ] No single call exceeded its time box against the pipeline

## Keeping the standard current as the pipeline grows

Re-check two things as your search runs, because both move under you. First, the number of rounds: interviews per hire are up 33% since 2021, traditional loops of two to four rounds now sometimes reach eight to ten, and iHire's survey found 20% of job seekers reported silence after a first interview. More rounds mean the story bank pays off more, because you reuse it further. Second, the stage mix: a week heavy on recruiter screens needs far less per call than a week of final panels, so re-grade the budget whenever the mix shifts.

Where you look for help matters too, and supply is uneven. In Refolk's index there are 131,369 recruiter and talent-acquisition profiles in the US against 9,225 in the UK, and 4,719 career or interview coaches in the US against 707 in the UK. Derived from those counts, the UK has one coach for every 13 recruiters while the US has one for every 28, so US candidates facing recruiter-led screens have proportionally less coaching supply to draw on and are more on their own.

| Segment | US count | UK count | US:UK ratio |
| --- | --- | --- | --- |
| Recruiters / TA | 131,369 | 9,225 | 14.2x |
| Career / interview coaches | 4,719 | 707 | 6.7x |
| Recruiters per coach | 27.8 | 13.0 | - |

If you want to see the people running your first-round screens before you walk in, so your interviewer look-up produces a real connection point rather than a name, Refolk turns that from a manual dig into a single query.

Ask me this: `Recruiters and talent acquisition specialists at mid-size software companies in London who run first-round screens.` - [run the search](https://www.refolk.ai/start?q=Recruiters%20and%20talent%20acquisition%20specialists%20at%20mid-size%20software%20companies%20in%20London%20who%20run%20first-round%20screens.).

*Returns named recruiters with backgrounds you can scan for a genuine connection point ahead of a screen.*

The point of a floor is not to prep less for the sake of it. It is to make sure every call in a crowded week clears the same bar, so you never walk into one underprepared because another one ran long. Grade each call, fix what fails, and spend the hours you save on the round that actually decides the offer.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/thin-prep-interview-standard*