TechCrunch wants founders to arrive with "a decision you're working through". The question that asks who the decision was for.
On October 15, 2026, TechCrunch published a reminder that early pricing for its own Founder Summit ends the following day. "Savings of up to $200 end October 16 for TechCrunch Founder Summit," the post said, inviting readers to "Join 1,000 founders and investors on November 4 at Boston's SoWa Power Station." Founder Passes are listed at $199 and Investor Passes at $399. It is promotion for a TechCrunch event and reads like one, but the pitch itself rewards a second look. It asks attendees to show up with a problem rather than a notebook: "Come with a decision you're working through. Consider which assumptions you need to test, where your plans need strengthening, and what you want to do differently when you return to work." The decisions it names are the ones founders actually lose sleep over: "Where should you focus before raising capital? How do you know you're ready to scale? Which hire would make the biggest difference?"
Read that list for who is in it. Investors, hires, the founder's own plans. The agenda, according to TechCrunch, covers "fundraising, hiring, product-market fit, and building an AI native company," and the day is built around comparing notes with other founders and investors. The customer shows up in that agenda as half of a phrase. That is not a criticism of the event. It is an accurate description of how decisions get made inside a growing company: in rooms full of people who are not the customer, by people with good reasons to think about capital, headcount, and the roadmap first. Prioritizing the customer is not a value a team holds. It is a choice someone makes, in one of those rooms, against the pull of everyone else at the table. That is why a conference pitch about testing your assumptions is also, exactly, an interview question.
Why they ask it
The question is "Tell me about a project where you prioritized the customer." Interviewers ask it because some version of customer obsession sits on every careers page and almost nobody can prove it with a specific memory. What they are listening for is whether the candidate has ever paid a real internal cost to do what the customer needed, and whether they can tell when that cost was worth paying. A manager who has never had to choose between the customer and something else the company wanted has not been tested yet. A manager who always chooses the customer, regardless of cost, is a different kind of risk. The question is looking for judgment, not loyalty.
The trap
The weak answer is a story in which prioritizing the customer cost nothing. The team built what customers asked for, customers were pleased, the metric went up. It is pleasant and proves nothing, because there was no competing priority in the story, and so there was no prioritization. The second version of the trap is the proxy: the candidate talks about listening to feedback or running a survey and describes the research in detail, never the decision. The interviewer hears about a process and learns nothing about what the candidate gave up. The third failure is the martyr story, where the candidate overrode the roadmap, the sales team, and their own manager on the customer's behalf and presents it as unambiguous virtue. Experienced interviewers hear that and wonder what else gets overridden.
Applying STAR-T
Situation. Name the competing pressure first, because it is the whole point. "We were two months from a funding round, and leadership wanted a new analytics dashboard shipped in time for the investor demo. At the same time, our support queue showed that the export feature our largest accounts depended on was failing silently about once a week."
Task. State what you owned and what was in tension. "I owned the quarter's roadmap for the platform team. I had capacity for one of the two, and the dashboard was the thing the company was asking me for."
Action. This is where the interviewer learns whether you prioritized the customer or merely preferred them. Describe how you established the customer's real stake, with evidence rather than sentiment. "I pulled the affected accounts and found that three of our top ten customers had opened tickets about the export in the past month, and one had raised it on a renewal call." Then describe the decision and how you made it survivable for the people whose priority you displaced. "I took it to the CEO with the renewal exposure quantified, and offered a scoped-down dashboard running on static data for the demo. We fixed the export first." Name who you had to persuade and what you traded away to get there.
Result. Give the customer outcome and the internal outcome, honestly. "The export failures stopped, the renewal closed, and the demo ran on the mocked dashboard. The real dashboard shipped six weeks later than the original plan." A result that includes the delay is more credible than one that pretends the trade-off evaporated.
Trade-off. Say what it cost and whether you would do it again. "The founders were frustrated with me for a few weeks, and I would make the same call. What I would change is raising the export problem a month earlier, before it became a choice between the customer and the round."
The follow-up that breaks weak answers
"How did you know the customer was right?" Candidates who told a story about listening to feedback have nowhere to go, because they never checked. Strong candidates have an answer about evidence: which customers, how many, what the problem was costing them, and what they would have done if the data had pointed the other way. The second version is "What did the people you overruled think afterward?" That one separates the manager who prioritized the customer from the one who simply won an argument. Be ready to say who disagreed, what they were right about, and how the working relationship held up once the decision was made.
Score your answer against the director’s bar
Q: Tell me about a project where you prioritized the customer.
Pick one project where the customer won against something internal, and rehearse the cost out loud until it sounds like a decision rather than a defense. Try it free →