The customer asks you to build something you are fairly sure will not solve their real problem. Do you build it anyway?
Answer
Short answer
Separate a disagreement about the mechanism from a disagreement about the goal, then test your objection cheaply rather than argue it: a week spent proving the request will not move the number is usually worth more than either refusing or complying in silence.
Keep forward deployed explicit in the answer because that is the concept the interviewer is actually trying to test. A good forward deployed explanation names the trade-off, the failure mode, and the evidence you would use before choosing. Use forward deployed once more at the decision point so the answer reads as judgement rather than a detached example.
Keep forward deployed explicit in the answer because that is the concept the interviewer is actually trying to test.
Was this answer helpful?
Likely follow-ups
- You build it, it does not work, and the customer blames the implementation. How do you handle that conversation?
- What kind of request would you refuse outright rather than build under protest?
- How do you decide whether to take your disagreement to the sponsor's manager?
- The request is politically necessary for your sponsor even though it will not help. Does that change your answer?
Related questions
- A prototype you built to prove a point is now being used as if it were production. Do you harden it or replace it?hardAlso on forward-deployed and scoping6 min
- The customer's ask is one sentence: they want to use AI on their claims data. You have six weeks. How do you get from that to something shippable?hardAlso on scoping and forward-deployed7 min
- Tell me about a decision you had to make in minutes, with information you knew was incomplete.mediumAlso on judgement6 min
- You have built something that works, and now you have to hand it to a team that did not write it and does not particularly want it. How do you run that handover?hardAlso on forward-deployed5 min