Most candidates answer this question by reciting what's on the About page. Founded in whatever year. Headquartered wherever. "A leading provider of X." They say it confidently, the interviewer nods, and then both people in the room know exactly what just happened: the candidate read the homepage twenty minutes before walking in.
The question isn't asking you to prove you can find a website. It's asking whether you've thought carefully enough about this company to know why you're sitting in front of them. Those are completely different things. And interviewers — especially experienced ones — can tell the difference in about four seconds.
Here's what the question is actually measuring, and how to answer it in a way that doesn't sound like a Wikipedia summary.
What interviewers are actually checking
This question isn't a knowledge test. It's a preparation test. And preparation is a proxy for something more important: genuine interest.
When an interviewer asks "what do you know about our company?" they're trying to figure out whether you want this job specifically, or whether you want a job and this one happens to be on the list. That distinction matters to them more than you might expect. Candidates who genuinely want this role tend to stay longer, engage more fully, and care more about the outcome of their work. Generic candidates leave the moment something better comes along.
The second thing they're checking is whether you've connected your research to them — not just accumulated facts about them. A candidate who says "you recently expanded into the EU market, and that's where my background in international logistics becomes relevant" has done something qualitatively different from a candidate who knows the founding year. One has thought about the company's problems. The other has done homework.
If you've been thinking carefully about why do you want this job, this question is its natural companion. The same research that fuels a strong motivation answer is what makes this one convincing.
The four-layer research framework
This is the structure that separates a memorable answer from a forgettable one. Four layers, in order of priority.
You don't need all four layers in every answer. Layers 1 and 2 are non-negotiable — if you can't cover those, you haven't done enough research. Layers 3 and 4 are what takes a good answer to a great one.
The structure of a strong answer
A well-structured answer to this question runs 60–90 seconds and covers three things: what the company does, something specific you've noticed about where they're going, and why that makes this role interesting to you. In that order.
Here's what that sounds like in practice:
"You're a B2B SaaS company focused on compliance automation for financial services firms — so your customers are mainly mid-market banks and insurers who are drowning in regulatory documentation. What caught my attention in your recent announcements is the move into real-time monitoring — the shift from point-in-time reporting to continuous oversight. That feels like a much harder and more interesting problem than what most of your competitors are solving. For me, that's specifically interesting because my background has been in building the kind of data pipelines that would sit underneath something like that."
Notice what's there. The core product and customer in one sentence. A specific recent development they've been public about. A genuine connection between that direction and the candidate's own background. And no hollow praise, no vague adjectives, no founding year.
The end of your answer should open a door, not close one. Finish with something that invites a response: "I noticed you recently expanded into X — can you tell me more about how that's affecting this team's priorities?" That turns a recitation into the start of a real conversation. And it hands the momentum back to the interviewer having just shown them you're actually thinking about their business.
How to research a company in 45 minutes
The practical problem with this question isn't that candidates don't know they should research — it's that they don't know what to actually look at or how long it should take. Here's a concrete 45-minute sequence.
Minutes 1–10: the company website
Go to their homepage, their product pages, and their About or Mission page. You're looking for: what they sell, who their stated customers are, and what language they use to describe their own work. The language matters — it tells you the vocabulary they use internally, which you can mirror in the interview without sounding like you're reading from a script.
Minutes 11–25: recent news
Search their company name in Google News and filter to the past 12 months. Separately, check their LinkedIn company page — specifically their posts, not just their profile. LinkedIn posts often contain announcements that don't make it into press releases. You're looking for: new products, partnerships, funding, expansion, or any public challenge they've been honest about. One specific thing from this layer is worth ten generic things from the homepage.
Minutes 26–35: growth signals
For startups and scale-ups: check Crunchbase for their funding history. Is it recent? Is it growing? Have there been layoffs listed on Layoffs.fyi? For public companies: skim the most recent annual report or investor update — not the financials in detail, just the CEO's letter and the priorities section. For any company: look at their open roles on LinkedIn. If they're hiring fifteen engineers, they're in a growth phase. If all their open roles are in support, that's different information.
Minutes 36–45: team and culture
Glassdoor, but ignore the overall score. Scores get gamed. Read the most recent written reviews — look for patterns in what multiple people mention. If four different reviewers in the past year mention poor cross-team communication, that's real. Also look at the LinkedIn profiles of your likely interviewers if you know who they are. Understand their background, how long they've been at the company, what they came from.
Forty-five minutes. Done properly, that's enough. And it puts you ahead of the majority of candidates who spend their prep time rehearsing answers to behavioural questions they've heard before.
What to do when you can't find much
Here's the counterintuitive part: when a company has limited public information, look at their job postings before you look anywhere else.
This sounds wrong. Most candidates treat job postings as a source of information about the role they applied for, not the company. But job postings are one of the most honest signals a company produces. They tell you what problems the company is trying to solve right now, what skills gaps they're carrying, and where they're betting their next phase of growth.
A startup with six engineering roles open and one sales role is in a very different place than a startup with six sales roles open and one engineering role. A company posting heavily for customer success managers is facing a retention challenge. A company posting for data infrastructure roles is about to try to do something that requires a lot of data. None of that is on the About page. All of it is in the postings.
For small companies — under fifty people — job postings may be the richest public signal you can find. Their press coverage is thin, their LinkedIn updates are inconsistent, and there are maybe three Glassdoor reviews from people who left two years ago. The postings are live and current. They tell you where the company's attention actually is.
This approach also gives you something unusually specific to say in the interview: "I noticed you're hiring heavily in customer success right now — what's driving that?" That's a question only someone who did more than read the homepage could ask.
What NOT to say
This is the textbook About page answer. "Founded in 2012, headquartered in Berlin, operating in fourteen countries." It tells the interviewer you found the Wikipedia page and nothing more. Historical facts without analytical connection to why you're there signal shallow preparation.
"You're a really innovative company with a strong culture." Every candidate at every company says some version of this. It means nothing without something concrete attached to it. If you're going to say something positive about the company, name the specific thing you read that convinced you of it.
Interviewers wrote that mission statement, or they've heard it repeated so many times it's white noise. Reading it back to them is not research — it's a signal that you couldn't find anything more interesting to say. Paraphrase it in your own words if you reference it at all, and only as a launch pad for something more specific.
"I know you have around 500 employees and did $40 million in revenue last year." This is the financial version of the founding year problem. Facts without insight. If you're going to reference a number, connect it to something: what it suggests about their trajectory, what it means for the team you're joining, why it makes the role you're applying for important right now.
What easedit.co coaching data shows
In easedit.co interview sessions, the company knowledge question produces a specific pattern that's hard to miss: candidates who haven't researched the company don't just give a weak answer to this question — they give weaker answers to every question that follows it.
That's not a coincidence. The preparation you do before walking into an interview doesn't just fill in knowledge gaps. It changes how you think during the interview itself. Candidates who've researched the company deeply are more confident, more specific, and more likely to connect their answers back to the company's actual situation. Candidates who haven't done the research are on the defensive from this question forward — trying to recover rather than demonstrate.
The second pattern: candidates consistently underestimate how much this question signals about their motivation. Interviewers don't just score the factual content of your answer. They use it to calibrate how much you want this specific job. A candidate with detailed, specific, connected knowledge of the company is someone who thought carefully about whether to apply. A candidate who stumbles through the About page is someone who applied to forty roles and this one was on the list.
That calibration affects how interviewers weight everything else you say in the room. It connects directly to why smart candidates still fail interviews — and to questions to ask at the end of an interview, where that same company research gives you specific, intelligent questions that land very differently from generic ones.
The actual substance of your research matters less than what it signals. Forty-five minutes of focused preparation tells the interviewer that you took this seriously — that you considered whether this company was worth your time before walking in, which implies you think carefully before acting. That's not a small signal for a hiring manager who needs to trust you with their clients, their budget, or their team.
One specific fact you found and connected to the role will do more for you than everything on the About page combined.
At easedit.co, you can practise this question — and every other common interview question — with a voice AI that reads your actual CV and the job description before the session starts. It doesn't coach you with generic advice. It challenges you based on your real background against a real role. Practise your interview — from $39, no data stored.