Answering "Why This Company" Without Flattery
Most applicants have no particular feeling about most employers, and the letter still asks them to explain why this one. The standard resolution is to visit the About page and paraphrase it back with the word “passionate” attached.
There’s a better move available, and it isn’t a trick: write about the work instead of the organisation. It’s honest, it’s specific, and it answers the question the employer was actually asking.
What they’re really asking
“Why us” is generally not a request for admiration. It’s a proxy for two practical questions: will this person still be here in eighteen months, and do they understand what this job involves.
Enthusiasm is a weak signal for both, because enthusiasm is free and every applicant supplies it. What answers both questions is evidence that you’ve chosen a kind of work deliberately and that you know what this instance of it looks like.
So the honest answer to “why this company” is often “because of the work, and here’s what I know about your version of it.” That answer is available to everyone, requires no invention, and reads as considered rather than keen.
The flattery paragraph, and why readers discount it
Weak: I have long admired your company’s commitment to innovation and your mission to transform the logistics industry. Your values align closely with my own, and I would be thrilled to contribute to such a forward-thinking organisation.
The reader knows three things about this paragraph: it could have been written before the applicant learned anything about the company, the phrases came from the marketing site, and the same paragraph with two nouns changed went to a competitor last week.
That last suspicion is the damaging one. Manufactured admiration doesn’t merely fail to persuade — it puts a small question mark over everything else in the letter, because you’ve demonstrated a willingness to write things you don’t mean.
There’s a second cost that arrives later. If you claim to admire the mission, someone will ask about it in an interview, and you’ll be improvising about a company you’d read about for four minutes. The sentence you can’t defend is worse than the sentence you didn’t write.
Five honest answers
1. The work itself, described precisely.
I’ve spent five years on internal tooling and I’d like to keep doing exactly that. Most postings for my skills are customer-facing; yours is explicitly for the team that builds for other engineers, which is the narrower thing I want.
Preferring a type of role is a real reason and a durable one. It also answers the retention question far better than mission alignment does.
2. The problem in the posting.
The posting describes reporting spread across four spreadsheets and one person who knows how it works. I’ve been that person and I’ve also been the one who replaced them, so the situation is legible to me in a way it isn’t from a job title.
3. Genuine use of the product, described as use.
I’ve run a small team on your scheduling tool for about a year. The thing that keeps me on it is the audit log, which is unglamorous and the only reason I can answer questions about who moved a shift.
Note: this is available only if it’s true. Claiming familiarity with a product you’ve never opened is the fastest way to lose an interview, because users have specific opinions and non-users have adjectives.
4. The stage or shape of the organisation.
I’ve worked at two companies that went from thirty people to two hundred, and I’d rather do the next one at the start than arrive after the processes have set. Your posting reads like the start.
5. The constraint you want.
I’m looking for a role where the reporting is regulated, because I’ve found the work more interesting when there’s an actual definition of correct. That’s why a compliance-facing analytics role rather than a growth one.
When you genuinely have no reason beyond needing a job
This happens constantly and the letter does not have to pretend otherwise.
You are not required to explain why you chose them. You’re required to make a case that you can do the job. A letter that spends its whole length on one specific, well-evidenced match and never addresses “why us” is a perfectly good letter — the requirement to answer that question is mostly imagined, and it’s imagined because interviews ask it and people assume the letter must too.
If the form has a literal box asking why you want to work there, answer it about the work, in two sentences, without adjectives. The role is the narrow version of what I do — internal tooling rather than customer-facing — and the posting’s second bullet is the project I spent last year on. That’s a complete answer. It just isn’t a flattering one.
The specific-but-not-fawning line
There’s a version of company-specific detail that works: an observation, offered neutrally, that shows you looked.
Your docs put the API rate limits on the first page rather than in an appendix, which I noticed because I’ve spent a lot of time hunting for other people’s.
That sentence is a compliment, technically, but it’s load-bearing: it’s specific, it’s checkable, and it tells the reader something about what the writer pays attention to. Compare your documentation is best-in-class — same sentiment, no information.
The rule: name the thing, not your feeling about the thing. If you can delete the evaluative word and the sentence still carries information, it’s the good kind.
What not to do with public information
Two cautions.
Don’t perform surveillance. Referencing a funding round, a departure, a reorganisation, or someone’s recent job change can read as diligence or as a bit unsettling, depending entirely on phrasing and relevance. If it doesn’t connect to the work you’d be doing, leave it out.
Don’t diagnose from outside. I noticed your onboarding flow has significant friction and I could fix it is a risky sentence even when correct, because you don’t know what constraint produced it. The safe form is a question in the closing paragraph rather than a verdict in the middle — see the closing paragraph.
The underlying principle
Specificity beats enthusiasm, and specificity has to be true or it doesn’t survive contact with a conversation.
Everything a flattery paragraph is trying to do — signal that you’ll stay, that you care, that you’re not sending this to forty employers — is done better by one accurate sentence about the work. That’s the whole argument of what a cover letter is actually for, applied to the one question people most often answer dishonestly.