How to Research a Company Before an Interview

By Renata Solberg, Director of Interview Coaching · Updated June 26, 2026 · ~40 min read

Why company research wins interviews

Every interviewer, consciously or not, is answering two questions about you: Can this person do the job? and Do they actually want this job, here, with us? Your resume and your answers carry the first. Company research is how you win the second, and the second is where most candidates quietly lose. When two people are equally capable, the one who clearly understands the business, speaks to its real challenges, and asks questions that could only come from genuine homework is the one who feels like a colleague already. That feeling is what converts an interview into an offer.

It runs deeper than impressing anyone. Research changes how you show up. A candidate who knows how the company makes money, what it's wrestling with this quarter, and what the role is really there to solve doesn't give generic answers; they give answers that land, because they're aimed at this specific target. They don't ask "So what does the company do?" They ask "I noticed you've leaned into self-serve onboarding this year — how is that reshaping what this team is responsible for?" One question signals a passenger; the other signals a future teammate who's already thinking about the work.

Consider what actually happens in the mind of an interviewer over the course of a conversation. They meet dozens of candidates who can technically do the work; what they remember are the few who made them feel understood. When you reference the exact challenge their team is wrestling with, or connect your experience to a strategic move they made last quarter, you're not just answering questions; you're demonstrating that you've already begun to think like a member of the team. That mental shift, from "applicant" to "colleague," is subtle but decisive. It's the difference between a candidate the interviewer evaluates and one they start, quietly, to root for. Research is the cheapest, most reliable way to trigger it.

There's a quieter benefit too: research protects you. An interview is a two-way evaluation. The same digging that helps you speak well also helps you spot a struggling business, a chaotic team, or a culture that won't fit you, before you accept and regret it. Done honestly, company research is as much about deciding whether you want them as convincing them to want you. The candidates who treat it that way come across as confident and selective rather than desperate, and that posture, all on its own, makes you more attractive to hire.

The right mindset: chase questions, not facts

The most common research mistake is treating it like cramming for a quiz — memorizing the founding year, the headquarters city, the headcount, the investor list. None of that helps you in the room, because no good interviewer asks you to recite their own About page. Trivia is the booby prize of preparation. What actually moves the needle is understanding, and understanding comes from chasing questions, not collecting facts.

So go in with questions, and let the facts assemble themselves as answers. Instead of "what year were they founded," ask yourself: How does this company make money? Who pays them, and why? What are they betting on this year? What's hard about their business right now? Why does this role exist, and what would success in it look like? Where could someone with my background move the needle? Each of those is a question whose answer is genuinely useful in conversation — and the act of answering them is what turns scattered reading into a coherent picture you can actually speak from.

This reframing also tells you when to stop. Facts are infinite; you could read forever. Questions are finite. Once you can answer the handful that matter — in plain language, without notes — you're done, whether that took ninety minutes or three hours. Aim for a small set of specific, relevant insights you can deploy, not a comprehensive dossier you'll never use. Depth on the few things that matter beats breadth on everything that doesn't.

Layer 1 — Understand the business

Start here, always, because everything else makes sense only once you understand how the company stays alive. If you can explain in one clear sentence how this company makes money, who its customers are, and what problem it solves for them, you already understand it better than most candidates who walk through the door. This is the foundation; build it first.

Why start with the money? Because every other thing you'll observe about a company is downstream of how it survives. A company that lives on a few enormous annual contracts will be cautious, relationship-driven, and slow to change, because losing one customer is a crisis. A company that earns small recurring payments from thousands of customers will be obsessed with retention, churn, and product self-service, because its fortunes turn on keeping a million people mildly happy rather than five executives delighted. The same job title — "account manager," "engineer," "marketer" — means something genuinely different inside each, and the interviewer's questions will reflect that difference. Understanding the model is how you decode what they're really asking.

The four questions that define a business

1. How does it make money? What does the company sell, and what's the model — subscriptions, one-time sales, transaction fees, advertising, services, licensing? A business that earns recurring revenue from many small customers behaves very differently from one that lands a few huge contracts a year, and that difference shapes nearly every role.
2. Who are the customers? Does it sell to consumers, to small businesses, to large enterprises, to developers, to governments? Who actually signs the check, and who actually uses the product (sometimes not the same person)? Knowing the customer tells you what the company truly optimizes for.
3. What problem does it solve? What's the core value — the reason a customer chooses this product over the alternative or over doing nothing? Strip away the marketing language and name the underlying job the product gets done.
4. How is it doing? Growing, mature, turning around, newly funded, cost-cutting? You won't always get hard numbers, but the broad trajectory shapes what the company needs from a new hire — a builder, a scaler, a fixer, a steady operator.

Try the product if you possibly can

Reading about a product is one thing; using it is another entirely. If there's a free trial, a freemium tier, a demo, an app, or a store you can walk into, experience it as a customer would. Sign up. Click around. Notice what's smooth and what's clunky, where it delights and where it frustrates. Few things land harder in an interview than "I created an account over the weekend and was impressed by how fast the onboarding was, though I did get a little stuck at the integration step." That single sentence proves more genuine interest and product sense than an hour of reading ever could, and it gives you authentic, specific things to talk about.

Layer 2 — What's happening right now

Understanding the business in the abstract is the floor. What separates good preparation from great is currency — knowing what's happening with this company this month, not just what it has always been. Recency is the strongest possible signal of genuine interest, because nobody bothers to learn last week's news about a company they don't actually care about. Spend real time here.

What counts as "right now"

• Recent announcements — product launches, new features, expansions into a market, partnerships, a rebrand. These tell you where the company is investing and what it's proud of.
• Funding or financial events — a raise, an acquisition (in either direction), a new earnings result, a public filing. Money moving is a window into priorities and pressure.
• Leadership changes — a new chief executive, a new head of your function, a notable departure. New leaders bring new priorities, and that often explains why a role is open.
• Press and coverage — what outsiders are saying, both flattering and critical. A balanced view beats only reading the company's own framing.
• The company's own voice — recent blog posts, an engineering or product update, the founder's or executives' recent public posts. This is where you hear, unfiltered, what's top of mind for the people you'll meet.

Connect the news to the role

Where currency comes from

Recency lives in a handful of predictable places. The company's own newsroom or blog is the first stop: it's where launches, milestones, and point-of-view pieces appear, and reading the three or four most recent posts tells you instantly what the organization wants the world to notice right now. Next, the public posts of the founder, the chief executive, and the leader of your function are unusually revealing, because senior people tend to write about whatever is genuinely top of mind: a strategic bet, a hard quarter, a hiring push, a lesson learned. When the person who will influence your hire has publicly said "this year we're all-in on X," you have a direct line into the conversation you're about to have. Finally, outside coverage — independent articles, industry commentary, customer chatter — rounds out the picture with a perspective the company didn't author, which both adds credibility and occasionally surfaces tensions the official channels won't mention.

The skill isn't finding the news; it's connecting it to why you're sitting there. A recent expansion into a new market may be exactly why this role exists. A new head of department may mean the team is being rebuilt and they want someone comfortable with change. A funding round usually means a hiring push and pressure to grow fast. When you can say, "It looks like you've been investing heavily in expanding to mid-market customers — I'd imagine this role is partly about supporting that shift," you've shown you can connect strategy to execution, which is precisely the thinking they want from a strong hire.

Layer 3 — Research the role itself

It's easy to research the company and forget the job, but the role is what you'll actually be hired to do, and most of the interview is about it. The job posting is your richest single document, and most candidates skim it once and never return. Read it like a detective, because it's a coded message about exactly what this team needs.

Mine the job posting

1. Find the problem the role exists to solve. Beneath the bullet points, why does this job exist now? Are they scaling something, fixing something, launching something, replacing someone? The "why now" is the heart of the role.
2. Separate must-haves from nice-to-haves. Requirements listed first, repeated, or phrased as "must" are the non-negotiables. Map your strongest evidence to each one and be ready to prove it with a story.
3. Find the success metrics. Look for how the role will be measured — "grow pipeline," "reduce churn," "ship the platform." If they're implied rather than stated, infer them, and prepare to speak to how you'd move them.
4. Decode the seniority and scope. Will you lead, execute, or both? Own a number, a team, a system? The scope tells you which of your experiences to foreground.
5. Note the language. The exact words the posting uses — and the order it lists priorities — tell you what to mirror in how you talk about your own background.

This is the same close reading that powers a strong, tailored resume; if you want a deeper method for matching your materials to a specific posting, our guide on tailoring your resume to a job walks through it step by step, and getting the keywords right covers how to mirror the posting's genuine terms. The point in interview prep is slightly different: you're not just matching keywords, you're preparing to narrate the match out loud, with evidence.

Map yourself to the role

For each major requirement, write the single best piece of evidence you have — a project, a result, a moment. Then prepare to tell that as a short, structured story when the matching question comes. The STAR method (Situation, Task, Action, Result) is the reliable container for these. And think one step past the posting: what would you actually do in the first ninety days? A candidate who can sketch a credible first-quarter plan — "I'd start by understanding your current pipeline data, then look for the two highest-leverage fixes" — sounds like someone already doing the job.

Layer 4 — Research the people you'll meet

You're not interviewing with a company; you're interviewing with people. If you know who they are in advance, you can build a little rapport, anticipate what each will focus on, and frame your answers to what they actually care about. Most interviewers will tell you, or your recruiter will, who you'll be meeting. If they don't, it's completely reasonable to ask: "Could you let me know who I'll be speaking with, so I can prepare?" is a professional, welcome question.

What to look for about each interviewer

• Their role and how it relates to yours. Are they your future manager, a peer, a skip-level leader, someone from a team you'll partner with? This tells you the lens they'll judge you through — a manager weighs whether you can do the job and fit the team; a cross-functional peer weighs whether you'll be good to work with.
• Their tenure and trajectory. Long tenure often means deep institutional knowledge and pride in the place; recent arrival may mean they're bringing change. Either is useful context for how to pitch yourself.
• Their background. Where have they worked and studied? You may find genuine common ground — a former employer, a field, a city, a stated interest — that makes the conversation warmer and more human.
• What they care about publicly. If they've written, spoken, or posted about their work, you get a direct read on what they value and what they might probe.

The goal is calibration, not surveillance. Knowing that one interviewer leads the data team and another runs partnerships lets you bring the right stories to each conversation. It also helps you ask each person better questions: you wouldn't ask a peer engineer about board-level strategy, or a founder about day-to-day tooling. For more on how the people across the table actually evaluate you, our piece on what hiring managers really want is a useful companion.

Layer 5 — Read the culture honestly

Culture is the hardest layer to research because the company controls most of the visible signals, and every company describes itself as collaborative, fast-paced, and mission-driven. The careers page is a recruiting brochure, not a documentary. To get closer to the truth, you have to triangulate, gathering signals from several independent sources and looking for the pattern, because no single source is reliable on its own.

Watch for the gap between the stated and the observed. If a company's values trumpet "work-life balance" but reviews repeatedly mention long hours and the interview is scheduled for 7pm on a Friday, believe the pattern, not the poster. Conversely, when the stated values, the employee voices, and your own experience of the process all point the same way, you can trust that read. The point isn't cynicism; plenty of companies genuinely live their values. It's that you verify rather than assume.

The signals worth weighing most

Not all culture signals are equal. The ones the company can't fully stage-manage are the most honest. Pay particular attention to how the interview process itself is run, because it's a live, unedited preview of how the organization operates. Is communication clear and timely, or do days pass without word? Do interviewers show up on time and prepared, having read your materials, or do they wing it? Are the stages explained, or are you kept guessing? A company that treats candidates with respect, organization, and warmth during the courtship is usually telling you the truth about how it treats people once they're inside. A chaotic, dismissive, or disrespectful process is rarely an outlier; it's a sample.

Weigh employee reviews carefully but skeptically. They skew toward the extremes — the delighted and the furious write reviews; the contented middle rarely bothers. So discard the lone five-star rave and the lone one-star tirade, and read for what shows up repeatedly. If a dozen unrelated reviews independently mention the same strength ("great manager support") or the same weakness ("unclear priorities"), that pattern is real signal. Pair it with how current employees describe their actual work in public, which tends to be more measured and concrete. The aim across all of it is a calibrated, fair read, not a verdict from any single voice.

Where to look: a practical source map

Knowing what to research is half the battle; knowing where to find it is the other half. Here's the map our coaches use, roughly in the order you should work through it: each source answers different questions, and together they build the full picture.

The most underused source: a person on the inside

Public sources only get you so far. The single richest input is a real conversation with someone who works there, or used to. A current or former employee can tell you in five minutes what the team is really like, what the interviewers tend to focus on, and what challenge the role is meant to solve, things no website will ever say. This is where your network becomes a research engine. If you don't have an obvious contact, a brief, respectful outreach to a second-degree connection often works; our guides on informational interviews and reaching second-degree connections show exactly how to ask without being pushy. Even one short conversation can transform your preparation from generic to genuinely insider, and reaching the people inside a company is the entire premise of the side door that Marqee runs on your behalf.

Tailoring research to the interview stage

How much you research, and what you emphasize, should change with where you are in the process. Pouring three hours into a thirty-minute recruiter screen is overkill; bringing screen-level preparation to a final-round panel is malpractice. Match the depth to the moment.

The pattern is a widening lens. Early rounds reward sharp focus on the role and your fit for it; later rounds reward commercial and strategic understanding of the whole business. By the final round, the panel often assumes you can do the job and is instead weighing judgment and conviction, which is exactly when your deep, current grasp of the company's strategy and market becomes the thing that separates you. Carry forward everything you learned in earlier rounds and add a layer of strategic altitude for the people at the top.

Competitors and the market

You don't need a market analysis, but a light read on the competitive landscape pays off twice. First, it shows commercial awareness: you understand that the company doesn't operate in a vacuum, which signals business maturity. Second, it sharpens how you talk about where you'd add value, because value is always relative to alternatives. Aim for just enough to answer three questions.

1. Who are the main alternatives? Who else solves this problem for the same customers — including the "do nothing" or "build it in-house" options? You don't need an exhaustive list, just the two or three that matter.
2. How is this company different? What's its stated edge — faster, cheaper, more premium, more specialized, better for a particular segment? This is usually clear from how it positions itself.
3. What pressure does that create? If a company competes on being the premium option, its pressure is justifying the price and retaining customers. If it competes on price, its pressure is efficiency and scale. Naming the pressure helps you speak to the challenges the role likely addresses.

Reading positioning from how a company talks

You can infer most of a company's competitive stance from the words it chooses about itself, without any market report at all. Language is positioning made visible. A company that repeatedly says "enterprise-grade," "secure," and "compliant" is signaling that it competes on trust and is courting large, risk-averse buyers — which tells you the role probably values rigor and reliability. A company that leans on "simple," "fast," and "no setup required" is competing on ease and likely selling to smaller customers who won't tolerate friction, so the role probably prizes speed and customer empathy. One that emphasizes "powerful," "customizable," and "for teams that…" is positioning for depth and a specific segment. Read three or four pages of a company's own copy and the competitive strategy usually reveals itself: who they're for, what they promise, and what they're implicitly conceding to rivals. That inference, offered tentatively in the room, demonstrates a level of commercial reading most candidates never show.

In the room, this knowledge surfaces gracefully: "I think your edge is really the depth of your integrations compared with the broader, shallower alternatives — is that how the team sees it?" That sentence demonstrates you understand not just the company but its place in the market, which is exactly the strategic awareness that distinguishes a senior, thoughtful candidate from a tactical one.

Researching small companies and startups

Small and early-stage companies present the opposite problem from large ones: there's barely anything online. No press coverage, thin or no reviews, maybe a single founder and a sparse website. Don't read that absence as a dead end; it just means you shift where you dig, and it raises the value of the sources that do exist.

• The founder is the company. At a small company, the founder's background, public posts, and stated vision often are the strategy. Understanding how the founder thinks tells you more than any About page would at a larger firm.
• The product is your best teacher. With little written about the company, using the product yourself becomes essential rather than optional. It's often the single most informative thing you can do.
• Customers and reviews, however few. Even a handful of customer testimonials, app-store reviews, or community comments tell you who's getting value and why.
• Funding or launch announcements. A single press release about a raise or a launch can reveal the stage, the ambition, and the immediate priorities.
• The wording of the job posting. At a small company the posting is often written by the founder or hiring manager personally, so it's unusually revealing about what they actually need and how they think.

There's an emotional dimension worth naming, too. Founders and early employees are personally invested in their company in a way that staff at a large corporation rarely are; the product is their idea, their risk, often their savings. When you show genuine, specific enthusiasm for what they've built, it lands far more powerfully than it would at a big company, because you're speaking to something they care about deeply. The candidate who says "I tried your product and I genuinely think the scheduling flow is the cleanest I've used, and I'd love to help more people discover it" is speaking the founder's language. That sincerity, grounded in real use rather than flattery, is disproportionately persuasive at the small end of the market.

The reframe for small companies is this: depth of product and customer understanding matters more than financial detail that simply isn't public. Showing a founder that you tried their product, understood who it's for, and have a point of view about it will impress far more than any fact you couldn't have found anyway. Genuine engagement is the whole game when the paper trail is thin.

Researching large companies and the right team

Large companies pose the reverse challenge: an overwhelming amount of information, most of it irrelevant to your specific role. The risk is drowning in corporate-level news while knowing nothing about the actual team you'd join. The discipline here is to zoom in.

• Find your division or team. A giant company is really a federation of teams with their own cultures, leaders, and priorities. Research the specific group, product line, or department this role sits in — that's where you'll actually work.
• Filter news to your area. Company-wide announcements matter less than what's happening in your function or product. Prioritize the news that touches your team's work.
• Identify the local leadership. The chief executive of a large company is far less relevant to you than the director or VP who runs your function. Know that person and their stated priorities.
• Use the scale to your advantage. Big companies have more public material, more employee voices, and more people in your network who've worked there. Mine all of it, but always filter for relevance to your role.

The principle is the same as everywhere else — chase the questions that matter for your conversation — but at a large company the hard part is narrowing. Resist the urge to memorize headline corporate strategy you'll never be asked about, and invest instead in understanding the team, the product, and the leader you'd actually report up through.

Turning research into talking points

Research that stays in your notes does nothing. The whole point is to convert what you learned into a few things you'll actually use in the conversation. Don't aim to deploy everything you found; aim for a small, potent set. After your research, distill it into exactly three deliverables.

Deliverable 1 — Your one-sentence understanding

Write a single, plain-language sentence that captures how the company makes money and what it does for whom. "They sell subscription scheduling software to small service businesses, helping owners fill their calendars without hiring an admin." If you can say that cleanly and confidently, you've internalized the business, and that clarity will infuse every answer you give, even when you never recite the sentence aloud.

Deliverable 2 — Two or three connection points

These are the bridges between what you learned and what you offer — the moments where your experience meets their need. Each one pairs something specific about them with something specific about you. For example: "They're pushing into enterprise customers; I spent two years building exactly the kind of security and compliance features enterprise buyers demand." Prepare two or three of these and you'll have a natural, compelling answer to "Why do you want this role?" and "Why are you a fit?" that no generic candidate can match.

Deliverable 3 — Four questions to ask

Great questions are themselves evidence of great research (the next section is devoted to them). Have at least four ready, because some will get answered during the conversation and you don't want to be caught empty when they turn it over to you.

Turning research into questions to ask

When the interviewer says "What questions do you have for me?", that's not a formality; it's part of the evaluation, and often a heavily weighted one. Your questions reveal how deeply you've thought about the role and the company. Generic questions ("What's the culture like?") signal generic interest. Researched questions signal a serious candidate. This is where your homework pays its highest dividend.

The anatomy of a great question

The best questions share a structure: they reference something specific you learned, then ask something genuine you couldn't have answered yourself. The reference proves you did the work; the genuine curiosity makes it a real question rather than a performance. "I read that you're investing heavily in your developer platform this year, so how is that changing what this team is accountable for?" does both. Compare that with "What does a typical day look like?", which is fine but proves nothing.

Categories of strong questions

• About the role's success. "What would a great first ninety days look like in this role?" Shows you're already thinking about impact.
• About the team and how it works. "How does this team make decisions and handle disagreement?" Reveals the real working environment.
• About the challenge. "What's the hardest problem this team is facing right now?" Signals you want to contribute, not coast.
• About strategy, tied to research. "I noticed the recent push into X — how does this role connect to that?" Demonstrates commercial awareness.
• About the interviewer. "What's kept you here?" or "What surprised you most when you joined?" Builds rapport and gives you an honest read.

Questions that quietly evaluate them

Remember that the interview runs both directions. A handful of your questions should be aimed at deciding whether you want them, and asking these signals confidence and self-respect, which read as attractive rather than presumptuous. Ask about how the team handles failure or a missed goal; the answer tells you whether the culture is blame-driven or learning-driven. Ask what the previous person in this role went on to do, or why the seat is open; the answer reveals whether people grow there or churn out of it. Ask the hiring manager what they find most challenging about leading the team; a candid answer signals psychological safety, while a polished non-answer tells you something too. These questions do double duty: they protect you from a bad fit, and they make you look like the kind of thoughtful operator who evaluates carefully before committing.

Prepare more than you'll need, and keep one in reserve for the very end — a thoughtful final question leaves a strong last impression. For a deeper bank of options and the reasoning behind them, see our dedicated guide on the best questions to ask your interviewer. And remember: the goal is genuine curiosity informed by research, never a list of clever questions performed to impress.

Using your research in the room without overdoing it

There's an art to deploying research. Done well, it's invisible: you simply sound informed and engaged. Done badly, it's a performance, and interviewers can smell a recited book report. The principle: weave, don't dump.

• Let it surface naturally. Bring up what you learned when it's relevant to a question or your own question back — not in a pre-loaded monologue. If they ask why you're interested, that's the moment for a connection point. If they ask about your experience, that's the moment to tie it to their stated challenge.
• Specific beats comprehensive. One precise, well-placed observation ("I noticed your onboarding flow is unusually fast") lands harder than a sweeping summary of everything you read. Resist the urge to prove how much you found.
• Hold it lightly. Frame observations as impressions to be confirmed, not pronouncements. "It seems like…", "I got the impression that…", "Is that how the team sees it?" invites dialogue and leaves room to be corrected, which is far more attractive than false certainty.
• Don't fake depth you don't have. If you skimmed something, don't pretend you studied it. A confident "I read a bit about that but I'd love to understand it better from you" beats a shaky bluff that unravels under one follow-up.

A useful mental model is to treat your research as ammunition you keep holstered, not a speech you've memorized. You don't know in advance exactly which questions you'll be asked, so you prepare a small arsenal of specifics and deploy whichever fits the moment. If they ask about a challenge, you reach for the relevant thing you learned about their challenge. If they ask why this company, you reach for your connection points. If the conversation drifts to strategy, you reach for your read on their market. Preparation done this way feels effortless in the room precisely because it isn't scripted: you're responding to the real conversation with relevant, researched substance, which is exactly what genuine engagement looks like.

The test of good research isn't how much you mention; it's whether the interviewer comes away thinking "this person really gets what we're trying to do." That impression is built from a few well-placed specifics and the quality of your questions, not from volume. When in doubt, say less and aim it better.

A focused 2–3 hour research plan

You don't need a full day, and you shouldn't spend one; diminishing returns set in fast. Here's how to spend two to three high-value hours, in order, so the work compounds rather than scatters. Adjust the proportions to the stage: lighter for a first screen, fuller for a final round.

Notice that synthesis gets its own dedicated block at the end. That's deliberate: the reading is only raw material, and the value is created when you turn it into the three things you'll actually use. If you're short on time, protect the synthesis block above all else; thirty minutes of distillation beats an extra hour of undirected reading every time.

The company research worksheet

Use this fill-in template for every interview. Copy it into a blank document, complete it as you research, and you'll arrive with exactly the right material — nothing missing, nothing wasted. It mirrors the five layers and forces the synthesis that makes research usable.

COMPANY: ____________________   ROLE: ____________________
INTERVIEW DATE: ____________   ROUND: ____________________

— THE BUSINESS —
How it makes money: ________________________________________
Who its customers are: _____________________________________
Core problem it solves: ____________________________________
Trajectory (growing/mature/turning): ______________________
One-sentence understanding: ________________________________

— RIGHT NOW —
Recent news / launch / move: _______________________________
Funding / financial event: _________________________________
Leadership change: _________________________________________
What it implies for this role: _____________________________

— THE ROLE —
Why this role exists (the "why now"): ______________________
Must-haves → my best evidence:
  1) __________________ → ___________________________________
  2) __________________ → ___________________________________
  3) __________________ → ___________________________________
My first-90-days sketch: ___________________________________

— THE PEOPLE —
Interviewer 1: ________  role: ________  one note: __________
Interviewer 2: ________  role: ________  one note: __________
Genuine common ground (if any): ____________________________

— THE CULTURE —
Stated values: _____________________________________________
What reviews / employees suggest: __________________________
Gap to probe in the interview: _____________________________

— SYNTHESIS (what I'll actually use) —
Connection point A: ________________________________________
Connection point B: ________________________________________
Connection point C: ________________________________________
Questions to ask:
  1) _______________________________________________________
  2) _______________________________________________________
  3) _______________________________________________________
  4) _______________________________________________________

How to keep your research from going stale

If you're running an active search, you may research a company days or even weeks before you finally interview — and a fast-moving company can change in that window. Build a small habit of refreshing the most perishable parts the night before. The business model and the role's purpose rarely change quickly, so your one-sentence understanding and evidence map stay good. But the "right now" layer is perishable by definition: a launch ships, a leader moves, a funding round closes. A five-minute scan of the company's newsroom and your interviewers' recent public activity the evening before catches anything new and saves you from the worst kind of stumble: confidently referencing something that's no longer true. Treat your worksheet as a living document: fill it once, then top up the volatile rows just before you walk in.

It also pays to keep your filled worksheets after each interview, win or lose. Over a search you'll interview at several companies, and patterns emerge — the questions that keep coming up, the connection points that consistently land, the kinds of cultures that energize or drain you. That accumulating record makes each subsequent preparation faster and sharper, and it doubles as honest data about what you actually want, which is easy to lose sight of in the grind of a search. Good research compounds; don't throw it away.

The worksheet isn't busywork; it's a forcing function. By leaving blanks for the synthesis, it stops you from reading endlessly and never converting. If you can fill the bottom section confidently, you're ready. For the broader interview, pair this with our full interview preparation guide and a strong answer to the inevitable opener, "tell me about yourself."

Common company-research mistakes

These are the errors our coaches see most often. Each is easy to avoid once you know to watch for it.

1. Memorizing trivia instead of understanding the business. The founding year won't help you; knowing how they make money will. Chase understanding, not facts.
2. Stopping at the homepage. The homepage is marketing. Layer it with news, reviews, the posting, and real product use to get a true picture.
3. Citing stale information. Praising a sunset initiative or a departed leader signals you didn't really look. Verify currency before you reference anything.
4. Ignoring the role to research the company. The job posting is your richest document. Don't neglect it while you read corporate news.
5. Forgetting to prepare questions. "What questions do you have?" is part of the test. Walking in without sharp, researched questions wastes your best chance to shine.
6. Dumping research as a monologue. Reciting everything you found is a performance, not a conversation. Weave specifics in naturally.
7. Over-studying the interviewers. Useful context is good; reciting someone's profile back is unsettling. Keep it light.
8. Trashing competitors. Knowing the landscape is smart; disparaging a rival is unprofessional and can backfire.
9. Taking the careers page as gospel on culture. Triangulate across sources; never trust a single self-published signal.
10. Researching everything, synthesizing nothing. Notes you never convert into talking points and questions do no work in the room. Always end with synthesis.

A full worked example: posting to prepared candidate

Let's run the entire method on one realistic scenario so the moves stick. You can apply the identical process to any interview you have.

The scenario

ROLE: Customer Success Manager — Lumen (B2B scheduling software)
ROUND: First-round video interview with the Head of CS and a peer CSM
POSTING HIGHLIGHTS:
- Own a portfolio of mid-market accounts
- Drive adoption, retention, and expansion
- 3+ years in SaaS customer success
- Comfortable with data and QBRs (quarterly business reviews)
- Bonus: experience moving upmarket from SMB to mid-market

Layer 1 — The business

From the website and a free trial: Lumen sells subscription scheduling software to service businesses, charging a monthly fee per location. Customers are owners and operations leaders who want to fill calendars and cut no-shows without hiring admin staff. One-sentence understanding: "Lumen sells per-location subscription scheduling software to service businesses, helping them fill calendars and reduce no-shows." The trial revealed a fast, friendly onboarding but a slightly clunky reporting view — both authentic talking points.

Layer 2 — Right now

Recent posts and a funding announcement show Lumen raised growth capital and is pushing from small businesses into larger, multi-location "mid-market" customers. A new VP of Customer Success joined two months ago. What it implies: this CSM role almost certainly exists to support the move upmarket, and the new VP is likely reshaping how the team works — change-readiness will matter.

Layer 3 — The role

First-90-days sketch: "Learn the current account health data, identify the mid-market accounts most at risk and most expandable, and build a simple playbook for the upmarket segment the team is growing into."

Layer 4 — The people

The Head of CS has been at Lumen four years and writes about customer-led growth — likely to probe retention philosophy and how I think about expansion. The peer CSM joined recently from another SaaS company; a good person to ask honest questions about the day-to-day. Common ground: we both came up through SMB support before moving into success — a natural, light point of connection.

Layer 5 — The culture

Stated values emphasize "customer obsession" and "moving fast." Employee reviews echo a fast pace and praise the team, with a recurring note that processes are still maturing — consistent with a company scaling upmarket. Gap to probe: ask how the new VP is bringing structure to a fast-moving team, which is both genuine and shows I read the situation.

Synthesis — what walks into the room

• One sentence: per-location subscription scheduling for service businesses, reducing no-shows.
• Connection points: (1) "You're moving upmarket — I led my last team's first push into multi-location accounts." (2) "I saw the new VP joined recently; I've thrived through exactly that kind of scaling and restructuring." (3) "I tried the product — the onboarding is fast, and I have thoughts on the reporting view that ties to driving adoption."
• Questions: "How is the mid-market push changing what success looks like for this role?" · "What's the new VP prioritizing as the team scales?" · "What's the hardest part of moving customers from SMB to mid-market for you?" · "What would a great first ninety days look like?"

That's a candidate who will clearly sound like they already understand Lumen's business, its moment, the role's purpose, and the people across the table — assembled in well under three hours, and far more compelling than any amount of memorized trivia. Pair this with sharp answers to the predictable questions, and you're ready; our guides on the questions to prepare for and the broader interview preparation playbook cover that half.

The pre-interview research checklist

Run this the day before any interview. It's the same parse-then-prepare discipline our coaches apply before every member's interview.

• One-sentence test. You can explain how the company makes money and for whom, in plain language, without notes.
• Currency check. You know at least two current, relevant things happening at the company right now — and you've verified they're not stale.
• Role mapped. You've re-read the posting and matched your best evidence to each must-have, with a first-90-days sketch.
• People noted. You know who you'll meet, their roles, and one useful note on each.
• Culture triangulated. You have an honest read on fit from several sources, plus a gap you want to probe.
• Product tried. Where possible, you've used the product and have a specific, authentic observation.
• Three deliverables ready. One-sentence understanding, two or three connection points, and at least four researched questions — written down.

The company isn't testing whether you memorized their About page; they're testing whether you understand their business and genuinely want to help build it. Get the understanding right and the questions sharp, then let your specific, well-placed insights do the convincing. If you'd rather not run this on every interview alone, that's the entire point of Marqee: real career experts find the roles, run recruiter outreach, surface warm referrals, brief you on each company, and rehearse your answers with you — so you become a marquee candidate the people who hire can't overlook. Explore interview preparation, see real member results, or browse more in the guides library and the blog.

Frequently asked questions