How to Research a Company Before an Interview

In brief, to research a company before an interview, learn what it does, who it serves, and how the role connects to that work. Grab one current update, then write a few questions the site never answers. Where do you start when the homepage is mostly marketing?

Three things to remember

1. Write notes you can say out loud, not a pile of facts you will blank on.
2. Match each question to a source, then read that page before you repeat a detail.
3. Treat values pages, reviews, and news as signals. They are not proof of daily life on one team.

Keep a one-page brief you can scan before the call

Phone calls eat long notes files. One page holds.

Anything that can change needs the claim, the page title, and the date you read it. Leadership moves, and products get renamed. A news item goes stale. If you can't point to a page, leave that line out of your answer.

Dates matter most on the news line and the culture line. A leadership name with no public remark attached is just a name. Leave it thin, or go find what that person actually said.

Brief field	What to write down
What the company does	A plain-language description
Customers or users	People or organizations served
Products or services	Offerings tied to this role
Business model	How it earns money, or how it is funded
Mission, values, priorities	Stated purpose and current themes
Recent news or projects	Announcements, with dates
Leadership	Names that matter to the role, plus what they have said publicly
Industry and competitors	Context you can verify
Role relevance	Link to a product, customer, or priority
Culture signals	Repeated themes, with source and date
Questions to ask	Two or three gaps

Each line you might actually say on the call needs a short chain: the finding, why it matters to this role, and how you would use it. That chain blocks an About-page recital.

Suppose the posting is a customer-success role at a software company. This is only a template, not a real employer. The site says the product helps clinic managers schedule staff. A recent newsroom note says they are adding a mobile view for those same managers. Your note is not that the company has great technology. They serve clinic managers, the change you can verify is the mobile view, and your story is the time you cut scheduling back-and-forth for a similar user.

You still don't know their roadmap. That gap belongs in a question. It does not belong in a guess you dress up as research.

If a stated priority touches the job, try this shape:

"I noticed your stated focus is [specific priority]. In my work with [relevant experience], I have [relevant capability], and I would like to use that on work tied to [role-related product, customer, or project]."

A question can borrow the same note:

"How would this role support [specific priority] in the first 90 days?"

Stop when the page is full. More facts will not make you sound more prepared.

What to look up, and what it cannot prove

Open the job description first. Circle the responsibilities, the tools, and the customer or user the work serves. That list filters which pages deserve your time.

Hays' employer research guidance pushes you past the homepage toward mission and values, products and proof points, recent news, social and leadership updates, the industry and competitors, and culture signals from people who work there. Use it as a map, not a script.

Thing is, a founding year or a map of offices only shows scale and history. It won't show how your manager runs a week.

Read the product or service pages closest to the vacancy, and name the problem the customer has. Then pick one skill or result from your own work that fits that problem.

Keep the link narrow, since a public page can only suggest where the role sits. It can't show what you will own on day one.

Mission statements are messaging the company chose on purpose. One review, one star rating, one professional-network post, or one news story doesn't describe every team, site, or manager.

A Harvard Faculty of Arts and Sciences career services post, citing an Accountemps survey of more than 1,000 senior managers, reports that 38% named knowing little or nothing about the company as the single most common mistake candidates make. Prepare so you are not in that group. The survey doesn't show that research produces an offer.

For basic facts such as products, size, and leadership, that post points you back to the company's website and LinkedIn page. A summary is a start. The page is the source.

The most useful facts are still plain ones. Know what the organization does, who it serves, what this role supports, which priority or development is current, and which industry conditions actually touch the work. Separate that public message from evidence about the day.

Match the source to the question

Pick the page that can answer your question. A saved link you never open is just clutter.

If you need to learn	Start here	Use it for	Watch out for
What the company provides	Website, newsroom, blog	Products, mission, leadership, announcements	Pages stress selected messages
What changed recently	Company LinkedIn page and recent posts	Launches, hiring themes, public tone	Posts leave out the hard parts
How leaders describe the business	Interviews, podcasts, videos	Repeated strategy language	Prepared remarks skip awkward topics
Industry context	Trade press	Reporting the company did not write	Coverage favors big events
Workplace patterns	Recent employee reviews	Themes on pace, management, or expectations	Check date, sample size, and which team
Formal business context	Annual report or, for many U.S. public companies, a 10-K	How the business describes risks and competition	Many private and non-U.S. employers have no 10-K

Take the clinic-manager template from earlier and run it across that table. The product page tells you what the company provides. The newsroom note is the change you can date. A review theme helps only if the same point shows up more than once, recently, and not in a single office. None of those pages proves how the team runs a week.

Official pages say what the company claims it does, sells, values, and plans. Employee comments help only when the same point shows up more than once, in recent reviews, and not in a single office. Outside articles add context. They can still be incomplete.

Annual reports and securities filings aren't interchangeable. Companies write their own annual reports, and those reports can double as public-relations material. SEC filings, where they apply, follow reporting rules. The FSU Libraries guide draws that distinction.

Neither document tells you whether a team is well run. Read them for interview context only. This isn't investment advice, and a filing isn't a verdict on whether you should join.

TopInterview's checklist suggests a public company's latest 10-K, often under an Investor section or on the SEC site, and Crunchbase for a startup's funding rounds, recent hires, and news. Use those when they exist. A nonprofit, a private firm, or an employer outside the United States may publish a different review, or nothing you can open. That absence is not a red flag by itself.

Confirm you have the right organization before you trust a page, because similar names, old brands, and subsidiaries cause mix-ups. Match the official website, location, and industry. A LinkedIn company page shows profiles that list the employer. It's not a verified staff directory.

If the role sits in a brand owned by a larger parent, read both. Don't mix their news. A product launch at the brand is not the same fact as a parent-company filing.

You can burn a long stretch comparing a competitor list you half-remember from a news sidebar, and it feels productive, it really does, right up until you notice you are just shuffling names you already half knew, because the interviewer will care more about whether you understand this company's customer than whether you named three rivals. Name a rival only if the company or a trade article names it. Otherwise skip the market map.

Let AI sort pages, then check them yourself

AI can speed a first pass through public material. It can also flatten tone or invent a clean fact.

Paste sources you actually opened: the About page, the job description, and one recent news item. Ask for a short read on what the company does, how the role might fit, and what is still unclear. The Harvard career services post describes that order. Sources first. Summary second.

Read the original pages before you say a detail out loud. A cautious line in a release, a limit on a product page, a date in a footer: prompts often skip those.

A model will happily smooth a messy page into a tidy sentence. Your job is to notice what got smoothed away, then put the cautious line back before you say it.

If the site is not in English, check the original-language page before you quote a priority. A translation can shift the meaning.

Here's a useful second pass. Ask for two or three honest sentences in your voice. They should use one specific company fact and connect it to work you have done. The Harvard post frames a similar 30-second draft for "Why do you want to work here?" that way. Delete any number you did not provide. Cut any fact that was not on a pasted page.

Don't ask a model whether the culture is healthy, what the pay will be, or whether you will get the job. Those replies sound sure. They are not checked.

Spend the time you have, not a template hour count

There is no universal hour count. A recruiter screen and a final meeting with the hiring manager don't need the same depth.

If you have about 30 minutes, don't browse. Put the first ten minutes on the job description, the homepage, and the product or service pages tied to the role. Then take one current update from the newsroom, a news search, or the company LinkedIn page. Leave the last ten for one connection to your experience and two questions.

That split is a planning choice, not a study rule.

An hour is enough to add mission language, one leadership bio, a trade-press search, and a scan for review themes that repeat. That hour is still a choice for this interview, not a number copied from someone else's checklist.

A longer evening before a final interview is for comparison. Read the role-related product more closely. Skim a report or filing if one exists. Say your answers out loud, using only sourced details.

If a recruiter is running the first call, a clear picture of the business and the role is usually enough. Save narrower questions about team habits for someone who does the work, if you get that conversation. The first call is about whether you understand the business and the role. Team habits can wait.

A hiring-manager interview can hold one product detail and one example from your work. A panel is different again. Don't tell the same anecdote to every person if a second verified detail is sitting in your brief.

Turns out the cutoff is practical. Stop when you can explain the business in plain language and tie yourself to one piece of it. Another tab rarely helps.

Turn the brief into answers you can actually say

You are showing that you understood the company. You are not delivering a script.

The interviewer can hear a memorized paragraph. They can also hear a person who checked one real thing and stopped.

"What do you know about our company?"

Give a short picture of the product, service, customer, or business model that matters to this job. Add one current priority only if you verified it.

"I understand that [Company] provides [product or service] for [customer or user group]. I also noticed [verified development or stated priority], which matters for this role because [connection]."

Then pause, because a short answer invites a follow-up. A long one won't.

"Why do you want to work here?"

Swap the compliment for one checked detail.

Before: "I want to work here because your company has great values."

After: "I noticed your stated focus is [specific priority]. In my work with [relevant experience], I have [relevant capability], and I would like to apply that to [role-related product, customer, or project]."

The second version names something you checked. It ties that point to work you have done. It doesn't treat a values page as proof of daily life.

Do name a verified priority and your own experience. Don't praise a culture you haven't seen.

"Why this role?"

Move from the company to the work. Pick a responsibility, customer, product, or priority from the job description. Connect it to a skill or result you can describe.

Check the company detail, and check that your example actually fits. Don't hint that you already know the team's internal process, and don't promise a result you can't control.

If the employer is in stealth mode, or the public site is thin, say what you could verify and ask the rest. Guessing an unsourced strategy is worse than a short answer.

Ask what the pages still cannot show

Public pages rarely show how decisions get made, how work moves between people, or what the first 90 days feel like. You'll want one question on the role, one on the team, and one on early success. Skip anything the careers site already answers in plain language.

Questions that tend to land:

• "How would you describe the team's working style?"
• "What do you enjoy most about working here?"
• "How will this role contribute to the work this team owns?"
• "What does success look like in the first 90 days?"

Hays offers the first two as ways to hear an insider's description. Use them as openings. Listen for specifics. A vague slogan is a signal, and you still have to decide with a partial picture, which is awkward, and that discomfort does not mean you researched badly.

Build on a note you checked:

"I saw that the company is focusing on [verified priority]. How would this role support that work?"

Culture research works the same way: look for patterns across recent reviews, ratings, public posts, and what people say in the interview, and notice differences by team, location, and role. Use the pattern to form a question. One comment is not the organization.

When sources clash, walk a short sequence instead of picking a side in the room.

1. If official messaging and outside reporting differ, write the gap down. Ask a current, respectful question only if it would change how you do the role.
2. Conflicting reviews need a second look for recent themes that repeat. One rating is not a fact. Teams differ. You can also notice public profile patterns, such as very short leadership stints or internal moves, without treating them as a score.
3. Negative news that is current and relevant to the work should not be ignored, and it should not become an accusation. Refer to what you actually read. Try: "How is the team approaching [role-relevant change]?"
4. A thin record means you stay with the job description, the official pages you can find, and your questions. Small and private employers often have little to read.

to be honest, this still won't prove culture, stability, or fit.

A last pass the night before

Walk the brief once. If a line has no source and no date, cut it or go find the page.

Say the company description out loud before you check the boxes. If you stumble, the brief is not ready.

• [ ] I can explain, in plain language, what the company does.
• [ ] I can say how the role relates to a product, customer, or priority.
• [ ] I checked at least one current update and wrote the date.
• [ ] I looked at industry context without inventing claims about rivals.
• [ ] I compared an official source with at least one outside or employee-perspective source.
• [ ] I have a short reason for this company and this role, tied to work I have done.
• [ ] I have two or three questions the website does not answer.

The bottom line

Fill the one-page brief with three verified details, one role connection, and two questions. That is enough for a specific conversation. It leaves room to learn from the interviewer. Before the call, read that page out loud and drop any line you cannot source.