Most candidates walk into interviews unprepared. Not because they’re lazy, but because nobody ever showed them how to research a company before an interview.
Short version: to research a company before an interview, you need 15 minutes and five blocks – the latest news (3 min), the interviewer’s LinkedIn (4 min), the job description (3 min), what they’re saying publicly (2 min), and two or three questions built from all of it (3 min). That’s enough to sound like you already belong there.
I’ve hired for tech teams for two decades and coached mid-career candidates into them for the last five. The candidates who sounded generic almost never lacked skill. Instead, they spent three hours on the company’s About page and zero minutes on what the person across the table cares about. The research was real, but it pointed at the wrong target.
Why 15 minutes beats three hours
Here’s the thing: the interviewer isn’t grading your research. They’re deciding whether you understand their problem and whether you’d need six months to figure the place out. Research only helps if it changes what you say in the room.
So the goal isn’t a briefing document. It’s three things you can use out loud: one specific thing you know about the company, one thing you noticed about the interviewer, and two questions that prove you did both. Anything past that counts as homework you’ll never get credit for.
In my own interview-prep sessions, I pull up every interviewer’s LinkedIn profile while the client is still describing the loop. By the time they finish, we’ve got a question for each person. Minutes, not hours, and it’s the prep habit that most reliably changes the energy in the room.
How to research a company before an interview in 15 minutes
Set a timer. The limit is the point, because pressure forces you to pick what matters.
Step 1: Read the latest news (3 minutes)
Search “[company name] news” and open the two most recent results. You’re looking for a funding announcement, a product launch, or a leadership change. Any of those tells you what the company is trying to do right now, and therefore what your role exists to support.
For a public company, skip the press releases and go straight to the annual report. Every US-listed company files a 10-K every year, and you can pull it free from the SEC’s EDGAR database. Read the “Risk Factors” section only. It’s the company telling you, in its own words, what keeps its executives up at night. Nobody else in your interview loop will have read it.
Then turn what you found into a question: “I saw you just launched [X]. How is the team thinking about [the related challenge]?”
Step 2: Stalk the interviewer on LinkedIn (4 minutes)
This is the block most candidates skip, and it’s the one that pays the most.
Open each interviewer’s profile and note three things: how long they’ve been at the company, what they did before, and whether their path suggests a promotion or a sideways move. Then look for one commonality – a shared former employer, a school, a city, a technology you both worked in.
Not to flatter them. A question only that one person could answer reads as genuine interest, while a question you could ask anyone reads as filler. “You’ve been here five years and moved up three times. What’s kept you here?” lands differently than “What’s the culture like?”
I tell clients to prepare three specific questions for each person, plus a bank of 10 general questions about the company for when a conversation runs long. You’ll use the two that fit.
Step 3: Read the job description like a map (3 minutes)
Paste it into a doc and highlight every skill or priority that appears more than once. The three to five things that repeat are what the hiring manager actually cares about, however long the requirements list runs. (If you’re not sure what’s real and what’s boilerplate, I wrote a full breakdown on how to read a job description.)
Now assign one story to each repeated priority. Not a bullet point – a story with a problem, what you did, and what changed. A priority with no story attached is the gap you’re most likely to get asked about, so prep it first.
Step 4: Check what they’re saying publicly (2 minutes)
Scan the company blog, the engineering or product blog if there’s one, and the CEO’s last few LinkedIn posts. You’re not reading for depth. You’re reading for the problem they keep circling, because that’s the problem they opened your role to solve.
This block catches things the news won’t. A CEO who posted twice last month about “doing more with less” is telling you what the budget conversation looks like, and that’s worth knowing before you spot the interview red flags in person.
Step 5: Build your questions (3 minutes)
Write down two or three questions that could only have come from this research: one about the company’s direction, one for the specific interviewer, and one about what success looks like in the role.
My favorite version of that last one: “In six months, how will you know I was the right hire?” The phrasing presupposes you’ve already got the job, so the interviewer answers as if you do, and you walk out with their actual success rubric. If you want more options, I’ve listed seven questions to ask in an interview that get real answers.
Using the research in the room without sounding like a stalker
Research only works if it’s invisible. The failure mode is the candidate who opens with “I read your 10-K and noticed your churn risk in the EMEA segment.” That’s not preparation, that’s a performance, and it makes people uncomfortable.
Instead, use it in three places:
- Early, once. One line in the first five minutes that shows you know what they’re working on. “I saw the launch last month. How’s that changed the team’s priorities?” Then move on.
- In your answers. When you tell a story, connect it to their problem, not to a generic version of it. “You mentioned scaling the onboarding team. The closest thing I’ve done to that was…” You’re handing them the sentence they’ll repeat in the debrief.
- At the end. The two questions you built. Delivered as curiosity, not as proof you did homework.
Notice what’s missing: reciting facts. Nobody ever got hired for knowing the founding year.
When you’ve got more than 15 minutes
Everything above is the floor. For a final round or a role you badly want, there’s one upgrade worth the extra hour: talk to someone who recently left. Current employees can’t tell you the truth. People who left six months ago can, and they usually will.
Still, don’t let the upgrade replace the basics. Most candidates who don’t research a company before an interview didn’t run out of time. Nobody showed them a version that fits in 15 minutes, and now you’ve got one.
Frequently asked questions
How long should you spend researching a company before an interview?
Fifteen minutes for a first round, done the day before. For a final round, add an hour and spend it talking to a former employee, not reading more web pages.
What should you research about a company before an interview?
Recent news, each interviewer’s LinkedIn, the priorities that repeat in the job description, and what the company says publicly. Skip the founding history and the mission statement.
Should you mention your research during the interview?
Once, and lightly. Reference one recent event early, connect your stories to their real problem, and ask the questions your research produced. Never narrate the research itself.
What to do next
If you want to know what a slow, under-prepared search is costing you, run the job search cost assessment. Ninety seconds, and it gives you a monthly dollar figure plus the stage of your search that’s leaking the most.
If company research is the part you want to get better at, read Company Research: The People Who Left Tell the Truth next. It’s the one-hour upgrade to this system.
If you would rather have someone prep the interview with you and tell you exactly what to research first, book a free strategy call.