Interview Research

How to research a company before an interview

Most candidates research the product. Senior candidates research the room they'll be judged in. Here's how to see it before you walk in.

By the time you reach a final-round interview for a senior role, the company already assumes you can do the work. The product demo, the headcount, the funding total — useful context, but it's not what the room is testing. What the room is testing is whether you understand the pressure the team is actually under, and whether you'd relieve it or add to it.

That's a different research target. You're not trying to know what the company does. You're trying to map the situation you'd be walking into — the mandate behind the role, where decisions really get made, and what changed recently to create this opening in the first place. Do that, and you stop guessing at the interviewers' questions; you start anticipating them.

What "company research" usually misses

Open most interview-prep advice and you'll find the same checklist: read the website, memorize the mission, learn the funding history, scan the leadership team. None of it is wrong. All of it is surface. It prepares you to recite the company, not to read the room.

The gap shows up the moment an interviewer asks something like "How would you approach your first 90 days?" or "What would you change about how we operate?" Surface research produces a generic answer. Situational research produces an answer that lands — because it's aimed at the specific tension the team is living with.

The five layers worth mapping

Good interview research is layered. The deeper layers are harder to find and far more valuable. Work down this list in order; even partial coverage of the lower layers beats a perfect recital of the top one.

1. The mandate behind the role

A role exists to solve a problem, not to fill a box. Why does this seat exist now? Is it a growth hire (scale what's working), a turnaround hire (fix what's broken), a backfill (continuity), or a new function (build from zero)? The job posting usually leaks the answer in its verbs — "scale," "rebuild," "establish," "stabilize." The mandate determines what "good" looks like in the role, and therefore what the interviewers are screening for.

2. Where decision rights actually sit

Org charts show reporting lines. They don't show authority. The questions that matter: who actually approves the things this role would own — budget, headcount, roadmap, architecture? Does the title carry real decision rights, or is it influence-without-authority? You can infer a lot from how the role is described and from how recent, similar leadership announcements were framed publicly.

3. What changed recently

Openings are created by change. New funding, a reorg, a leadership departure, a strategy pivot, a missed target, an acquisition. Recent change is the single highest-signal thing you can know, because it tells you the emotional weather of the team — energized, anxious, defensive, rebuilding. Recent press, funding announcements, and leadership-change news are the easiest places to find it.

4. The panel's incentives

Each interviewer is evaluating you against their own stake. A hiring manager wants relief and a safe pair of hands. A future peer wants to know you won't make their life harder. A skip-level wants strategic judgment. A cross-functional partner wants to know you'll collaborate, not empire-build. You won't always know the exact panel in advance, but you can usually anticipate the roles in the room — and each role tests a different thing.

5. The failure stories

Every team has a story about the last person in this seat, or the last big initiative that didn't land. You rarely get this from public sources, but you can probe for it carefully in the interview itself (see reverse-interview questions to ask). Knowing what the team is quietly afraid of repeating is worth more than any fact on the careers page.

Where to actually look (public sources)

You don't need insider access to map most of this. Read these sources for signal, not just facts — what they imply about mandate and change:

• The job posting, read twice. First for the requirements, then for the verbs and the order of priorities. What's listed first, and how it's phrased, usually reveals the real mandate.
• The careers and "about" pages. Tone and emphasis tell you what the company believes about itself right now — and where it's trying to convince itself.
• Recent press, funding, and leadership news. The change layer. A raise, a new exec, a pivot, a layoff — each reshapes the pressure on the team.
• Engineering, product, or company blogs and talks. How the team thinks and what it's proud of (and quietly defensive about).
• Public filings, for larger companies. Risk sections and strategy language are unusually honest about what leadership is worried about.

Treat anything you read as a hypothesis to confirm in the room, never as settled fact — especially for fast-moving companies where last quarter's situation may already be stale.

The goal of research isn't to walk in knowing the answers. It's to walk in knowing the real questions — the ones the team is actually wrestling with — so your answers aim at them.

Turn research into questions

Research that stays in your head is wasted. The payoff is turning each layer into a sharp, specific question or a precisely-aimed answer. If your research suggests the role is a turnaround, your "first 90 days" answer should sound like a stabilizer, not a visionary. If you sense unclear decision rights, you can probe for them respectfully. The strongest signal you can send a senior panel is that you already understand the shape of their problem.

This is the bridge from research to performance, and it's where most preparation falls down — people gather context and then never convert it. A structured way to do that conversion is the heart of reverse-interview questions and executive interview preparation.

A 45-minute research routine

You don't need a week. You need focus. A repeatable pass:

1. 10 min — Mandate. Re-read the posting for verbs and priority order. Write one sentence: "This role exists to ______."
2. 10 min — Change. Scan recent news, funding, and leadership announcements. Write one sentence on the team's current weather.
3. 10 min — Decision rights. Note what the role would own and where you're unsure authority really sits. Mark those as questions for the room.
4. 10 min — The panel. List the likely roles you'll face and what each one is testing for.
5. 5 min — Convert. Turn each unknown into one reverse-interview question. Walk in with five.

Frequently asked questions

How long should I spend researching a company before an interview?

For a senior role, about 45 focused minutes is enough — if you spend it on mandate, decision rights, and recent change rather than memorizing the product. The 45-minute routine above is designed to fit that budget.

What should I look for that most candidates miss?

The room, not the product: why the role exists now, where authority actually sits, what changed recently, and what the team is quietly afraid of repeating. Those shape the questions you'll be asked.

Can I research a company without insider connections?

Yes. The job posting, careers page, recent press and funding news, public blogs and talks, and (for larger companies) public filings carry more signal about mandate and change than most candidates extract from them.