# The Pre-Interview Company Brief, Built Before Each Loop

*You can build a one-page interview brief in about 90 minutes that yields a specific "why this company" answer, three role-mapped talking points, and three round-appropriate questions.*

- Canonical URL: https://www.refolk.ai/candidates/guides/pre-interview-company-brief
- Pillar: Interviewing
- Format: Playbook
- Published: 2026-08-08
- Last reviewed: 2026-08-08
- Reading time: 16 min

## Key takeaways

- Set a 90-minute cap that sits between the two published budgets - 1 to 2 hours lean and 2 to 4 hours standard - and spend it producing one artifact rather than opening more tabs.
- Investor pages beat review sites for signal per minute: a 10-K or earnings release states strategy and risk in the company's own words, while everything on review sites is self-reported and hard to verify.
- Route questions by round, because a recruiter often cannot answer team-internal questions; focus shifts from company at the screen to team and role at the manager to strategy at the final.
- The final round rewards company research more than skills: with only two to four candidates reaching it, a current, specific fact about strategy is disproportionately decisive at the stage most candidates stop researching.
- Your outreach pool is role-dependent - Refolk's index holds about 5.2x more US software engineers than product managers, so an engineer can almost always find a current employee to ask, while a PM at a small firm leans harder on filings and news.
- A finished brief has one 'why us' line, three talking points each mapped to a named job-description requirement, and three round-appropriate questions, with every field filled before you stop.

You have an interview in a few days and one evening to prepare. This playbook is for candidates who want to research a company well enough to answer "why us," tailor a pitch, and ask sharp questions, without burning a whole night reading. It runs the research as a timed, source-by-source procedure that outputs one reusable one-page brief and ties every finding to a specific interview moment.

Most advice on how to research a company before an interview ends with a pile of unsorted intel: visit the website, check LinkedIn, read the news. That leaves you with more tabs open, not a plan for the room. This guide fixes an output first - one page, three named deliverables - and works backward through the sources that fill it.

## Why a fixed-output brief beats open-ended reading

The brief is the point. Reading is not research; an artifact is. Published sources describe hours of reading but rarely name a finished document, which is why candidates run out of evening with nothing they can carry into the room.

Set the target before you open a single tab. A finished brief has three things: one "why us" line, three talking points each mapped to a named job-description requirement, and three questions sorted by which round they belong to. Everything you read exists to fill one of those fields. If a fact does not map to the "why us" answer, a talking point, or a question, it does not go on the page.

This reframes the time budget. One recruiter survey of over 500 interviewers found that failure to research was the single most common interview mistake, and in a separate survey of 100-plus professionals, 27% spent over four hours preparing for their last interview. The gap between those two facts is where the artifact lives: plenty of candidates spend time and still walk in generic, because time without an output produces atmosphere, not answers.

**27% - Professionals who spent over four hours preparing for their last interview**

From a recruiter survey of 100-plus professionals; time spent is not the same as an artifact produced.

I set a 90-minute cap deliberately. It sits between the two published budgets - one source says an hour or two is all most people need, another recommends two to four hours for a standard role - and it forces the discipline that matters. At 90 minutes you stop and check the page, not the tab count.

## The reliable source stack, and what each one proves

Six public sources, ranked by signal per minute: investor pages and filings first, then the company site, then news, LinkedIn, competitors, and review sites last. Each proves something different, and each lies in a predictable way, so knowing what a source misleads on is as important as knowing what it shows.

Investor pages are the highest-signal source. In 30 to 60 minutes you can skim the investor relations page and reach annual reports, 10-K forms, quarterly results calls, and recent press releases. If there is no home-page link, search "investor relations" plus the company name. A 10-K or earnings release states strategy and risk in the company's own words, which is exactly the raw material for a specific "why us." For public companies, you can cross-check the headline financials against filings at the US Securities and Exchange Commission.

The company site's About, Careers, and product pages give mission, values, leadership, and products. Treat them as marketing, not ground truth: "About Us" and "Meet Our Team" pages are geared toward attracting customers and clients. Use them to learn what the company says about itself, then corroborate with something dated and external.

Review sites go last, and only for culture. Everything on those sites is self-reported, subjective, and hard to verify, and reviews skew toward very happy or very unhappy employees. Look for patterns, never a single verdict.

| Source | What it proves | How it misleads |
|---|---|---|
| Investor page / filings | Strategy, risk, performance in the company's own words | Written for shareholders; dense, may lag current events |
| Company site (About, product) | What they sell, mission, leadership | Marketing, not ground truth |
| Recent news | Direction and momentum in the last 90 days | Old items look current if you do not filter by date |
| LinkedIn (company + people) | Interviewer background, team titles, connection points | Titles are self-set; profiles can be stale |
| Competitors | Market position and what makes this firm distinct | Easy to over-read from one comparison |
| Review sites | Culture patterns | Self-reported, unverifiable, skewed to extremes |

> **Rule:** Anchor the "why us" in a filing or news, not a mission statement
>
> Your "why this company" answer must name something specific to this company that a competitor could not claim, corroborated by one dated external fact - a filing, an earnings release, or news from the last 90 days.

## The 90-minute brief, source by source

Run the sources in a fixed order with a clock on each. The sequence moves from highest-signal, most-objective sources to softer ones, so your foundation is solid before you spend any time on culture reads that can bias you.

#### Build the brief in 90 minutes

1. **Confirm the loop and interviewers (5 min)** - Email the recruiter to ask who you will meet and whether there is a task, technical test, or case study. Done when you have named interviewers and a confirmed round type.
2. **Foundation scan (20 min)** - Read the website About, Careers, and product pages plus one recent news item. Done when you can state what they sell, to whom, and one recent development.
3. **Financial and strategy check (15 min)** - Skim the investor page and the latest annual report or press release; for public firms cross-check filings at the SEC. Done when you have one fact about direction or performance in the company's own words.
4. **People and team (15 min)** - Open the LinkedIn company page and each interviewer profile; note titles and shared background. Done when you have one connection point per interviewer.
5. **Outside view (15 min)** - Scan news from the last 90 days, review-site patterns, and one competitor. Done when you have one strength and one watch-out, each with a source.
6. **Synthesize the brief (15 min)** - Map every finding to one "why us" line, three talking points tied to job-description requirements, and three round-appropriate questions. Done when the page has no empty fields.
7. **Rehearse (5 min)** - Say the "why us" answer aloud once. Done when it runs under 60 seconds with no notes.

That order is a choice worth naming. Some sources start with LinkedIn rather than the website, and others put financials near the end. I front-load the financial check because it is the most decisive and the easiest to skip when you are tired. Foundation-then-deep sequencing keeps you from reading team gossip before you know what the company actually does.

#### The 90-minute brief pipeline

1. **Confirm loop** - Recruiter email surfaces interviewers and any task
2. **Foundation** - Site and one news item establish what and who
3. **Financials** - Investor page and filings give the strategy anchor
4. **People** - Interviewer profiles give connection points
5. **Outside view** - News, reviews, one competitor give balance
6. **Synthesize** - One page: why-us, three talking points, three questions

*Each stage feeds the synthesis; nothing gets read that does not map to a brief field.*

Confirming the interviewers in step one is not a courtesy - it changes what you research. Ask "Who will I be meeting?" and "Is there anything specific I should prepare for?" That single email tells you whether there is a case study to prep and whose LinkedIn to open, so the remaining 85 minutes are spent on the right people.

## Scale the budget to the role level

Ninety minutes is the floor for a standard role, not a universal number. Scale up for senior positions and down for entry-level ones, using the same source order but spending longer on financials and people for senior loops.

The published time budgets vary by source and level. Full interview prep, including practising answers and logistics, averages five to 10 hours; Indeed suggests the first 20% of that goes to company, role, and industry research. The research-only budget below is the part this brief covers.

| Role level | Recommended research hours |
|---|---|
| Entry / graduate | 1 - 2 |
| Standard | 2 - 4 |
| Senior | 4 - 6 |

These figures come from a single recruiter source; another source gives a flat one to two hours regardless of level, so treat the table as a directional guide, not a rule. For a senior loop, spend the extra time on filings, on the interviewer profiles of the executives you will meet, and on a second competitor. For entry-level, the 90-minute brief may be the whole budget, and that is fine.

> **Note:** The 90-minute number is a defensible middle, not a law
>
> It sits between the lean one-to-two-hour view and the standard two-to-four-hour view. The value is the artifact, not the minute count; if you finish the page in 70 minutes, stop.

## Turn findings into a "why us" answer that names this company

A strong "why this company" answer follows the "3 Whys": why this company, why this position, why me. The most common failure is an answer that is really "why I want a job," which reads as low interest to the hiring side.

Content discipline decides whether the answer lands. Do not lead with salary, benefits, vacation, commute, or personal circumstances. Instead, explain why the company fits your career goals, why the role interests you, and how your skills contribute to their objectives. Robert Half offers a useful private reframe: flip the question to "why would this company want to hire me?" and focus on the impact you could make. You say the "why us," but you build it around what you offer.

The test for a good answer is falsifiable: it names something specific to this company that no competitor could claim. "You are an industry leader" fails - any leader's competitor could hear that. "Your last earnings call flagged expansion into X, and I have shipped exactly that at Y" passes, because it is true only of this company.

**The "why us" one-liner (synthesize from your financial check)**

```
"I want to work here because [specific, current company direction from a filing or the last 90 days of news] - and that lines up with [named thing I have done or want to do next]. That's the work I want to be doing, and I think I can move it forward."
```

*Fill the two brackets from your strategy anchor and your own evidence, then cut it to under 60 seconds spoken.*

> A "why us" answer that any competitor could also hear is not an answer, it is a compliment.

## Route questions and talking points by interview round

Focus shifts by round, and so should your questions and talking points: company at the recruiter screen, team and role at the hiring manager, strategy at the final. Asking a deep team question of a recruiter wastes your best material, because recruiters often lack team-internal context.

The recruiter screen is typically a 30-minute phone conversation to determine how well your background fits the opening. Ask about company basics, process, timeline, and logistics. The hiring manager round comes after the screen, at the point where your skills have already attracted the manager and they want to see how you would fit their team - bring three to five prepared questions about the team, the role, and the problems being solved. Panel rounds mix the hiring team with people you will work alongside, checking skills plus team fit.

Final rounds are different in kind. They are typically led by VPs, department heads, or the CEO, and they focus on judgment, leadership, cultural alignment, and long-term impact rather than technical skills. Research the stakeholders who will be in the room, because they control budgets and set strategic direction. This is exactly where company research pays off most and where most candidates stop.

#### Why final-round research pays off most

| Stage | Figure | Note |
| --- | --- | --- |
| Applications | many | research effort per candidate is low |
| Recruiter screen | fewer | 30-minute background fit check |
| Final round | 2 to 4 | executives judge fit over skills |

*With only two to four candidates reaching the final, a current strategy fact is disproportionately decisive at the stage most candidates stop researching.*

| Round | Research focus | Question to ask back |
|---|---|---|
| Recruiter screen | Company basics, process, logistics | "What does the rest of the loop look like?" |
| Hiring manager | Team, role, problems being solved | "What is the hardest problem this role owns in the first quarter?" |
| Panel | Team fit, cross-functional work | "How does this role work with the teams around it?" |
| Final | Strategy, direction, priorities | "Where is the team headed over the next year, and how does this role move that?" |

Each of your three talking points must map to a named job-description requirement plus your evidence. A broad statement without an example fails. If the posting asks for experience scaling a service and you have it, the talking point is not "I am experienced" - it is the named requirement, the thing you did, and the outcome.

## Find a current employee to ask, when the pool exists

If a current or former employee will talk to you, that beats every public source for team-internal context. Whether that is available depends on the role and the company, and it is a quantifiable question, not a hope.

In Refolk's index of professional profiles, some roles are far more common than others, which sets your odds of finding someone to ask. There are about 5.2 times as many US software engineers indexed as product managers, so an engineer can almost always locate a current employee for a 15-minute informational chat, while a PM candidate targeting a small firm may find no one and must lean harder on filings and news.

| Target title | Indexed US profiles | Ratio to Product Manager |
|---|---|---|
| Software Engineer | 348,395 | 5.2x |
| Product Manager | 66,440 | 1.0x |

Counts are from Refolk's index; the ratio is derived from those counts. The practical read: before you assume you can get an informational chat, check whether the pool exists for your role at your target's size.

Ask me this: `Current software engineers at Figma in the San Francisco Bay Area I could ask for a 15-minute informational chat.` - [run the search](https://www.refolk.ai/start?q=Current%20software%20engineers%20at%20Figma%20in%20the%20San%20Francisco%20Bay%20Area%20I%20could%20ask%20for%20a%2015-minute%20informational%20chat.).

*Returns named current employees you could approach for team-internal context that no public source gives.*

The same index shows who tends to run your screen. In Refolk's index, there are 109,713 profiles with recruiter titles in the United States against 6,978 in the United Kingdom - the US pool is about 15.7 times the UK pool. If you are interviewing in a smaller market, expect fewer intermediaries and more direct contact with the hiring team, which changes who you route your questions to.

| Country | Indexed recruiter profiles | Share of the two-market total |
|---|---|---|
| United States | 109,713 | 94% |
| United Kingdom | 6,978 | 6% |

If you want the research done faster than an evening allows, [Refolk](/candidates) writes your resume from your own history and tailors it to each posting, which frees the evening for the brief itself rather than the paperwork around it.

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

The brief fails in predictable ways. Each failure has a tell and a check you can run before you walk in.

**Mistaking marketing for fact.** About and Team pages are customer-facing. The false positive is reciting the mission verbatim as your "why us." Check: can you cite one dated, external fact - news or a filing - that corroborates it? If not, it is a slogan.

**Over-weighting one bad review.** Reviews skew to extremes. The false positive is walking in convinced the culture is toxic from a single post. Check: require a repeated pattern across multiple reviews before treating it as signal.

**Asking the wrong person the wrong question.** A recruiter often cannot answer team internals and rarely knows the problems the team is solving. The false positive is spending your screen questions on team problems and getting vague answers. Check: route strategy and problem questions to the hiring manager or panel.

**A "why us" that is really "why me a job."** Leading with salary or perks reads as low interest. Check: does your answer name something specific to this company that no competitor could claim?

**Generic talking points.** Broad statements without examples fail. Check: each talking point maps to a named job-description requirement plus your evidence.

**Stale intel.** Using old figures for a company that just merged or had layoffs is a visible miss. Check: filter news to the last 90 days and verify headline financials against filings.

**Blowing the time budget.** Endless reading with no artifact. Check: at 90 minutes you must have a filled one-page brief, not more open tabs.

> **Watch out:** The most common interview mistake is failing to research
>
> In one survey of over 500 interviewers, failure to research was the single most cited mistake. A brief with empty fields is the same failure wearing a document; fill every field or the artifact is doing no work.

## Verify the brief before you close the laptop

Run this check before you call the research done. Every item is a pass-or-fail statement, not a topic, and a "no" tells you exactly which source to reopen.

#### Brief-complete check

- [ ] I can name the interviewers and the round type from the recruiter's reply.
- [ ] I can state what the company sells and to whom in one sentence.
- [ ] I have one strategy or performance fact in the company's own words from a filing or investor page.
- [ ] My "why us" line names something specific to this company and runs under 60 seconds spoken.
- [ ] I have three talking points, each mapped to a named job-description requirement plus my evidence.
- [ ] I have three questions sorted by round: company for the screen, team for the manager, strategy for the final.
- [ ] Every news item I am relying on is from the last 90 days.
- [ ] Every culture claim rests on a repeated pattern, not a single review.

## Keep the brief current between the screen and the final

The brief is not a one-time document; it is a living page you revisit before each round of the same loop. After the screen, add what you learned about the process and the team so your hiring-manager questions get sharper. Before the final, run a fresh 15-minute news and filings pass, because a company that merged or announced layoffs since your first pass will make your old figures a visible miss.

The mechanism to stay current is simple: re-filter news to the last 90 days and re-check headline financials against filings each time you advance a round. If you reach the final - where only two to four candidates land and executives judge fit over ability - one current, specific fact about strategy is worth more than any polished skill answer. Keep the page open, keep it dated, and let each round add one row.

## Frequently asked questions

### How long should I spend researching a company before an interview?

Match the effort to the level. One recruiter source recommends 1 to 2 hours for graduate or entry roles, 2 to 4 hours for standard roles, and 4 to 6 hours for senior positions, while a leaner view says an hour or two is enough. This guide sets a 90-minute cap that sits between those budgets, because the differentiator is not time spent but producing a finished one-page brief rather than more open tabs.

### What is the best structure for a 'why do you want to work here' answer?

Use the most-cited framework, the '3 Whys': why this company, why this position, why me. Lead with something specific to this company that no competitor could claim, drawn from a filing or recent news, not a mission statement recited verbatim. Do not lead with salary, benefits, vacation, or commute, which reads as low interest. Robert Half's flip is useful: quietly answer why this company would want to hire you and focus on the impact you could make.

### What should I research before a job interview if I only have one evening?

Run the six-source procedure in order and stop at 90 minutes: confirm the loop and interviewers, a 20-minute foundation scan of the site and one news item, a 15-minute financial and strategy check on the investor page, 15 minutes on interviewer and team profiles, 15 minutes on news, review patterns, and one competitor, then 15 minutes to synthesize the brief. Anchor your 'why us' in a filing or press release, not a review site.

### What questions should I ask at each interview round?

Route questions to the person who can answer them. At the recruiter screen, ask about company basics, process, and logistics. At the hiring manager, bring three to five questions about the team, the role, and the problems being solved. At the final round, ask about strategy and direction, since it is led by VPs, department heads, or the CEO. Asking deep team questions in the screen wastes your best material, because recruiters often lack team-internal context.

### Are employee review sites reliable for judging company culture?

Use them only for patterns, never for a single verdict. Everything on these sites is self-reported, subjective, and hard to verify, and reviews skew toward very happy or very unhappy employees. Require a repeated pattern across multiple reviews before you treat something as signal, and never walk in convinced from one post. Anchor your 'why us' in filings and news instead; reserve reviews for culture caveats only.

---

*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/pre-interview-company-brief*