What Do You Know About Our Company Answer: Three Facts

The interviewer is not testing whether you memorised the website. They are checking three things: that you made a real effort, that you understand what the company actually does today, and that you can connect it to the job in front of you. A good what do you know about our company answer is short — 45 to 60 seconds — and built from three facts, each tied to the role. Here is how to choose those facts, where to find them, and what to say when you have had almost no time to research.

What is the interviewer actually testing?

They are listening for effort and genuine interest, not encyclopaedic knowledge. A short, accurate answer beats a long recital every time, because it shows you can prioritise. They also want to see whether you can link what the company does to the role you applied for — that is the part most candidates skip.

Underneath, they are checking whether you understand the company's customers and current priorities. Founding date and mission-statement wording tell them nothing about that. What the company sells, who buys it, and what it is trying to change this year tell them a lot.

Set your own target before you practise: three points, 45 to 60 seconds, one closing question. That shape keeps you concise and gives the interviewer something to follow up on, which is exactly what you want early in an interview.

The three-fact structure for your what do you know about our company answer

Three facts, in this order, do the job.

What the company actually sells or does, in plain language, in one sentence and in your own words. If you cannot explain it without jargon, you do not understand it yet.
Something current — a product, a market, a stated priority — that shows you looked past the homepage. This is the proof of effort.
The bridge: why that context makes this role matter, and what you would want to contribute. This is where most answers stop short, and it is the part the interviewer remembers.

Here is a fill-in-the-blank template you can adapt:

"From what I've read, [the company] helps [customer] to [outcome] through [product or service]. What stood out to me recently was [current thing — a launch, a market move, a stated priority]. That matters for this [role] because [the problem it creates or the work it implies], which is the kind of work I've done when [brief, true example]. I'd be curious how [one genuine question about the team or the priority]."

Keep the brackets as notes, not a script. The wording should sound like you on the day.

Where to look so your facts are specific

Skip the About page as your main source. Prioritise material that shows current priorities:

Recent announcements — launches, expansions, partnerships, leadership changes. These show what the company is betting on now.
Product pages — what it sells, who it is for, and how it describes the problem. Read two or three, not all of them.
Job postings for the team you are joining — they describe the work in the company's own words and hint at what the team is building.
Public customer stories or case studies — the clearest window into who the customer is and what they care about.

Then reread the job description and note which company facts it implies. If the posting mentions a new market, a migration or a customer segment, those are the facts to mention, because they connect directly to the role.

A 20-minute research checklist

Use this when time is short. Twenty minutes is enough for three facts.

One fact about the product: what it is and who it is for, in one sentence you could say aloud.
One fact about the customer: who buys it and what problem it solves for them.
One fact about a recent change: a launch, a new market, a stated priority from the last few months.

What to skip: the founding story, the exact wording of the mission statement, and anything you cannot explain in your own words. If you cannot paraphrase it, you cannot defend it if they ask a follow-up.

Worked example: a weak answer and a stronger one

Here is a weak answer for a fictional company, Northwind Logistics, a software provider for regional freight operators.

"You were founded in 2011 and you value innovation and customer focus. You've grown a lot and you care about your people. I really admire the culture and I think I'd fit in well."

It recites the About page, links nothing to the role, and could be said about any company. The interviewer learns nothing about your understanding.

Now a stronger answer, at about 50 seconds:

"From what I've read, Northwind gives regional freight operators software to plan routes and track shipments in one place. What stood out recently was your push into same-day delivery scheduling for smaller carriers — it looks like you're going after customers who've been priced out of the bigger platforms. That matters for this support role because those customers are often switching systems for the first time, so the first few weeks of onboarding decide whether they stay. I've spent most of my career helping small businesses through exactly that kind of switch, and I'd want to understand how your onboarding team measures a successful first month. Is that something the support team owns?"

Why it works, fact by fact:

Fact one (what it does): a plain-language description of the product and customer. It proves you understand the business, not just the brand.
Fact two (what is current): the same-day scheduling push. It shows you looked beyond the homepage and know what the company is prioritising now.
Fact three (the bridge): it connects that priority to the support role and to your own experience, without overclaiming.
The closing question: it invites a real conversation and shows interest in how the team works.

A shorter variant for a career changer

If you are moving into a new industry, lean on the bridge and keep the facts modest.

"I'm newer to logistics software, so I focused on what Northwind sells and who it serves: planning and tracking tools for regional freight operators, with a recent push into same-day scheduling for smaller carriers. That tells me the customers are often small teams making a first big software decision. In my previous work in retail operations I was usually the person walking a small team through a system change, so that's the part of this role I'd expect to lean into. I'd like to understand what a typical onboarding looks like here."

Being honest about what you did not know, and specific about what you did, reads as confidence rather than a gap.

What if you have done very little research?

Be honest about the limits without apologising. Say what you do know and what you looked into, then use what the interview itself has told you — the role, the team, the problem they described in the first few minutes.

"I'll be straight: I only had time for a quick look, so I focused on the job description and your product pages. What I took from them is that [the company] is solving [problem] for [customer], and this role sits close to that. I'd rather ask you than guess: what does success look like in the first six months?"

Turning a gap into curiosity works because interviewers would rather hear an honest question than a shaky recital. It also gives them a chance to talk, which usually relaxes the room. For more on keeping your wording natural when you are thinking on your feet, see our guide on how to sound natural with talking points in a job interview.

The three most common mistakes

Reciting the About page word for word. It signals preparation without understanding. Fix: replace any sentence you copied with one you would say to a friend, and cut it if you cannot.

Listing facts with no bridge to the role. The interviewer cannot see why the facts matter. Fix: after each fact, add one sentence starting "That matters for this role because…".

Overclaiming. Saying "I've followed you for years" when you have not is easy to check and hard to recover from. Fix: keep every statement true and specific — "I read your recent announcement about…" is stronger than vague admiration.

A good answer also depends on clear delivery. If you want a framework for structuring spoken answers, our guide to communication interview questions covers the patterns that hold up under follow-up questions.

How to practise this answer out loud in 15 minutes

Write the three facts as bullet points, not a script. Bullets keep the wording fresh; a script makes you sound recited.
Say it aloud twice. Then cut anything that sounds like a press release.
Record yourself or practise with a person. Check the time — aim for under a minute.
Rehearse the closing question so it sounds like a real question, not a line you memorised.

If you want a structured way to review your own practice runs, our AI Interview assistant guide explains how to prepare honestly and use feedback well.

Before you walk in

Your answer is three facts and a bridge, said in under a minute. Your next step: choose one company you are interviewing with, spend twenty minutes on the checklist above, and say your three-fact answer aloud once. If it runs past a minute, cut the weakest fact, not the bridge.

Frequently asked questions

How long should the answer be if the interviewer seems to be short on time?

Aim for about 30 seconds: one sentence on what the company does, one current fact, and one line connecting it to the role. Drop the closing question if the interviewer is clearly moving fast. Short and specific still shows effort, and you can offer more detail if they ask.

What if the company is small or private and there is almost nothing online?

Look beyond the company's own site. Local business press, the LinkedIn pages of the team you would join, customer reviews on marketplaces, and conference talks by staff often reveal more than the homepage. Pull one detail from any of these, say where it came from, and ask how it matches the team's current focus.

Should I mention something negative I found, like a recent layoff or a bad review?

Usually not in this answer. The question is about what you understand, not what you think is wrong. If a recent change affects the role, you can refer to it neutrally and ask how the team has adapted. Save critical questions for later stages, and keep your tone curious rather than judgemental.

Is it okay to say I looked at their careers page and job description as my main sources?

Yes, as long as you turned them into insight rather than repeating them. Say what the posting told you about the team's priorities and connect it to the role. Naming your sources is honest; just make sure you add a conclusion the interviewer could not have read on the page.

What if they ask this for a company I am interviewing with through a recruiter and know little about?

Send the recruiter a short message before the interview: ask for the company name, the team, and what the hiring manager most wants solved in the first six months. Their reply often gives you two usable facts. If they cannot share it, say so plainly and ask the interviewer one specific question about the team.

Practise your three-fact answer out loud and review how it lands.