How to Answer “What Do You Know About Our Company?

Indeed frames the answer as a concise, role-relevant explanation of the company’s business, customers, recent activity, and connection to the vacancy. Build it from two or three verified points, use LinkedIn to confirm current role context, and deliver the core answer in roughly 45–90 seconds, the range Indeed recommends.

What should you say first when asked what you know about our company?

An opening answer can briefly explain what the company does, whom it serves, and one verified, current fact relevant to the vacancy. Indeed’s guidance

Use this spoken line:

“From the company’s [About or Mission page], I understand that [company] provides [product or service] for [customer or market]. I noticed [current development from the Newsroom or company blog], which matters to this role because the job description focuses on [responsibility or priority].”

Replace every bracket before the interview. Check the company’s About, Mission, Careers and Newsroom pages, then read the job description beside your notes. Choose two or three relevant points rather than trying to summarise the company’s entire history.

Keep company knowledge separate from “Why do you want to work here?” AceRound AI’s guidance

If asked about motivation, bridge cleanly:

“That priority is also what attracted me, because my experience with [relevant task] would let me contribute to it.”

Interview Pilot’s structure

What is the interviewer really checking in your answer?

The order matters. A polished answer built on an outdated launch still fails.

1. Factual accuracy comes first. Check the company’s current product, customers, ownership and developments before you speak. If sources conflict, do not guess. State the narrower fact you can verify.

2. Business and customer understanding comes next. Apply the “so what?” test to each point. If you mention a product launch, explain the customer problem it addresses. If you mention expansion, explain the business priority or risk behind it. Use that breadth to understand the business, not to recite research.

3. Role relevance makes the answer useful. Connect one verified fact to a responsibility in the job description. Compare company financials with a 10-K, annual reports and investor-relations materials ([What Do You Know About Our Company (What Do You Know About Our Company? How…)? How…](https://www.resumemate.io/blog/what-do-you-know-about-our-company-how-to-answer/)). Then check LinkedIn, Glassdoor, company blogs, press releases, local business journals, chamber-of-commerce listings, trade publications, customer reviews and independent reporting for context.

4. Motivation and delivery come last. Add a brief reason the priority interests you. Speak clearly. Do not let enthusiasm hide a weak fact or an absent role link.

Sacrifice extra facts before sacrificing accuracy or the role connection. Two reliable points beat a crowded answer that leaves the interviewer unsure what you understood.

Keep your preparation notes wider than your spoken answer. The cited 47%, 77%, and 31% figures are not accompanied by direct methodology in the supplied material. Treat them as unverified context, not evidence of hiring outcomes. How…](https://blog.theinterviewguys.com/what-do-you-know-about-our-company/))? How…](https://blog.theinterviewguys.com/what-do-you-know-about-our-company/)). Aim to build your answer from evidence you can explain.

How long should the answer be for each interview setting?

Interview Pilot recommends 30–60 seconds; candidates can begin with a concise core answer and expand if the interviewer invites more detail.

Choose the answer length by interview setting

Interview setting	Start with	Add if invited	What to prioritise
Recruiter screen	A 20-second company snapshot and one role link	One current development after a follow-up	Basic relevance
Hiring manager interview	The 20-second core	The business priority closest to the job description	Team priority
Panel interview	The core and one useful fact	Detail for the panellist who follows up	A clear discussion point
Technical interview	The product, customer problem and role link	Technical or operational detail	Role-relevant priority
Executive or senior-leadership interview	The business model and market direction	Risk, growth signal and relevant experience	Strategic judgement

The 20-second core is this:

“In short, you help [customer] do [outcome]. I noticed [current fact], which connects to this role because [link].”

Deliver the company snapshot and one role link first. Add a current development only after the interviewer pauses, invites more detail or asks a follow-up. That prevents a recruiter screen from turning into a company-history recital.

Published guidance allows for different levels of detail, depending on the interview context. Resumemate recommends practising under 60 seconds, while AceRound AI and CareerTestPrep recommend 60–90 seconds; Indeed recommends roughly 45–90 seconds. Use those ranges as expansion options, not as a command to keep speaking.

If the interviewer interrupts, stop cleanly. Say:

“Of course. The short version is that [company] serves [customer] through [product or service], and I connected that priority to [role responsibility].”

If the interviewer nods without asking more, finish the sentence and stop. If they ask, “What else stood out?”, add one verified development. Do not force the prepared detail into the conversation.

What structure turns company research into a natural answer?

It combines the business, a current signal, your connection and a question.

Use this four-line sequence:

1. Company snapshot: what the business provides and who it serves.
2. Current signal: a recent development or verified business fact.
3. Role connection: why that fact matters to this vacancy.
4. Optional question: what you want to understand next.

“From what I’ve found, [company] provides [product or service] for [customer]. I was interested to see [recent development or verified business fact]. That matters to this role because [job-description duty or priority]. I’d be keen to understand [specific question].”

Build the evidence in layers. Start with the company About, Mission, Values, Careers and Newsroom pages. Add the job description. Then check LinkedIn, company blogs, press releases, local business journals, chamber-of-commerce listings, trade publications and customer reviews. For public companies, compare company financials, annual reports, investor-relations materials and the 10-K ([What Do You Know About Our Company (What Do You Know About Our Company? How…)? How…](https://www.resumemate.io/blog/what-do-you-know-about-our-company-how-to-answer/)). CareerTestPrep’s research plan provides one possible sequence for reviewing sources. AceRound AI also suggests consulting several sources and reviewing recent developments rather than relying on a mission statement alone.

Most interview guidance asks for a concise, structured answer. Interview Pilot recommends 30–60 seconds, while Resumemate recommends keeping the response under 60 seconds. That advice breaks down when an interviewer interrupts, moves quickly or gives you only an opening.

Do not treat 45–90 seconds as a fixed target. Build a 20-second core first, then add the role connection only when the interviewer gives you room.

For a private company, parent group or confusing division, name the exact entity you researched. Do not merge brands or guess figures. Say: “I found limited public detail on that division, so I focused on the customer problem and the responsibilities in this role.” Zippia and Harvard Business Review offer general framing rather than company-specific evidence.

What are strong example answers for different candidates?

Each answer below links one verified company point to evidence the candidate already owns.

Example: early-career candidate

“From my research, GreenPath provides energy-monitoring software for small businesses. I noticed the company recently added automated carbon reporting. In my university project, I analysed energy-use data and presented practical changes to a student housing team. That experience interests me because this role supports customers who need clear guidance, not just software features.”

If asked, “Why does that interest you?”

“I want to build stronger customer and data skills while working on a product with a clear practical use.”

This answer uses a customer, a recent service fact and a study project.

Example: experienced candidate

“I understand that Northstar Health serves hospitals with patient-management tools and is prioritising wider adoption across regional providers. In my current role, I led an onboarding redesign that cut average implementation time by 18% ([What Do You Know About Our Company (What Do You Know About Our Company? How…)? How…](https://www.resumemate.io/blog/what-do-you-know-about-our-company-how-to-answer/)). I would bring that experience to a team helping hospitals adopt the product consistently, while keeping the patient and operational needs visible.”

If asked, “Why does that interest you?”

“The priority matches work I have already delivered, but at a larger customer and operational scale.”

Use your own verified result here. Do not insert a company metric unless you have checked its date and source. STAR-format behavioural examples can provide the evidence behind this role connection.

Example: career-changer

“BrightCart runs an online marketplace for independent food producers. I noticed its recent focus on improving customer trust in delivery times. In retail operations, I resolved recurring order issues by mapping the customer journey and retraining the handover team. That experience gives me a useful starting point for helping BrightCart understand friction from the customer’s side.”

If asked, “Why does that interest you?”

“I am moving industries, but not abandoning the problem-solving work customers already rely on.”

Example: leadership candidate

“I understand that Vale Systems sells workflow tools to regulated businesses and is balancing growth with operational control. I have managed a £2 million service budget and introduced risk reviews across three teams (How To Answer “What Do You Know About…). I would bring that discipline to a business scaling without losing customer trust.”

If asked, “Why does that interest you?”

“The business priority is familiar, and the context gives me room to contribute at a strategic level.”

How should you adapt the answer to the role and likely reply?

Adapt the evidence, not just the wording.

• Recruiter screen: “I understand your core service, your customers and the priority mentioned in this vacancy.”
• Hiring manager: “Your team appears focused on [priority]. My experience with [relevant task] fits that need.”
• Panel: Offer one clear fact that gives each interviewer an opening to ask a question.
• Technical interview: Explain the customer problem, product constraint or operational priority.
• Executive interview: Discuss growth, market position, risk or strategy.

Administrative, hourly, operational and early-career candidates do not need strategy language. Use a customer-service standard, process improvement, reliability measure or safety priority instead.

Prepare these replies:

• “What specifically interested you?” “Your work on [verified detail] stood out because I have worked on [relevant task].”
• “How does that relate to this role?” “The job description emphasises [duty]. I can contribute through [evidence].”
• “What would you improve?” “I would first understand the team’s constraints. Then I would test [measured improvement].”
• “Where did you find that?” “I found it on your [page or release], supported by [independent source].”
• “Why us rather than a competitor?” “Your focus on [specific customer or capability] matches the work I want to do.”

For layoffs, lawsuits, poor reviews or negative news, stay factual: “I saw the verified report about [issue]. I do not want to assume the cause. How is this role supporting the stated priority?”

How do you practise saying the answer out loud in two minutes?

Use this two-minute drill:

1. Write three verified facts. Use the company’s current website, job description, LinkedIn or reliable reporting. That is a preparation list, not a script.
2. Select one core fact and one role link. Choose the fact that best explains what the company does, who it serves or what it is working towards. Add: “That connects to this role because [specific responsibility].”
3. Record one attempt from keywords. Do not memorise full sentences. Speak your answer in your own words.
4. Review five points: factual accuracy, clear company snapshot, credible role connection, natural pace and no unsupported praise.
5. Practise one interruption and one follow-up. Stop when asked, “What recent development caught your attention?” Then answer, “How would you contribute?” Return to the role link rather than restarting the whole answer.

A recording shows pace. A transcript shows missing detail. A human partner tests listening. Real-time interview copilots and AI interview assistants may affect interview preparation, but users should independently verify company facts and apply their own judgement.

If you freeze, reset with: “The short version is…”

Which answers should you avoid saying?

Avoid: “You’re a great company.” Repair it with one verified customer, product or market fact.

Do not recite the About page. Select two facts and connect one to the vacancy.

“I just need a job” explains your need, not your knowledge. “I researched you for hours” announces effort without showing understanding. Avoid claiming an outdated launch, confusing a parent company with its division, inventing a figure or presenting promotional copy as independent proof.

Treat The Interview Guys’ statistics as requiring verification rather than as evidence about hiring decisions.

“I would rather be accurate about two relevant points than list facts I cannot verify.”

Razen Rehearsal Sandbox: The 20-Second Company Answer in a Final Interview

It is Thursday at 10:00 in the final panel for a Senior Customer Operations Manager role at HarborLoop, a logistics software company. Maya has one chance to show she researched the business without reciting its website; Daniel and Priya will decide whether she advances after the last interview that afternoon.

Setting. A video interview with Maya, Daniel, the hiring manager, and Priya, the COO. The panel has 45 minutes and must assess Maya before the final candidate arrives.

Cast

• Maya, Job candidate and reader stand-in. At stake: She needs the offer but must sound informed, not rehearsed.
• Daniel, Hiring manager for customer operations. At stake: He needs someone who understands the role's immediate priorities.
• Priya, COO and second interviewer. At stake: She wants evidence that Maya connects company facts to operating results.

The Wrong Way

Daniel: Maya, to start us off, what do you know about HarborLoop?

(Daniel leans toward the camera and checks his notes. His tone is open but brief.)

Maya: Sure. I spent quite a bit of time researching you. HarborLoop was founded to make freight operations more efficient, and you serve retailers, manufacturers and logistics providers across several markets.

(Maya smiles tightly and speaks quickly, trying to sound prepared.)

Maya: I also saw the March announcement about self-serve onboarding, the customer advisory programme, the sustainability commitments, and the recent leadership changes. Your mission is to simplify movement of goods, and your values include ownership, curiosity and transparency.

(She keeps going without checking either interviewer’s reaction. Her hands move in small circles.)

Priya: Sorry, which part of that connects to this job?

(Priya raises one hand and looks from Maya to Daniel.)

Maya: Yes, absolutely. I mean, the onboarding release is obviously very relevant, and I have experience with customer journeys, process mapping, stakeholder management, training, reporting, and improving adoption, so I thought that was a strong fit.

(Maya nods too often and piles up examples without naming one result.)

Daniel: What would you actually focus on in your first few months?

(Daniel glances at the job description and shortens his question.)

Maya: I’d want to understand the whole operation first. I’d speak with sales, product and support, review the data, map the process, and then identify quick wins. There are quite a few things I’d want to look at.

(Her voice drops at the end. She avoids Priya’s camera tile.)

Priya: All right. We need to cover your experience with escalations next.

(Priya closes her notebook, signalling the topic has ended.)

Why it fails. Maya uses the competent preparation tactic of listing several researched facts, but her opening gives no clear customer outcome or role link. The line about the mission and values adds company copy without showing why the onboarding release matters to this vacancy. When Priya asks for the connection, Maya adds a list of skills instead of one relevant operating priority, so the panel has to redirect her.

The Right Way

Daniel: Maya, to start us off, what do you know about HarborLoop?

(Daniel leans toward the camera and gives Maya the floor.)

Maya: In short, you help retailers and manufacturers manage freight operations with software that gives teams better control of shipments and customer updates.

(Maya plants both feet, looks at Daniel’s camera tile, and speaks at an even pace.)

Maya: I noticed the March self-serve onboarding release. That connects to this role because the job description puts implementation speed and customer adoption at the centre.

(She pauses briefly after “release” and lets the role link land.)

Priya: What specifically interested you about that release?

(Priya leans forward and gives Maya a clear opening to add one layer.)

Maya: It suggests the team is trying to remove friction before customers need human support. In my last role, I used onboarding data to find where accounts stalled, then changed the handoff process.

(Maya keeps one hand still on the desk and gives the example without rushing.)

Daniel: Where did you find the information about implementation speed?

(Daniel points to the job description on his screen.)

Maya: That part came from the job description. The product detail came from your March newsroom post, so I kept those two points separate rather than guessing at a target.

(She holds Daniel’s gaze and gives a small nod on “separate.”)

Priya: Good. Let’s talk about how you’d handle an account that stalls during onboarding.

(Priya makes a note and moves the interview into a concrete scenario.)

Why it lands. Maya starts with a 20-second company snapshot, then adds one verified fact only after the panel invites more detail. She pays a real price by leaving out the leadership changes, values and other research she prepared. That restraint gives Daniel and Priya a useful question, and her answer shows exactly how the company fact connects to the job.

<aside class="razen-coach-card" data-razen-scenario="the-20-second-company-answer-in-a-final-interview"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-20-second-company-answer-in-a-final-interview&amp;article=how-to-answer-what-do-you-know-about-our-company&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=how-to-answer-what-do-you-know-about-our-company">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start briskly and factual for the company snapshot; shift to a warmer, more specific tone when explaining why self-serve onboarding matters.
• If Priya interrupts, lower your pitch and shorten the next sentence instead of speeding up to finish the prepared answer.
• When naming the job-description link, sound definite; when separating the newsroom fact from the role priority, use a measured, careful tone.

Pause placement

• Pause for 1 second after “freight operations” so the customer and outcome are easy to follow.
• Pause for 2 seconds after “March self-serve onboarding release” before giving the role connection.
• If asked what interested you, pause for 1 second after the question and choose one operating implication, not another company fact.

Physiological cues

• Before answering, exhale once and press both feet into the floor; do not let your hands start listing facts in the air.
• Keep your jaw loose after saying “In short,” and look at the hiring manager’s camera tile until the first sentence ends.
• When Priya asks where the information came from, keep one hand flat on the desk and suppress the urge to smile apologetically.

Recovery moves

• If you start listing facts, say: “Let me make that relevant to this role. The short version is that onboarding is the priority I found most connected to the job.”
• If you lose the thread, say: “The short version is: you help these customers manage freight operations, and this role supports adoption of that product.”
• If you quote an uncertain detail, say: “I don’t want to overstate that. The point I could verify is the March onboarding release, and its relevance here is customer adoption.”
• If the panel interrupts before your role link, say: “Yes, that is the link I was coming to: the release matters because this role is responsible for smoother implementation.”

Watch it explained

Frequently asked questions

What is the best length for “What do you know about our company?”

Use a short core answer first, then expand if the interviewer gives you space.

How many facts should I include?

Prepare more facts than you say. Resumemate recommends selecting two or three meaningful points, while The Interview Guys suggests recording several possibilities during research before narrowing them down. In the spoken answer, use one or two verified facts and connect at least one to the role.

Should I answer “Why do you want to work here?” too?

Answer the company-knowledge question first. State what the business does, who it serves and one current priority. Then add a brief motivation link only if it sounds natural or the interviewer asks why the information interests you.

What if I know very little about a private company?

Do not bluff. Use the company’s public site, job description, LinkedIn, press releases, trade publications and customer evidence. Say, “I found limited public detail, so I focused on your customer problem and the responsibilities in this role.”