How to Research a Company Before an Interview

Research should help you have a conversation

The point of company research is not to memorize the founding year. It is to understand what the organization does, what the job likely involves, and which of your real examples will matter. Interviewers notice when you can talk about the work. They also notice when you recite the About page.

You will not learn everything from public pages. That is fine. Good research produces a short list of facts, a few open questions, and one or two stories from your own work that match the posting. It should not produce a fake insider persona.

Start with the job posting, then the company site

Read the posting twice. First, list must-have tasks and tools. Second, highlight phrases that repeat. Those phrases tell you what the team wants to hear about — if you have done similar work. How to match resume keywords without stuffing uses the same discipline on paper. In an interview, you will speak those ideas instead of pasting them.

Then open the company’s own site. Read the homepage, the product or services page, and the careers or team page if they exist. Write down, in your words: who they serve, what they sell or provide, and where this role sits. If the About page is vague, the posting and any team blog posts may be clearer.

Look at recent public news only enough to avoid surprise. A product launch, a store opening, or a leadership change can be useful context. Skip rumor threads and anonymous complaints you cannot verify. You are preparing for a conversation, not building a case file.

If the company is small, the site may be thin. The posting, the Google Business profile if they have one, and any public LinkedIn company page can still tell you location count, industry, and how they describe themselves. Write down uncertainty as a question: “I could not see how large the local team is — could you describe it?” That is better than guessing a headcount.

What to write down

Keep notes short enough to review on a phone before you join the call.

• One sentence: what the organization does.
• Three tasks from the posting you can discuss with real examples.
• Two questions you cannot answer from the website (schedule, team size, success measures, tools).
• Words they use for customers, products, or processes — only if you will use them honestly.
• Logistics: interviewers’ names, time zone, video link, and anything they asked you to prepare.

Turn research into answers, not a speech

When they ask why you applied, connect one true fact about the company to one true fact about your work. Weak: “I have always admired your innovative culture.” Better: “You support three clinic locations, and I have coordinated schedules across two retail floors. I want to do that kind of coordination in a healthcare setting.” If you have not coordinated two floors, do not say it.

How to Answer “Tell Me About Yourself” in an Interview should still be about your path, with the company appearing in the “why this role” close. STAR Method Interview Answers: How to Structure Real Stories is for behavioral questions. Use company research to choose which story to tell — not to invent a story set inside their office.

If you use the Interview Question Generator, paste the real posting and your real background. Treat the output as practice prompts. If a generated question assumes a tool or industry you do not know, skip it or say you have not used that tool.

Questions that show you did the reading

Ask about things the website cannot tell you. “How does this team measure a good first 90 days?” “What does a busy week look like for this role?” “Which systems does the coordinator actually live in day to day?” “How do you hand off work when someone is out?” Those questions are useful in almost any operations, support, or coordination job.

Avoid questions whose answers are in the posting you already claimed to read. Avoid asking about salary in the first five minutes unless they open that topic. Avoid asking the interviewer to defend a negative news story you found. If something public concerns you, you can ask a neutral process question later, after you have rapport.

Good and weak prep

Weak: printing twenty pages and reading quotes. Weak: claiming you use their internal tool because the careers page mentioned it. Weak: telling them their strategy is wrong. Weak: researching employees’ social photos.

Better: a half-page of notes, two stories, and three questions. Better: knowing their product category even if you are not a customer. Better: admitting what you could not find. “I saw that you opened a second location last year. I would like to hear how scheduling changed after that” is honest and specific if the opening is public.

Checklist the night before

If you cannot finish a deep dive, finish this list.

• You can say what the company does in one breath.
• You mapped three posting requirements to work you actually did.
• You have two questions that are not answered on the homepage.
• You know the interview format and the names you were given.
• You did not add research “facts” you are unsure about.

Common mistakes

Confusing the parent brand with the local team. Over-indexing on culture-page adjectives. Preparing only questions and no stories. Using AI to summarize the company and then repeating a generic paragraph that could fit any employer. If a summary adds claims you did not see on a primary page, drop those claims.

How to prepare for behavioral interviews without scripting a fake story pairs with this guide: research chooses the prompt, your real work supplies the answer. How to Write a Follow-Up Email After a Job Interview is the short note after the meeting — mention one thing you discussed, not a new research report.