How long should company research actually take?

Thirty to forty-five minutes is the useful range. Below that you arrive with the about page, which every other candidate also has; well above it you are refining detail that will not come up. The target is three specific things you can reference naturally, not coverage.

Which sources are worth the time and which are not?

Recent leadership talks, recent product or engineering posts, and employee reviews read for repeated themes. The about page and generic press releases are the ones to skip — they are written to be uninformative, and quoting them signals you did the minimum. One background-watched talk usually yields more usable material than an hour of skimming.

What do I do with what I find?

Turn it into questions rather than statements. Reciting a fact about the company proves you read something; asking a question that could only come from having read it starts a conversation, and the conversation is what people remember. Two or three such questions is plenty.

How do I research a company that has almost no public footprint?

Go to people instead of pages. A small or private company may have nothing published, and in that case one conversation with a current or former employee is the entire research. Failing that, read the job advert extremely closely — a small company's advert is usually written by the person you will work for, and it says a great deal about what they want.

What red flags are worth noticing during research?

Heavy turnover at director level and above, the same complaint repeating across two years of reviews, and public statements that contradict what you are told in the process. None of these is disqualifying alone. What makes them worth noting is that they give you something specific and polite to ask about, and the quality of the answer is the real signal.

Should I mention that I did the research?

No — demonstrate it and let them notice. "I read your engineering post on the payments migration, and I wondered…" does the work; "I did a lot of research on your company" does not. The reference is the evidence, and pointing at it weakens it.

content:contentPage.section.resource

Company research

How to research a company before an interview — where to look, what to ask, and the red flags worth noticing.

Last reviewed: 19 August 2026
Length: About 5 minutes
Scope: Maintained, not published. Corrections welcome.

Company preparation is the 30–45 minutes of focused research that separates strong interviews from generic ones. The goal is three specific things you can reference in the conversation, not a memorized about-page summary. Generic research is invisible; specific research is memorable. Most candidates skip company prep entirely or spend the time on the wrong sources (the about page, generic press releases). The right sources: recent leadership talks, recent product launches, employee review patterns over 6+ months, and the company's own engineering / product blog.

Who this is for

Where it applies.

Pre-interview research the night before

30–45 minutes spent surfacing 3 specific things to reference. Saves hours of generic skimming and produces concrete material for "why this company?" answers and your own questions.

Validating cultural fit before accepting an offer

After offers come in, deeper company prep helps you decide. Read 6+ months of employee reviews; talk to one current and one former employee. Specifics surface; the offer's real shape becomes legible.

Comparing two competitive offers

Same research depth on both companies surfaces different signals. The "research output" for each becomes input to your offer-comparison framework — culture, leadership, product trajectory, growth path.

Researching to decide, not only to impress

The same forty-five minutes serves a second purpose most people waste. You are also deciding whether to work there, and the research is the only part of the process where you can look at the company without anyone performing for you. Write down what would worry you as well as what impressed you, before the interview makes you want the job.

In order

How it works.

Read public values + recent press in 10 minutes
Values give you the framing they use; recent press tells you what is actually happening (launches, funding, leadership changes). Both inform conversation specifics.
Check leadership tenure and recent moves
High turnover at director / VP level is a signal. Three of five VPs joining in the last 12 months is worth probing in the interview.
Read 6+ months of employee reviews for patterns
Patterns repeating across 5+ reviews are signal; single complaints are noise. Note both positive and negative themes.
Watch one recent leadership talk or interview
30 minutes in the background while doing dishes. Surfaces specific quotable moments without feeling like research. Reference one specific thing in the interview.
Skim 2–3 recent blog posts matching the role
For engineering: engineering blog. For PM: product launches. For design: design system or case studies. Pick the post that matches your role; quote one specific thing.

Worked

Worked illustrations.

Constructed to show the shape of the decision, not reported cases. The figures are illustrative.

A candidate doing 40 minutes of company prep

Surfaces a recent funding round, a CTO talk on payments architecture, and a repeated employee theme about strong cross-team collaboration. References all three across the interview; interviewer flags as "clearly did the work" in feedback.

A candidate spotting a red flag during prep

Sees 3 of 5 VPs joined in the last 6 months. Probes politely in the interview; honest answer surfaces ongoing reorg. Candidate withdraws politely before investing more time.

A candidate whose research changed the questions rather than the answers

Forty minutes surfaced a recent reorganisation mentioned nowhere in the advert. They asked how the team's remit had changed since, got a candid answer about a scope that was still being settled, and accepted the offer knowing what they were joining rather than discovering it in month two.

Asked often

Questions people bring here.

How long should company research actually take?: Thirty to forty-five minutes is the useful range. Below that you arrive with the about page, which every other candidate also has; well above it you are refining detail that will not come up. The target is three specific things you can reference naturally, not coverage.
Which sources are worth the time and which are not?: Recent leadership talks, recent product or engineering posts, and employee reviews read for repeated themes. The about page and generic press releases are the ones to skip — they are written to be uninformative, and quoting them signals you did the minimum. One background-watched talk usually yields more usable material than an hour of skimming.
What do I do with what I find?: Turn it into questions rather than statements. Reciting a fact about the company proves you read something; asking a question that could only come from having read it starts a conversation, and the conversation is what people remember. Two or three such questions is plenty.
How do I research a company that has almost no public footprint?: Go to people instead of pages. A small or private company may have nothing published, and in that case one conversation with a current or former employee is the entire research. Failing that, read the job advert extremely closely — a small company's advert is usually written by the person you will work for, and it says a great deal about what they want.
What red flags are worth noticing during research?: Heavy turnover at director level and above, the same complaint repeating across two years of reviews, and public statements that contradict what you are told in the process. None of these is disqualifying alone. What makes them worth noting is that they give you something specific and polite to ask about, and the quality of the answer is the real signal.
Should I mention that I did the research?: No — demonstrate it and let them notice. "I read your engineering post on the payments migration, and I wondered…" does the work; "I did a lot of research on your company" does not. The reference is the evidence, and pointing at it weakens it.

Worth knowing

Small things that help.

30–45 minutes is the sweet spot. Less leaves you generic; more produces diminishing returns.
Three specific things to reference — not ten. Density beats coverage.
Single review complaints are noise; patterns across 5+ reviews are signal.
Watch one leadership talk in the background; produces quotable moments without feeling like work.
JD-grounded questions land better than generic ones — research feeds questions.
Turn what you find into questions, not statements — a question that could only come from having read something starts a conversation; a recited fact ends one.
Write down what worried you as well as what impressed you, before the interview makes you want the job.

ClearHire Editorial

Written to be corrected. If something here is wrong, say so and it changes.