“Why do you want to work here” checks two things. Is your reason about this team? Will it still be true in a year? Most answers fail the first check. Try one test on yours. Replace the company’s name with a competitor’s. If the answer still works, it’s generic. The interviewer can’t score it. A strong answer is built from three facts. Name one specific thing about their engineering work that you looked at closely. Connect it to something you’ve already built or struggled with. Then say what you’d still have to learn there. Keep it to about a minute when spoken. Praise for the product or culture can open the answer. It can’t carry it, because every other applicant says it too. The rest of this post follows one Android engineer through that rewrite. They’re applying to a company whose app has to work without a network. Their first answer could have gone to any company.
Interviewers file this answer under motivation, so it needs evidence
At some companies, motivation is a scored area in the behavioral round. Lior Neu-ner’s guest post on interviewing.io lays out how Meta evaluates these interviews. The post has no visible date. The site also sells interview prep. The post lists motivation among eight focus areas. The question behind it is simple. What drives this candidate?
Amazon describes the same check from the recruiter’s side. In an undated About Amazon article on interview tips, Rasheeda Liberty explains what she listens for. “What I really want to know is why Amazon fits into your specific career path.” She adds that candidates should say what they want to learn there.
Both sources point the same way. The interviewer needs a reason they can write down and test. “I’m passionate about your mission” gives them nothing to test. A reason tied to your own work does.
The swap test catches an answer that could be about any company
Here’s the first answer from our Android engineer. Call them Sam. Sam has five years on a grocery delivery app. They’re interviewing at a company that builds an Android app for utility field technicians. The technicians log repairs in basements and rural areas, often with no signal.
I’ve always admired your products. I love how much your company cares about its users. I’m looking for a place with strong engineering culture where I can grow. Your team seems really collaborative. I think I’d fit in well.
Now swap in a bank, a game studio or a social app. Every sentence still works. Sam might be completely sincere. But the interviewer has heard those words from other candidates, so they can’t tell.
Yangshun Tay is a former Meta staff engineer. He writes about this mistake in GreatFrontEnd’s behavioral interview playbook. The playbook is part of a paid prep product. His point is that admiring the product leaves you interchangeable with every other fan. He also suggests keeping the answer within 60 to 90 seconds.
Find the one problem their team is working on right now
The fix starts before the interview. Look for evidence of what the team is actually working on. Good places are the engineering blog, conference talks, release notes and the job description itself. One well-read item is enough.
Sam finds a post on the company’s engineering blog. It describes how the team handles two technicians editing the same work order offline. Each phone syncs later. Then the edits can clash. The post explains why they moved from “last write wins” to merging changes field by field.
That post gives Sam something the swap test can’t break. No other company wrote it. It also gives the interviewer a topic to probe. A real reason should hold up to that.
Connect their problem to work you’ve already done
The second fact is your evidence. It shows the interest isn’t new. Pick one project where you met the same kind of problem, even at a smaller scale.
Sam’s delivery app had a similar issue. Drivers marked orders delivered while offline in parking garages. Support agents sometimes changed the same order from the web dashboard. When the phone came back online, one of the updates silently disappeared. Sam built a small conflict log to find out how often it happened. It was about one order in four hundred.
The one-in-four-hundred figure tells the interviewer Sam has already measured this problem. So the interest in the blog post is believable.
Say what you’d still need to learn there
The third fact answers Liberty’s question about your career path. Name the gap between what you’ve done and what this team does. That shows the interviewer what the move adds to your career.
For Sam, the gap is scale and stakes. A lost delivery update annoyed a customer. A lost repair note could mean a technician returns to an unsafe site. Sam fixed conflicts after the fact. This team designs for them from the start. That’s the thing Sam wants to learn to do.
The gap also keeps the answer honest. It admits Sam isn’t already an expert. It gives the interviewer a reason Sam would stay, because the learning takes time.
Sam’s rewritten answer to why do you want to work here, about a minute long
The main reason is your offline sync work. I read your team’s post about two technicians editing the same work order without signal. You moved from last write wins to merging field by field. I’ve hit a smaller version of that problem.
At my current job, drivers mark orders delivered in parking garages with no signal. Support sometimes edits the same order from the dashboard. When the phone reconnects, one update can quietly disappear. I added a conflict log to measure it. It was about one order in four hundred. Then I added a rule so the delivery status always wins.
That rule fit our case. But I fixed conflicts after they showed up. Your team designs for them up front. The stakes are also higher. A lost repair note matters more than a lost delivery update. That’s what I want to get good at next. The role would let me do it on an app people rely on at work.
Sam and the company are invented for this post. Build your version from a source you actually read and a project you actually shipped.
Run the swap test again. Put a bank’s name in the first sentence and the answer falls apart. It never mentions culture or passion. The sync post, the conflict log and the stated gap carry the motivation instead.
Expect a follow-up that tests whether the reason will last
A specific answer invites specific questions. The interviewer will ask them. The interview-prep site techinterview.org makes this point in a July 2026 post. It argues that interviewers want a reason that won’t vanish when a better offer arrives. It also notes that answers anchored in a real artifact hold up under probing.
For Sam, the likely follow-up is “What did you think of our approach?” Have one real opinion ready. Sam might say field-by-field merging fits work orders, because most edits touch different fields. Then Sam can ask what happens when two technicians edit the same field. That turns the answer into a technical conversation.
Another common probe is “Why not a competitor?” Answer with the gap you want to close. Leave criticism of the other company out. Sam can say they also looked at other offline-first apps. But this team writes publicly about the hard part, so Sam knows they take it seriously. Keep it to two sentences. Our post on behavioral follow-up questions covers this kind of probing in more depth.
When the honest reason is money, a layoff or remote work
Sometimes the real reason is practical. You were laid off, the pay is better or the role is remote. Don’t build the answer on that reason. Don’t pretend it doesn’t exist either. Lead with a true reason about the work. Then mention the practical one in a sentence if it’s relevant.
Sam might have been laid off two months ago. Then the answer opens with the sync post, as above. If the interviewer asks why Sam is looking now, the layoff gets one plain sentence. Our post on explaining a layoff in an interview covers how short that sentence should be.
If you can’t find a true reason about the work, that’s useful information too. Spend another hour on their engineering blog and release notes. If nothing there interests you, say what does. Sam could say, “The remote setup is a big part of it. Your async review process also looks like how I work best.” The first sentence is honest. The second still gives the interviewer something specific to ask about.