How to Research a Company Before an Interview

“Do your research before the interview” is advice everyone hears and few people turn into an actual plan. Vaguely browsing a homepage the morning of isn't research, and neither is memorizing the “About” page well enough to recite it back. Here's an actual process: where to look, what's worth pulling out of it, and how to use it in your answers without it sounding rehearsed.

Where to actually look

The job posting itself, reread closely

Most candidates read a posting once to decide whether to apply, then never look at it again before the interview. Reread it the day before: the specific language it uses for the team's priorities, the “nice to have” qualifications, and whatever it says about the role's actual day to day, are the closest thing you have to the interviewer's own framing of what matters.

The company's own site, past the homepage

The homepage is marketing copy, the useful pages are usually one click deeper: a product or pricing page (what they actually sell and to whom), an engineering or careers blog if one exists, and a leadership or about page for names you might hear in the interview.

Recent news, specifically the last 3 to 6 months

A quick search of the company name plus “news” surfaces funding rounds, leadership changes, layoffs, or a product launch, any of which can genuinely change what a role needs right now versus what the posting was written for months ago. This is also where you catch a real reason to ask a sharp question instead of a generic one.

Reviews and outside perspective

Glassdoor or similar review sites are worth a skim, weighted carefully, since the people most motivated to leave a review are often the most frustrated ones, not a representative sample. Read for patterns that repeat across many reviews, not any single dramatic one.

The interviewer, if you know who it is

A name in the calendar invite is worth a minute on LinkedIn, not to mention anything personal, but to understand their role and how long they've been there, which tells you what they likely care about asking.

What's actually worth pulling out of all that

• What the company actually does and who its customers are, in your own words, not their tagline
• One specific, recent thing (a launch, a milestone, a change in direction) you could reference naturally
• What the role seems to actually need right now, based on the posting's specific language
• One genuine question that couldn't be answered by their homepage alone

That's a short list on purpose. Trying to hold ten facts in your head produces exactly the recited, rehearsed answer you're trying to avoid.

Using it without sounding like a fact sheet

The difference between research that helps and research that sounds like homework is whether it connects back to you. “I saw you launched X last quarter” is a fact. “I saw you launched X last quarter, and that's actually the kind of problem I worked on at my last role, scaling a feature after a similar launch spike” connects the fact to something real about you. The first sounds like you searched the news, the second sounds like you thought about the role. Our full breakdown of common interview questions and how to answer them covers exactly this pattern for “why do you want to work here,” the single question where a lack of research is most obvious.

Turning research into a sharper resume too

The same reread of the posting that prepares you for the interview is the raw material for tailoring your resume before you even get to that stage, matching its language and priorities is the entire process covered in how to tailor your resume to a job posting. If you'd rather not do that comparison by hand, the free ATS checker runs it for you and surfaces exactly what the posting emphasizes that your resume doesn't yet.

Try free AI interview prep

FAQ