How to Research a Company Before Interview: 45-Minute Plan

You need four things about an employer: what they sell, what changed recently, who they compete with, and who you would work with. You can learn all four in about 45 minutes and write them on one page. This guide shows you how to research a company before interview without spending all night on it. Depth on those four beats a shallow sweep of twenty facts, because an interviewer notices specific, current knowledge, not encyclopaedic recall. You get a timed checklist, a one-page brief template, and three spoken outputs you can rehearse before you walk in.

What do you actually need to know about an employer?

Four boxes, no more. What they sell. What changed in the last six to twelve months. Who else the customer could choose. Who you would work with and what problem the role solves.

Why four? Because each one feeds something you say. The product box lets you talk about their world instead of yours. The news box gives you a question to ask. The competitor box lets you answer "why us?" without flattery. The team box lets you connect your experience to their actual problem.

A candidate who recites twenty facts sounds like they read a website. A candidate who explains one recent change and asks a sharp question about it sounds like someone who already cares about the work. Interviewers are listening for that second person.

Here is the one-page brief. Write these headings on a sheet of paper or a blank document and fill them in as you go.

Product: one plain sentence.
Recent news: one item, dated.
Competitors: two or three names, plus one way this company positions against them.
Team and role: the team name, the reporting line, the problem the role exists to solve.
Questions to ask: one line, written last.

The 45-minute research checklist, step by step

Set a timer for each block. The timer is the point: it stops research from becoming an all-night scroll.

Ten minutes on the product. Use the company site and its product or services pages. Write what they sell in your own words, not their tagline.
Ten minutes on recent news. Use the company's news or announcements page, their blog, or press coverage you find from their own site. Write one item and its rough date.
Ten minutes on competitors. Use competitor sites and the company's own comparison or positioning pages. Write two or three names and one contrast.
Ten minutes on the team and role. Use the job description and the careers page. Write the team name, the reporting line, and the problem the role solves.
Five minutes to write the brief. Fill the four boxes and the questions line on one page.

Stopping rule: when a box has two or three facts you can explain in your own words, move on. You are not writing a report. You are preparing to talk.

Box 1 — Product: can you explain what they sell in one sentence?

Find the core product first. Company sites often bury it under side offerings, partner tools and add-ons. Ask yourself: what does the customer pay for, and what problem does it remove?

Then write it plainly, without marketing language.

Weak: "They're a SaaS platform for enterprise solutions."

Stronger: "They make software that lets a company's support team answer customer emails from one shared inbox, so nothing gets answered twice."

The second version is longer but a friend would understand it. That is the test. If you can say it simply, you can answer follow-ups about who their customer is and why someone picks them. If you can only repeat their tagline, the first follow-up question will expose it.

Box 2 — Recent news: what changed in the last six to twelve months?

Useful news is a launch, a funding round, a leadership change, an expansion into a new market, or a public setback. All five give you something to ask about, because each one changes what the team is working on.

Turn one item into a question rather than a statement. For example, if the company announced a new product line, you could ask:

"I saw you launched the self-service tier a few months ago. Does that change how the support team splits its time between new customers and existing ones?"

That question works because it is specific, current and about their work rather than your curiosity.

Honesty rule: if you only half-understand a news item, ask about it rather than assert it. "I read something about a funding round but I wasn't sure what it was for — can you tell me?" is a stronger move than confidently getting the details wrong.

Box 3 — Competitors: who else could the customer choose?

Name two or three competitors and one way this company positions itself against them. A short comparison note is enough:

Competitor A is known for being cheap and simple.
Competitor B is known for large-company integrations.
This company emphasises speed of setup and support.

This box feeds "why us?" without flattery. Instead of "you're the market leader and I love your culture," you can say: "You seem to win on setup speed rather than integrations, and that fits how I like to work with customers — getting them to value quickly." That is a reason, not a compliment.

Box 4 — The team and the role: who will you actually work with?

Read the job description for three things: the team name, the reporting line, and the problem the role exists to solve. Those three sentences are usually in there, even when the rest is generic.

If the interviewer's name and role were shared with you, note one relevant thing about their work or team. Keep it light. You are looking for a connection, not a dossier.

Here is a sample talking point that links your experience to the team's stated problem:

"The description mentions the team is rebuilding its onboarding flow. In my last role I spent most of a year on exactly that — we cut the time to first value by simplifying the setup steps. I'd be glad to talk through what I learned about where people get stuck."

Notice it names their problem, names your experience, and offers a conversation rather than a claim.

What if the company is small, private, or has almost no public information?

Small and private companies often have thin public footprints, and that is normal. Look in four places before you give up: the job description itself, the founders' public writing or talks, customer reviews, and how the company describes itself on its careers page.

The job description is often the richest source. It tells you what the team is building, who they serve and what they are worried about.

If public information was genuinely limited, say so honestly:

"I'll be honest — there wasn't much public information about the company, so most of what I know comes from the job description. It sounds like the team is small and close to customers, which is part of why I applied. I'd like to understand what a typical week looks like."

That is stronger than pretending to know. It shows you did the work, states the limit, and turns the gap into a good question.

Turning your brief into three things you can say out loud

Your one-page brief is raw material. Convert it into three spoken outputs:

One question to ask. Take it from the news box or the team box.
One talking point. Link your experience to their situation, as in the sample above.
One honest gap to name. Something you have not done yet, said plainly and without apology.

Then rehearse. Say each one aloud, not in your head. Follow each with a likely follow-up question and answer that too, so it does not sound recited. For delivery practice, see our Sound Natural With Talking Points Interview Guide.

The four most common research mistakes

Reciting facts instead of connecting them to the role. Fix: after each fact, add one sentence on what it means for the job. In the interview, that sounds like "which is why the role's focus on onboarding makes sense to me."
Relying on outdated news. Fix: check the date on anything you plan to mention. If it is older than a year, treat it as background, not a talking point.
Researching the interviewer personally instead of their work. Fix: stick to their role, their team and anything they have published professionally. Personal details are not your business and can make the conversation awkward.
Claiming knowledge you do not have. Fix: say "I wasn't sure about that" and ask. Interviewers usually respect the honesty more than the pretence.

Before you walk in

One page, three spoken outputs, one honest gap. That is a complete brief, and it is enough. Read your questions line aloud once before you go in, then put the page away. If you want a second opinion on how your talking points sound, our AI Interview assistant guide to preparing honestly and our Communication Interview Questions: Honest, Clear Answers are good next reads.

Frequently asked questions

How long should company research take if the interview is tomorrow?

Forty-five minutes is enough. Spend ten minutes each on the product, recent news, competitors and the team, then five minutes writing a one-page brief. If you only have twenty minutes, do the product and the team boxes first, since those come up in almost every interview, and skip the competitor comparison.

Should I mention something I read about the company in the interview, or wait to be asked?

Bring it up yourself, briefly, when it fits the conversation. One specific reference tied to the role is more useful than a list of facts. The natural places are when they ask why you applied, when you ask your question at the end, and when you connect your experience to a problem they have described.

What should I do if the company's website and job description contradict each other?

Treat the job description as the more current and specific document, then ask about the difference. Something like "The website describes the product one way and the role another — which is closer to where the team is heading?" is a good question and shows you read both carefully.

Is it worth researching the interviewer on professional networks?

Yes, but narrowly. Look at their role, their team and anything they have written or spoken about professionally. Skip personal details. One relevant, work-related observation is plenty, and mentioning it lightly is better than showing you have read everything they ever posted.

How do I research a company for a second interview differently from the first?

Go deeper on the team and the work. By the second round you usually know the product, so spend the time on the specific problem the role solves, who you would collaborate with, and what has changed since you last spoke. Bring a sharper question and a clearer view of how you would approach the first ninety days.

Rehearse your three spoken outputs out loud with the AI Interview assistant.