You are interviewing at other companies too. Why would you choose us?
answer
- acknowledge the comparison plainly
- name your two or three criteria
- place them against each criterion
- say the tradeoff out loud
- end with what you still need to learn
basics
~20 sProbes whether your interest survives comparison. Name the two or three criteria you are actually deciding on, place this employer against them with evidence from the process, admit one honest tradeoff, and never disparage the alternatives.
how to answer
5 beats- acknowledge the comparison plainlyConfirm you are looking at other options, in one unbothered sentence. Denying it costs you credibility for everything that follows, and the interviewer already assumes it is true.
- state the two or three criteria you are deciding onGive your actual decision criteria, ranked, in the order you weigh them. Two or three is the right number; five reads as a checklist and one reads as thin.
- place this employer against each criterion, with evidenceFor each criterion, cite something specific you observed in this process or in their public work. Evidence from your own conversations is the strongest material you have here.
- name the tradeoff you would be acceptingSay out loud what you would be giving up by choosing them. Delivered calmly, this is the beat that makes the rest believable, and it invites them to address the gap rather than guess at it.
- close with what you still need to learnEnd on the open question and ask for the thing that would resolve it. This keeps the answer honest and turns a closing question into a two-way conversation.
your answer
4 story prompts- List the two or three criteria you are genuinely deciding on, ranked, before you draft anything.
- For each criterion, note the specific evidence this process has already given you.
- Name the tradeoff you would be accepting and check you can say it calmly.
- Reuse your why-us hook here, but lead with criteria rather than admiration.
draft and rehearse your own answer in a learn session
go deeper
This probes motivation under comparison, and self-knowledge. It is asked late in a loop to see whether your interest is specific enough to survive alternatives, and to hear which criteria you actually decide on rather than which ones sound good. A strong answer names those criteria, places this employer against them using evidence gathered during the process, and admits a real tradeoff without disparaging anyone.
I do have two other processes running, and I would rather be straight about how I am choosing. Three criteria, in order: what the real constraint of the work is, how decisions get made and unmade, and who I would be learning from. On the first, this is the only option in front of me where build infrastructure is the thing being built rather than the tax on building it. I ran an internal cache service for our delivery teams for six months and pulled the worst offender from 27 minutes to 6 minutes 40, and I spent the entire time defending the work against billable hours. I do not want to keep making that case. On the second, I asked in both of my earlier conversations here about a decision this team later reversed, and I got a specific one with a real reason attached, not a rehearsed story. That tells me more than anything I could read. The third is genuinely still open. I have met two engineers here and I liked how they argued with each other, but I have not seen how work gets reassigned when priorities collide, and that is exactly what made my last engagement rough. The tradeoff I would be accepting is a slightly lower number at the same level than one of the other options. I would take that to work on the problem I think about anyway, but I would rather say it than pretend the gap is not there.
The criteria are technical and ranked, and each is backed by something observed during the process rather than published by the company. Naming the open criterion and the tradeoff without drama is what makes it credible. The compensation reference is deliberately structural, with no figure attached; keep yours that way, since a number here reframes a fit question as a negotiation.
I am, and I think you would be suspicious if I were not. I am deciding on three things in this order: where the hard problem sits, what mandate the role carries, and whether I believe the people. On the problem, I have run the infrastructure practice at a consultancy for four years. The last program was five squads sharing one delivery pipeline, where I took p95 image build from 18 minutes 40 to 5 minutes 30 and, more usefully, the release train stopped slipping. All of that work ended when the engagement ended. What draws me here is that the same problem is permanent and compounding rather than rented. On mandate, I asked your director what a new lead here changed without asking permission, and the answer was concrete and slightly uncomfortable, which is the good version. In my other process I have asked that twice and been given a slogan. That is most of my decision. On people, I am at roughly eighty percent. Four conversations here, one of them genuinely hard in a useful way, where someone pushed back on my read of a caching tradeoff and turned out to be right. The tradeoff is scope. The other option is a broader remit over a weaker system, and I would rather have a narrower remit over something already good that needs to get faster. If the mandate is what I have been told it is, this is where I want to be.
Ownership shows in the criteria themselves: mandate and constraint rather than learning and environment, with evidence drawn from questions the speaker put to leadership. The scope tradeoff is stated as a decision, not a worry. Softening the mandate criterion into general enthusiasm, or omitting what is being given up, would drop this a level.
You are allowed to say your criteria are still forming, as long as you name the two you have: what you would learn and who you would learn it from. Honest uncertainty lands far better than a confident-sounding ranking you cannot defend.
Your criteria should be technical and specific to the problem you want to spend your days on, and each one should be backed by something you observed in this process rather than something from a careers page. Naming a tradeoff you would accept is what separates this from flattery.
Speak about mandate and constraint: what you would be trusted to change, what the hard problem is, whether the environment lets it be solved. Interviewers at this level expect you to say what you are giving up by choosing them, and to sound calm saying it.
Frame the choice as a bet on where your leverage is largest, and be explicit about the conditions under which you would be wrong. At this level the answer also signals how you make consequential decisions generally, so the reasoning matters more than the conclusion.
saying these in an interview costs you the question
- Pretending this is your only process when it obviously is not
- Listing other employers by name to manufacture urgency
- Criteria so generic that they would select any company hiring
- Ranking the alternatives as worse rather than different
- Claiming total certainty this early, which reads as flattery
- Turning a fit question into an early negotiation about numbers
- What is the strongest case for one of your other options?Answer it fairly. Give one real advantage the alternative has, without naming the employer, then say why your criteria still point here. Refusing to concede anything makes the whole answer sound rehearsed, and a fair concession is the cheapest credibility you can buy.
- What would you need to see from us to be sure?Convert your open criterion into a concrete request: a conversation with someone doing the work, clarity on scope, a look at how priorities get resolved. Ask for something they can actually give, and be ready to say what you would conclude from it either way.
- Where are you in your other processes?Give the timeline in broad terms without naming employers or turning it into pressure. Say when you expect to be deciding and what you need from them by then. Accuracy matters here; an invented deadline usually surfaces later and costs you trust.