How to research a company before an interview

Most candidates research a company by skimming the homepage and calling it done — then freeze when an interviewer asks something a touch more specific. Good company research isn't about how many tabs you opened; it's about finding two or three true, specific things and being ready to use them. Here's a framework that takes about twenty minutes and actually holds up when someone asks a follow-up.

Why this matters more than candidates think

Interviewers use your research as a cheap, reliable signal for how seriously you want the role. It's also the raw material for two of the hardest moments in any interview: answering "why do you want to work here" with something that isn't generic, and asking a question at the end that isn't something you could've typed into a search bar. Skip the research and both moments get noticeably harder, no matter how strong your actual experience is.

There's a second, quieter benefit: research changes how you listen during the interview itself. A candidate who already knows the team shipped a major redesign last quarter notices immediately when an interviewer's answer touches on it, and can follow up in a way that feels like a real conversation instead of a Q&A. A candidate with no context just nods along. Interviewers can tell the difference, even when they can't quite articulate why one conversation felt sharper than another.

The framework: Product, People, Problem

1. Product. What the company actually builds or sells, for whom, and why someone pays for it. Say it in your own words — if you can't, you don't understand it yet, you've just read about it.
2. People. Who you'd likely be working with: the team's shape, anything they've published publicly (blog posts, talks, open-source work, case studies), and — if you know who's interviewing you — what their role actually touches.
3. Problem. What the company, or that specific team, is wrestling with right now: a strategic bet, a public challenge, a recent change in direction. This is the material that turns into real, specific answers instead of rehearsed ones.

You don't need equal depth on all three. One solid, specific fact from each is usually enough to carry an entire interview's worth of research-backed answers.

Where to actually look

Skip the hour of aimless browsing. In order of signal: the company's own blog or changelog (what they're actually building and talking about now), a recent interview or press mention of a founder or leader (what they're emphasizing publicly), the job posting itself re-read slowly for what it repeats or spends extra words on, and — if the product is something you can try — using it yourself for five minutes. Each of these produces something specific; a homepage mostly produces marketing copy you already know not to repeat back.

If you're interviewing with a larger company, narrow your research to the specific team or product line you're joining rather than the company as a whole. A broad fact like "they have millions of users" is true of almost every large company and says nothing about you; a specific fact about the team's own roadmap or a problem they've mentioned publicly is much harder to find, and much more valuable precisely because of that.

A worked example

"I saw in your last product update that you moved the onboarding flow to skip account setup entirely until after someone sees their first result — that's a pretty deliberate bet on activation over completeness, and most teams don't have the stomach for it. I'd be curious whether that's already showing up in retention, or if it's still early days."

That single sentence does the work of an entire "why this company" answer and a sharp closing question at once — because it comes from something true and specific, not a tagline.

Common mistakes to avoid

• Reciting the homepage. Repeating their own marketing language back to them reads as having skimmed, not researched.
• Researching the company but not the role. The job posting itself is full of hints about what they're emphasizing this cycle — most candidates barely reread it.
• Cramming the night before. Rushed research produces generic facts. Twenty focused minutes a few days out beats two scattered hours the night before.
• Treating research as separate from the interview. The point isn't to "know things" — it's to weave what you found into your actual answers and questions.
• Stopping at the company level. Research into the specific team or role almost always produces sharper material than company-wide facts everyone already knows.

The bottom line

Company research isn't about volume — it's about finding a small number of true, specific things and actually using them. Look at what they're building now, who you'd work with, and what they're wrestling with, and you'll walk in with real material instead of recycled talking points. That's also exactly the material that makes your closing questions land instead of falling flat.

Related: The best questions to ask the interviewer · Why do you want to work here?