How to Answer "Why This Company?" in an Internship Interview
"So, why us?" The honest gut answer is "because you're hiring," and you can't say that. But you don't need a passion you don't have. Twenty minutes of the right research plus a three-part answer shape turns that panic into something specific you can say out loud. Below you get the timed research checklist, the formula, and two full worked examples built from a thin resume, so your answer sounds like you did the homework instead of skimming the About page.
What this question is really testing
When an interviewer asks "why do you want to work here," they're not fishing for compliments. They're checking three quiet things: that you know what the company actually does, that you understand what the role does day to day, and that you're not spraying the same application at fifty companies and hoping one lands.
The answer they screen out is the one that fits any company. "I love your mission and I want to grow with a great team" could be pasted into a hundred interviews without changing a word. That's the tell. If your answer would still make sense with the company's name swapped out, it isn't answering the question. The whole game is to say something that could only be about them.
The 20-minute company-research method
You don't need hours. You need twenty focused minutes and a place to jot four notes. Here's the timed checklist. Run it the night before, or in the parking lot if that's the situation you're in.
The product or service (5 min)
Open their site and answer three plain questions: what do they sell, who buys it, and how do they make money? A B2B analytics tool sells to companies, not consumers. A consumer app might make money on ads or subscriptions. Get it clear enough that you could say one sentence out loud: "You make scheduling software that restaurants use to build staff rosters." That sentence is your foundation. If you can't say it, you're not ready.
The team and the role's day-to-day (5 min)
Reread the job description, but read it for the tasks, not the buzzwords. What would you actually be doing on a Tuesday? "Build internal dashboards," "write test cases," "draft social copy." Then skim the team's public footprint: an engineering blog, a few people's LinkedIn, whatever shows what the work touches. You're looking for one concrete detail about the day-to-day you can name back to them.
Recent news (5 min)
Find one recent thing: a product launch, a funding round, a feature update, a blog post, a news article. Google News and the company's own blog are the fastest routes. This single detail is what makes an answer sound current instead of generic, because almost nobody bothers to find it. "I saw you shipped the new mobile app in the spring" instantly signals you looked past the homepage.
The honest reason it fits you (5 min)
Now connect one thing you found to something you've actually done or want to build. Not a grand narrative. One real link. The dashboard task connects to the data project you did for a class. The recent app launch connects to the side project you've been tinkering with. This is the beat that makes the answer yours, and it's the one students skip because it feels too small. It isn't.
The 3-part answer formula
Every strong answer to "how to answer why this company" runs three beats, in this order.
- What drew you. A specific hook, not "your mission." Point at the product, the news, or the role detail you found. Something concrete.
- Proof you did the homework. Name it. The feature, the recent launch, the actual task from the job description. This is where you spend the twenty minutes of research.
- How it fits your path. The honest connection to a class project, a club role, or something you want to learn. End here, on you and the role.
Aim for roughly 30 to 60 seconds, which is two or three sentences per beat, not a monologue. Here's the fill-in skeleton:
"What first caught my attention was specific product, feature, or recent thing. One sentence naming the detail you found, so they know you looked. That connects to your class project, club role, or goal, and this role is where I'd get to what you'd learn or do here."
Note that this is a different beat from the "why this role" line in your tell me about yourself opener. That one is a quick bridge inside your self-introduction. This is the full, standalone answer when they ask the motivation question directly.
Two worked examples (thin resume)
Both examples below build the answer from coursework and clubs, no work history required. Companies are hypothetical, and any detail is illustrative. Yours will use the real thing you found in your twenty minutes.
Example 1: a CS student, software internship
"What first caught my attention was that you shipped the new mobile version of your scheduling app this spring, and I actually went and tried the free tier to see how the shift-swap flow worked. what drew me + proof The reason it clicked for me is that last semester I built a small class-scheduling tool for a course project, and the hardest part turned out to be handling conflicts when two things overlapped, which is basically the problem your app solves at scale. This internship is where I'd get to see how a real team handles that instead of my one-off version. how it fits"
The hook is a specific recent launch, not the mission. The proof is that the student actually opened the product. The fit is one honest class project that maps to what the company does.
Example 2: a marketing student, marketing internship
"The thing that drew me in was your back-to-campus campaign this year, the one built around student ambassadors posting their own dorm setups. I noticed it because I run the Instagram for my film society, and it was the opposite of my by-feel approach. what drew me + proof Taking over that account taught me how much a posting schedule matters versus just posting when I remember, and I've been wanting to learn how a real team plans a campaign like yours with a calendar and actual data behind it. This internship is exactly that step. how it fits"
Same three beats, different field. The hook is a specific campaign the student saw. The proof is that they noticed why it worked. The fit comes from a club role, not a job.
What to cut (the "don't recite the About page" tell)
The fastest way to sound generic is to add the wrong things. Cut these:
- The mission recital. Quoting the mission statement back at them ("your mission to democratize X inspires me") is the single clearest tell that you read the homepage and nothing else.
- Vague flattery. "You're a leader in the space" and "you have such a strong culture" fit any company and prove nothing.
- Anything company-swappable. Run the test: would this sentence survive if you replaced the name? If yes, cut it.
- The long backstory. "Ever since I was young I've been passionate about..." burns your 60 seconds before you've named a single real detail.
Keep exactly two things: one specific, verifiable detail you found, and one honest personal connection. That pair beats five paragraphs of enthusiasm every time.
Frequently asked questions
How do you answer "why are you interested in this internship"?
Use the same three beats, but lead with the role's day-to-day instead of the brand. "Why this internship" is really "why this role," so open on a task from the job description you're genuinely drawn to, name the proof that you understand what the work involves, then connect it to something you've done. The company-level version leads with the product or news; the role-level version leads with the work itself.
How long should your "why this company" answer be?
Roughly 30 to 60 seconds. Think two or three sentences per beat, not a monologue. Long enough to name a specific detail and an honest connection, short enough that you're not still talking a minute and a half later. If it runs long, you're probably padding with flattery you should cut.
What if you applied to a lot of companies and don't have a strong reason?
You only need one honest, specific reason, not a life-defining passion. Applying widely is normal, and interviewers know it. Run the twenty-minute checklist and find your one real hook in the product or the role: a feature you'd actually use, a task you'd genuinely like to learn. One true detail beats a fake grand narrative.
Should you mention the company's mission?
Only if you tie it to something concrete you've actually done. A naked mission quote is exactly what they screen out. "Your mission to cut food waste maps to the leftover-tracking app I built for a hackathon" works because it's anchored in a real thing you made. "Your mission inspires me" on its own does not.
How do you research a company quickly before an interview?
Run the twenty-minute checklist above: five minutes on the product and how they make money, five on the role's day-to-day tasks, five on one piece of recent news, and five connecting a detail to your own work. That's the whole method for how to research a company before an interview when you're short on time.
Close
Before your next screen, run the twenty-minute checklist and write your three beats on one notecard: what drew you, your proof, and the honest fit. Say it out loud once so it sounds spoken instead of read. The same research pays off twice, because it also fuels the smart questions you ask them at the end. For the wider set of prompts you'll face, keep the internship interview questions guide handy, and remember this question often opens the recruiter phone screen too. Then keep the interviews coming: browse internships and get more reps at saying it for real.