Company research is not about memorising facts — it's about building the context to answer 'Why us?' convincingly, to ask questions that signal genuine understanding, and to frame your experience against what actually matters to this specific business right now. The candidates who treat company research as a box-ticking exercise show it immediately. This guide walks you through a structured 4-hour research protocol that covers everything you need without wasted effort.
Time investment by interview stage
Phone screen: 45 minutes. Technical/hiring manager round: 2 hours. Final loop (4–6 rounds): 3–4 hours. For a final loop at a company you care about, budget a full evening.
Step 1: Understand the Business Model (20 minutes)
Before you read anything else, you need to understand how the company makes money, who their customers are, and what their unit economics look like. This is the frame everything else fits into.
- Google '[Company name] business model' and read the top result — Wikipedia, Investopedia, or a quality breakdown on Stratechery or Similar Web.
- For public companies: pull the most recent 10-K from SEC EDGAR (sec.gov/edgar). Read the first 10 pages: Business Overview, Risk Factors, and Management Discussion. Set a timer — you don't need the full document.
- For private companies: check Crunchbase for funding history, investor names, and reported revenue. The investors themselves often publish thesis documents that explain what they saw in the business.
- Note: What are the top 2–3 metrics this business lives or dies by? (ARR, GMV, DAUs, margin, etc.) You'll reference these in your interview answers.
Step 2: Read Their Public Narrative (20 minutes)
The company's public narrative — what they say about themselves — tells you what they're optimising for in culture, brand, and talent. This is what 'cultural fit' is actually evaluated against.
- Read the company's About page, mission statement, and any published values or principles. (Amazon: Leadership Principles. Google: Ten things we know to be true. Netflix: Culture memo.)
- Watch the CEO's most recent public talk, podcast appearance, or earnings call opening remarks. Look for the 3–5 priorities they keep returning to.
- Check the company's engineering or product blog. The content they publish publicly reflects what they're proud of technically and what they want talent to know they're working on.
- For roles with a product component: use the product for 30 minutes. Note what's great, what's broken, and what you'd fix first — this is genuine material for 'What would you improve?' questions.
Step 3: Get the Current News Context (15 minutes)
Companies that are hiring are doing something — launching a product, entering a market, recovering from a setback, or scaling a successful division. Understanding what's happening right now is what separates preparation from research.
- Search '[Company name]' on Google News filtered to the last 3 months. Read the top 10 headlines and click into the 2–3 most significant ones.
- Check if they've had any recent layoffs, fundraises, acquisitions, or leadership changes. These always come up implicitly in final-loop conversations.
- For public companies: read the most recent earnings call transcript on Seeking Alpha (free tier) or The Motley Fool. The Q&A section shows what analysts are worried about.
- Check LinkedIn for the role's hiring manager and your potential team members. Note what they've published recently — topics, projects, priorities.
Step 4: Research the Interview Process (20 minutes)
Understanding the specific format of your interview is separate from understanding the company — but equally important. You need to know what's coming so you can prepare appropriately.
- Search '[Company name] [Role] interview process' on Google. Read the top 3–5 results — blog posts, Reddit threads, and forum discussions.
- Check Glassdoor Interviews for recent reports specific to the role and location you're interviewing for. Filter to the last 12 months.
- Search on Blind for recent threads about the company's loop — candidates often post very detailed breakdowns within days of completing an interview.
- Use Interview Intel's company prep guide to get the structured format, question types, evaluation criteria, and recent loop changes for your specific target.
Step 5: Prepare Your 'Why This Company' Answer (20 minutes)
This is where research converts into a talking point. 'Why us?' is asked in almost every loop, and generic answers ('I love your mission', 'you're a market leader') are immediately recognisable as surface prep.
- Write down 3 specific, concrete reasons you want this role at this company — one about the product or market, one about the team or culture signals you've seen, one about the strategic moment the company is in.
- Each reason should be traceable back to something specific you found in your research: a blog post, a product decision, a piece of news, a value that maps onto your work history.
- Rehearse the answer aloud. It should take 90 seconds and end with something forward-looking: 'I want to be part of [X] as the company [does Y].'
- Prepare a version for the recruiter screen (shorter, surface level) and a version for the hiring manager (deeper, more strategic).
Step 6: Prepare 5 Questions to Ask (15 minutes)
The questions you ask at the end of each round communicate as much about your judgment as your answers do. Generic questions ('What does success look like in this role?') are fine but forgettable. Questions anchored to your research are memorable.
- About the team: 'I saw you shipped [X feature/product] recently — what's the biggest technical or product decision that led to that?'
- About the roadmap: 'I noticed you're entering [market segment] based on [news/earnings]. How does this team contribute to that strategic push?'
- About culture: 'I read your [engineering blog post / leadership principles] — can you give me an example of a recent decision here that reflects [value X]?'
- About the role specifically: 'What would the first 90 days in this role actually look like — what's the most important thing to get done?'
- About growth: 'What's the path from this role to the next level, and what have you seen make the difference for people who move quickly?'
Don't ask questions answered in the job description
Reading the JD carefully before your questions round is basic prep. Asking 'What does this team do?' or 'What technologies do you use?' when those answers are in the posting signals you haven't done the minimum.
Step 7: Synthesise — What Are They Actually Looking For? (20 minutes)
By this point you should know the business, the culture, the news, and the interview format. The final step is synthesis: given everything you've learned, what specific experiences and stories from your background best match what this company needs right now? Write down 3–5 STAR stories that are directly relevant, then map them to the question types you're likely to face. This step is what turns research into performance.