Why do you want to work here? How to answer with research

Why interviewers ask this question

Hiring managers use this question to filter out candidates who are applying everywhere without much thought. They want to know whether you understand what the company actually does, whether your reasons for joining are likely to keep you engaged, and whether you have thought about how your work fits into a larger picture.

A weak answer signals low motivation and raises the risk that you will leave quickly. A strong answer signals that you researched the role, that you have a reason to stay, and that you can connect your skills to the company's current situation.

What to research before you answer

You need at least three concrete facts about the company before you can give a credible answer. Surface-level information from the homepage is not enough. Go deeper.

• Recent news: product launches, funding rounds, acquisitions, or expansions in the past six to twelve months
• The company's stated strategy: annual reports, investor letters, or the CEO's public interviews often spell out priorities clearly
• The team or department you are joining: LinkedIn profiles of your potential manager, recent blog posts from the engineering or product team, or published case studies
• Customer or user problems the company is trying to solve: look at reviews on G2, Trustpilot, or the App Store to understand what users value and what gaps remain
• The job posting itself: the specific language used for responsibilities and goals often reflects internal priorities that are not public elsewhere

A template that works

A reliable structure for this answer has three parts: what you noticed about the company, why that matters to you personally, and what you bring that is relevant to it. Keep the whole answer to ninety seconds or less when spoken aloud.

Template: 'I've been following [specific thing the company is doing]. That matters to me because [your relevant experience or goal]. I think I can contribute to that by [specific skill or past result].'

Example for a product manager role at a fintech company: 'I read that you launched a savings feature for gig workers last quarter and that it reached 200,000 users in three months. I spent two years building financial tools for freelancers at my last company, so I understand the irregular income problem from the inside. I'd want to work on the next iteration of that product and bring what I learned about onboarding drop-off in that segment.'

Notice that this answer contains no flattery. It contains a fact, a personal connection, and a forward-looking contribution. That combination is what makes it memorable.

Common mistakes to avoid

Most weak answers fall into one of four patterns. Knowing them helps you catch them in your own preparation.

• Complimenting the brand without evidence: 'You're one of the most respected companies in the space' sounds hollow without a specific reason
• Focusing only on what you want to gain: 'I want to grow my skills here' is about you, not about the company's needs
• Repeating the job description back: 'I see you're looking for someone with strong analytical skills and I have that' does not answer why this company
• Mentioning salary or benefits: even if compensation is a real reason, this is not the place to say so
• Vague culture references: 'I heard the culture is great' is unverifiable and forgettable

Adapting the answer by industry and country

The core structure stays the same across industries, but the research sources and tone shift depending on context.

In the US and Canada, public companies file quarterly earnings reports that are easy to read for strategic priorities. Startups often publish blog posts or appear on podcasts where founders explain their roadmap. In the UK, Companies House filings and the company's annual confirmation statement can reveal growth patterns. In Australia, the ASX announcements page is a reliable source for listed companies.

For government or public sector roles in any of these countries, the answer should connect to the agency's published mandate or a recent policy initiative rather than financial performance. For nonprofits, connect to a specific program outcome or a report the organisation has published.

For technical roles, referencing a specific engineering blog post, an open-source contribution the team made, or a technical talk a team member gave at a conference shows a level of research that most candidates skip.

Practising until the answer sounds natural

Writing a good answer is only half the work. Delivering it without sounding rehearsed takes practice. Record yourself on your phone and listen back. If you hear filler words like 'um' or 'basically' more than once or twice, the answer is not yet automatic enough.

Run through the answer at least five times before the interview. Change one or two words each time so it does not become a recitation. The goal is to sound like you are thinking it through in the moment, even though you have prepared it carefully.

Break-In Bad's interview assistant listens to the interviewer's questions in real time and shows you a suggested answer on screen that only you can see, even on a shared screen. If you have done the research but want a safety net for the live moment, that is what it is there for.

What to do if you genuinely do not know much about the company

Sometimes you get a last-minute interview and have thirty minutes to prepare. In that case, prioritise in this order: read the job posting carefully, read the About page and the most recent press release, and search the company name on LinkedIn to see what the team has been posting.

Thirty minutes of focused reading is enough to find one specific fact you can use. One specific fact is enough to build a credible answer. You do not need to know everything. You need to know one thing that is true, relevant, and connected to your own experience.