Most advice on researching a company is a list of things to look up. Read the About page, check the news, know the mission.
That's fine. It's also the same list every candidate brings, which is why it stops being an advantage the moment everyone follows it.
The better question is the one the listicles skip. What does the person interviewing you actually do with your research, and what gets written down when you get it wrong?
We've mapped the Apple and Google interviews the same way, naming what each interviewer actually scores. Here's that lens pointed at company research. The candidate-side guides, including a solid one from Final Round AI, tell you what to look up. We're telling you what the interviewer is measuring, and where it costs you.
What this actually feeds in the debrief
After an interview, structured hiring teams don't ask "did you like them." They ask interviewers to rate the candidate against pre-defined attributes on a scorecard.
Greenhouse, one of the most widely used hiring platforms, describes the interview scorecard as the framework everyone uses to assess a candidate against attributes the team set before the loop. The point is to replace vibes with evidence.
Company research doesn't usually get its own scorecard line. It shows up in the interviewer's read of two things: how real your interest is, and how much diligence you bring.
Indeed's guidance is blunt about why. It frames the "what do you know about our company" question as a way to confirm you're genuinely interested, and says an answer showing you researched and prepared signals you'd "put the same care and attention to detail into daily tasks."
That last line is the whole game. Your research is read as a sample of how you'd do the job, not graded as trivia.
What recruiters and hiring managers expect
They want different things, and most candidates prepare for neither.
The recruiter screens you first. They're checking that your interest is real and specific before spending a hiring manager's time. "I'm excited about the mission" reads as filler. A concrete reason tied to something you actually saw reads as real. The recruiter also packages you for the rest of the loop, so the specific observation you give them gets passed along as "this one did the homework."
The hiring manager wants to know you understand the role in context. Not the company in the abstract, the role.
Interviewing for a growth job? They want to see you've thought about how the company gets customers. An infrastructure role? They want a sign you grasp the scale problem. Knowing the founding year tells them nothing. Knowing how the company makes money, and what that means for the work, tells them you'd show up oriented.
The five-item checklist, ranked by signal
Not all research counts equally. Ranked by how much it moves an interviewer's read:
- The product, used firsthand. The highest-signal item by far. Sign up, use it, bring one specific observation. Interviewers can tell instantly whether you touched the product or just read the homepage.
- How the company makes money. Who pays, for what, roughly how. Most candidates skip this because it isn't on the About page. It signals commercial awareness, which reads as maturity.
- One recent, specific piece of news. A launch, a funding round, a leadership change. One thing you can actually discuss beats five you can only name. It proves your interest is current.
- The team and your interviewers. A two-minute LinkedIn check tells you what they care about and keeps you from explaining their own job back to them.
- The mission and values, lightly. Worth knowing, near the bottom. Reciting the mission signals nothing. It only matters when you tie it to something concrete you'd contribute, and at that point the concrete thing is doing the work.
The pattern is simple. The high-signal items take effort and can't be faked. The low-signal items are the ones every candidate already has. Spend your time at the top.
Three places that beat the About page
The About page is written for everyone, so leaning on it makes you sound like everyone. Three sources surface better material:
- The pricing page. It tells you who the customer is, how the company makes money, and what it competes on, faster than any mission statement. No public pricing? The "request a demo" flow and case studies do the same job.
- Recent news and the company blog or changelog. This is where you find the specific, current observation. What shipped last month, what they're hiring for, what the CEO wrote.
- Your interviewers' LinkedIn profiles. Knowing who you're talking to lets you tailor your examples and ask sharper questions.
What gets you downgraded
The failure modes are predictable, and good interviewers spot them in minutes.
Generic interest. When your reason for wanting the job would apply to any company, the interviewer notes low real interest. It rarely sinks a strong candidate alone. But in a debrief comparing two similar people, "genuinely interested in us" versus "could've been interviewing anywhere" tips against the second one.
Questions answered on the homepage. This one undercuts everything else, because it directly contradicts the diligence the whole exercise is supposed to show.
Researching the company but not the role. The most overlooked. A candidate who can recite company history but has no view on what the job is for prepared the wrong thing. Interviewers care far more that you understand the problem you'd solve.
One thing that won't hurt you: forgetting a fact. No good interviewer downgrades you for not knowing the exact headcount. Those are lookups, not signal. Don't waste prep memorizing numbers that prove nothing.
Two questions that prove you did the work
You don't demonstrate research by reciting facts. You demonstrate it by asking questions only a prepared person could ask. Two types land every time.
Connect a specific finding to the role. "I saw you launched X last quarter. Would my team own the next phase of that, or is that elsewhere?" This proves you read recent news and you're already placing yourself in the work.
Probe the business behind the role. "It looks like most revenue comes from enterprise customers. Is this role about deepening those accounts or opening a new segment?" This proves you understand how the company makes money.
Neither question is askable without doing the research, which is exactly why they read as proof of it.
A 45-minute prep block you can run
You don't need hours. You need 45 focused minutes on the high-signal items.
- 0 to 15, the product. Sign up or open a demo. Use it. Write down one honest observation, including something you'd improve.
- 15 to 25, the money. Read the pricing page or case studies. Answer in one sentence: who pays, for what, and what they compete on.
- 25 to 35, the news. Find one launch or post from the last few months you can talk about. Note why it matters for the role.
- 35 to 45, the people. Look up your interviewers. Note one thing per person that connects to your background or sharpens a question.
That gives you two or three specific observations and two prepared questions. More than enough, and more than most candidates walk in with.
The throughline is the one the debrief enforces. Interviewers read your research as a sample of how you'd work, not as a recall test. Specific and role-aware reads as genuine interest. Generic reads as someone who'd take any offer.
Want to hear how your research sounds out loud before it counts? Four-Leaf's AI mock interviews let you practice tying it to the role in a real conversation, which is where knowing the facts and sounding interested turn out to be different skills.