Growing up in a working-class family, “prep for an interview” sounded like a luxury activity other people had time for. I thought you either knew the right people or you got lucky. After years in university admissions and corporate recruiting, I can tell you what actually moves the needle: walking into the interview understanding what the company is trying to do, what might be getting in their way, and where this role fits.
Company research is not about impressing someone by repeating their About page. It is about giving answers that sound like you already understand the work, because you do.

What you are trying to learn
Before interview day, you want to be able to answer four questions in plain language:
- What does this company sell or deliver?
- How do they make money and who do they serve?
- What has changed recently? Growth, leadership shifts, a new product, a lawsuit, a merger, a funding round, a big contract, a new competitor.
- What problems is this role likely here to solve? This is the part most candidates skip, and it is the part that makes your answers feel tailored.
If you can speak to those four points, you are usually better positioned for “Why us?”, many role-specific prompts, and a good chunk of the behavioral questions that come up. Not all of them. But enough that it is worth the time.
Your 5 to 10 minute plan
If the interview is same-day and you are squeezed, do this quick version. It is not perfect, but it gets you out of “I skimmed the About page” territory.
- Job posting first: circle 3 repeated phrases or must-haves.
- Homepage and one product page: write a 2-sentence summary of what they do and who it is for.
- One recent signal: check their newsroom or a quick Google News scan for the last 3 to 6 months.
- Two questions: one about the first 60 to 90 days, one about how success is measured.
Your 30 to 60 minute plan
You can do deep research for a dream job, but most people need a reliable system that works on a weeknight. Here is the order I recommend.
1) Company basics (10 minutes)
Skim the website, but be intentional. You are not memorizing. You are looking for keywords and priorities.
- Products or services: What exactly are they offering? Is it one core product or multiple lines?
- Customers: Who is it for? Individuals, hospitals, school districts, small businesses, enterprise?
- Business model: Subscription, per-service billing, contracts, consumer retail, ads, grants?
- Values and differentiators: What do they claim to do better than competitors?
Pro tip: If their site is vague, look for a “Solutions,” “Industries,” “Case Studies,” or “Customers” page. Those pages reveal what they actually sell and who buys it.
2) Recent news and signals (10 to 15 minutes)
Hiring managers live in the day-to-day, not the careers page. Spend a few minutes catching up on what changed recently so you do not walk into avoidable surprises.
- Company newsroom or blog: Product updates, expansions, new partnerships.
- Google News search: Look for major headlines in the last 6 to 12 months.
- Leadership announcements: A new CEO or VP often means a new strategy.
- Funding and growth signals: For private companies, funding rounds can be one reason they are hiring fast, but not the only one.
Write down 2 to 3 changes, then ask yourself: What new priorities might these changes create?
3) The team (10 to 15 minutes)
This step helps you stop giving generic answers. The point is to understand what the team actually does and what they care about.
- Company org signals: On LinkedIn or the company site, skim the company page and look for people with the title you would work with (manager, team lead, peers).
- Team structure: Is this role part of HR, operations, customer success, engineering, clinical leadership, or a shared services team?
- Career paths: Where do people come from? Where do they get promoted to?
You do not need to memorize names or dig through personal posts. Look for patterns: tools they mention, industries they hire from, and what they seem to prioritize.

4) The role (10 to 20 minutes)
Print the job posting or paste it into a document. Then do two quick passes:
- Pass one: Highlight must-have requirements and repeated phrases.
- Pass two: Translate each requirement into a problem the company is trying to solve.
Example translations (treat these as hypotheses to validate in the interview):
- “Improve documentation” often points to inconsistency, compliance risk, or too much tribal knowledge.
- “Handle escalations” often points to churn, service issues, unclear ownership, or capacity problems.
- “Build dashboards” often points to leaders lacking visibility, trust in the numbers, or consistent definitions.
- “Cross-functional stakeholder management” often points to conflicting priorities and stalled projects.
Once you have the likely problems, you can shape your stories around solving them.
Learn the product fast
If you only have time to learn one thing, learn the product or service in a way a customer would describe it. I used to hire for nursing roles and remote tech roles, and the best candidates were the ones who could explain the company’s offering simply, then connect it to outcomes.
Use this mini-checklist:
- Who uses it? End users and decision-makers are not always the same.
- What problem does it solve? Speed, cost, safety, convenience, compliance, revenue.
- What is the “aha” benefit? The one-sentence reason someone buys.
- What might be hard about it? Implementation, training, change management, integration, adoption.
Keep it grounded: Watch a product demo video, read one case study, or scan their FAQ. Stop after you can explain the offering in 2 to 3 sentences.
For technical and portfolio roles
If you are interviewing for engineering, data, design, product, or marketing roles, add one more layer: touch the product and skim how they talk about building it.
- Use the product: Create an account, run through onboarding, and note any friction points. Even 10 minutes helps.
- Read the docs: For developer tools, APIs, or platforms, scan the docs table of contents to learn what they prioritize.
- Check changelogs or release notes: You can often spot what is being improved and what is still rough.
- Look for an engineering or product blog: Not for trivia, but for signals about their stack, quality standards, and how they think.
In interviews, you can say something simple like: “I tried the onboarding flow and I can see how it gets a new user to value quickly. I also noticed a few steps where I had questions. I would love to learn how you think about activation and drop-off.”
Spot the role’s problems
This is the part that turns research into interview advantage. You are trying to predict the headaches this role is meant to reduce.
Look for clues in three places:
Clue 1: Verbs in the job posting
Words like reduce, streamline, own, launch, stabilize, scale, and turn around are signals. “Scale” and “stabilize” are very different problems.
Clue 2: What they brag about
If the company emphasizes speed, they may struggle with bottlenecks. If they emphasize quality, they may be tightening standards. If they emphasize culture, they may be in growth mode or recovering from turnover.
Clue 3: What changed recently
New leadership, a new contract, a product launch, or an expansion often creates workload spikes and process gaps. That is where a new hire comes in.
When you can name a likely problem tactfully, your answers sound like you already belong in the room.
Research the interviewer
If you have names from the calendar invite, use them. This takes a few minutes and helps you build rapport without being weird about it.
- Start with their role: What team are they on and what do they own?
- Scan their recent experience: A quick scan is usually enough to spot patterns like “process builder,” “startup to scale,” or “customer obsessed.”
- Look for shared context: Industry overlap, tool overlap, or the type of problems they work on.
Keep it professional. Do not mention personal posts, family details, or anything that feels like you went deep. A good line sounds like: “I saw you’ve been leading the team through a growth phase. I’d love to hear what has been hardest to scale.”
Use research in answers
Most candidates make one of two mistakes: they either say nothing company-specific, or they overdo it and sound like they memorized marketing copy.
Use this structure instead:
- 1) Name what you noticed in one short line.
- 2) Connect it to the role or the team’s goals.
- 3) Prove fit with a quick example from your experience.
“Why do you want to work here?”
Instead of: “I love your mission and values.”
Try: “I noticed you’ve been expanding into new markets this year, and the job description emphasizes building repeatable processes. In my last role, I helped standardize our intake and handoff steps across three locations, which cut rework and made onboarding new staff much smoother. That is the kind of scaling work I’m excited to do again.”
“What do you know about us?”
Try: “You serve mid-sized health systems, and it looks like your platform focuses on reducing administrative burden for clinical teams. I also saw a recent update around integrations, which tells me interoperability is a priority. I’m curious how that is influencing your roadmap for this quarter.”
“Tell me about a time you handled a challenge”
Try: “From the posting, it sounds like this role handles escalations when timelines or expectations slip. In my last position, I inherited a backlog of urgent requests. I set up a triage system, clarified service levels with stakeholders, and within six weeks we had predictable turnaround times.”
You are not quoting their site. You are translating what you learned into a practical conversation.
Questions to ask
You do not need a long list. You need a few questions that prove you understand the work and care about impact.
- “What problem would you most like the person in this role to solve in the first 60 to 90 days?”
- “What does success look like by the end of the first quarter?”
- “What’s working well on the team today, and what feels heavier than it should?”
- “What would you say is the biggest constraint right now: time, tooling, process, headcount, or alignment?”
- “How does this team measure outcomes?”
These questions invite real conversation and give you information you can use later, including in your follow-up thank-you email.
Remote and hybrid research
Because I’ve hired heavily for remote roles, I always encourage candidates to research how the company actually operates day-to-day, not just whether they allow remote work.
- Communication norms: Do they talk about async work, documentation, or meeting culture?
- Time zones: Where is the team located, and what hours are implied?
- Tools: Job postings often reveal what a team runs on. Common examples include Slack, Teams, Jira, ServiceNow, Workday, Epic, or a specific CRM.
- Collaboration style: Look for phrases like “high autonomy,” “fast-paced,” or “white-glove support.” Each one comes with expectations.
If you are interviewing for a remote role, it is fair to ask: “How does the team stay aligned when priorities shift?” That question lands well when you have already done your homework.
Veterans and career changers
I’ve helped a lot of military veterans translate their experience into civilian roles, and the same research process applies, with one extra step: learn the company’s language for the work you already know.
- Translate your experience into their outcomes: reliability, safety, compliance, training, logistics, incident response, process discipline.
- Look for regulated environments: healthcare, finance, government contracting, and manufacturing often value the structure many veterans bring.
- Identify handoff points: In both military and civilian settings, problems happen during transitions. If the role touches coordination, your stories can shine.
For career changers, research helps you do the same thing: connect your transferable skills to the company’s real needs, not just the job title.
Boundaries that matter
Research should make you sharper, not creepier. Keep it above-board and respectful.
- Respect paywalls and terms: If a source blocks you, move on. You do not need to break rules to prepare well.
- Do not “surprise connect” right before the interview: Unless someone invites it, skip last-minute LinkedIn requests to interviewers.
- Stay job-relevant: Professional context is fair game. Personal details are not.
Night-before checklist
Before you go to bed, try to have these written down in a notes app or on paper:
- A 2-sentence explanation of what the company does and who it serves.
- Two recent updates or headlines and why they matter.
- Three role “likely problems” you think you’re being hired to solve.
- Two stories from your experience that map to those problems.
- Three questions you want to ask.
If you do only this, you will sound more focused than most candidates who “researched” for hours but did not translate anything into interview-ready language.

Common mistakes
- Mistake: Memorizing the About page.
Fix: Learn the product, customer, and current priorities instead. - Mistake: Ignoring negative news.
Fix: Be aware, but stay professional. Ask neutral questions like, “How is the team navigating change this year?” - Mistake: Researching everything except the job posting.
Fix: The job description is your map. Translate it into problems and outcomes. - Mistake: Overusing buzzwords you saw online.
Fix: Use your own words. Clarity beats jargon in interviews.
Handling negative news
Sometimes you find a tough headline: layoffs, a lawsuit, a sudden CEO change, a product outage. Do not pretend you did not see it, and do not make the interview a courtroom.
If it is relevant, keep it calm and forward-looking. Here is a script that works:
“I saw the announcement about the reorg earlier this year. I know that kind of change can put pressure on teams. I’d love to understand what priorities are most important right now, and what support this role would have to help the team execute.”
You are signaling awareness and maturity, not panic.
FAQ
How much research is enough?
Enough is when you can explain what they do, name 1 to 2 recent changes, and connect your experience to 2 to 3 problems the role likely exists to solve. For many interviews, that is 30 to 60 minutes of focused work.
Should I bring notes?
Yes, if it helps you stay organized. A small notebook with your questions and a few bullet points is professional. Just do not read full answers off the page.
What if the company is private and there is not much info?
Use what you can: the job posting, leadership profiles on LinkedIn, customer reviews if applicable, and any interviews or podcasts featuring executives. Then focus on role problems and how you solve them.
How do I research without LinkedIn?
Start with the company site, press releases, and news coverage. You can also look at leadership bios, conference speaker pages, and reputable industry publications. The goal is still the same: product, customer, changes, and role problems.