What they're really testing
Risk, not curiosityInterviewers ask this to sort the people who applied to them on purpose from the people who applied everywhere. A specific, researched answer signals genuine interest, lower flight risk, and someone who'll still be motivated once the novelty wears off. They're also listening for fit: whether what excites you about the role lines up with what the job actually is. So the answer is less about praising them and more about showing the overlap between what they need and what you're looking for.
- Alarm · generic flatteryGreat company, great culture. It could apply to any employer, so it proves nothing at all.
- Alarm · all about youThe salary, the brand on your CV, the location. It tells them what you get and nothing about what you'd bring.
- Alarm · the About pageReciting their own copy back to them shows you read the website but didn't think about where you fit.
- Alarm · no role specificsPraise for the company with nothing about the actual job. It reads as wanting in, rather than wanting this.
The shape of a strong answer
Two specifics, one bridgeName two concrete things and connect each to your own trajectory. Something specific about the role: the problem you'd own, the scope, the team, tied to what you want to do next. Something specific about the company: a product, a value, a direction you've actually looked into, tied to why it fits you. Then one line that connects the two to where you're trying to go, so it lands as fit rather than flattery.
Fill this in
“Two things. You're [the specific thing the role owns], and [the matching thing you've been doing], so I'd be useful early. And [the specific thing about the company you actually looked into], which is [why it matters to you].”
Worked through: “Two things. You're rebuilding the checkout flow to cut drop-off, and reducing friction in payments is exactly the problem I've spent the last two years on, so I'd be useful on day one. And I've followed how openly your team writes about its incidents. That blameless culture is how I want to work, and it's rarer than it should be.” Specific, researched, and clearly about fit.
The hard cases, answered honestly
Where it gets stressfulSpecific is easy when you've wanted to work somewhere for years. Here's how to get there when you haven't.
You barely know the company
Move · twenty minutes, two factsYou don't need to admire them, you need two things you actually looked at. The product, a recent launch, how their engineers write publicly. Two is enough for a credible answer.
How to research a company before an interview →A recruiter approached you
Move · be straight about itSay so, then say what made you take the call. Pretending you'd been watching them for years is the version that unravels under one follow-up question.
The product is genuinely unglamorous
Move · find the hard problemBoring domains have excellent engineering problems, and saying so is more credible than manufactured excitement about the sector. Scale, correctness, regulation, latency: pick the real one.
You're mostly in it for the money
Move · lead with something elseComp can be part of it and shouldn't be the headline; it's trivially outbid and says nothing about whether you'd stay. Find the true second reason and lead with that.
What are your salary expectations? →You're applying broadly
Move · answer per companyOne reusable answer is exactly what this question is designed to catch. Write the two specifics per application. It's twenty minutes, and it's the difference between a credible answer and an interchangeable one.
They ask "why this role" instead
Move · same shape, role firstSame structure, weighted to the job: the problem you'd own and why it's the natural next step from what you do now. The company half becomes the supporting note.
The generic version is obvious the moment it's said out loud. Yours should name things nobody could have said about a different employer.
Score my answer →What not to say
The short blacklist- Don't praise the culture in the abstract. Every company says it has a good one, so it carries no information.
- Don't lead with what you get. Salary, brand and location answer a question they didn't ask.
- Don't quote their website. They wrote it. Reading it back proves nothing beyond having found the page.
- Don't invent enthusiasm. Manufactured passion collapses under a single follow-up about specifics.
- Don't reuse one answer across applications. It's the exact thing the question exists to detect.
Rehearse it out loud before it's live
Saying it is the testSpecific and generic sound completely different out loud, and the gap is wider than it looks on paper. Say your two things below and Calibrd will score them on specificity, connection and research: whether they could have been said about any other employer, and whether you tied them to yourself. The same homework powers your questions for them at the end, so it pays off twice, and the method is in how to research a company before an interview.
Answer out loud · free · nothing to sign up for
“Why do you want to work here?”
Specific, before you're in the room
Answer with things nobody could say about a different company.
Paste any real job and Calibrd builds a company snapshot — what they do, how they work, recent signals — so you have concrete things to anchor on, then lets you rehearse the motivation question out loud until it sounds specific rather than generic. Free to start.
Free to start · No credit card · Your CV stays on your device