How to Handle YC Interview Questions You Don't Know the Answer to

When a partner asks a question you do not have a complete answer to, they are watching for one of four responses:

Response 1 — Honest acknowledgment + pivot to what you do know (correct) "I don't have that number — we haven't measured Day-30 retention yet because our oldest cohort is 5 weeks old. What I can tell you is Day-7 is 61% organically. We'll have Day-30 data in 3 weeks."

Response 2 — Fabricated or inflated answer (fatal) Giving a confident answer to a question you are not certain about. Partners probe specifics. If the number you invented does not hold up to a follow-up question, the credibility damage extends to every other answer in the interview.

Response 3 — Deflection or topic change (bad) "That's a great question — let me tell you about our growth trajectory instead." Partners recognize deflection instantly. It signals that you know you do not have a good answer and are trying to avoid it. They will ask the question again.

Response 4 — Excessive apology and shutdown (bad) "I'm so sorry, I should know this — I can't believe I don't have that number." Over-apologizing signals low confidence and poor self-management. Partners want composure, not self-criticism.

Response 1 is the only one that works. The others — fabrication, deflection, and over-apology — each create problems larger than the original gap in knowledge.

Every answer to a question you cannot fully answer should follow this structure:

[Acknowledge the gap honestly] + [Give the closest thing you do have] + [Name when or how you will close the gap]

This structure works for every category of unknown:

Missing metric: "I don't have our CAC calculated yet — we've been doing all acquisition manually and haven't systematized the cost tracking. What I can tell you is our last 10 customers all came from the same WhatsApp group and we spent 4 hours total on outreach to get them. We'll have a formal CAC calculation by the time the batch starts."

Unknown competitor: "I'm not familiar with [competitor name] — can you tell me more about what they do? I want to make sure I understand who you're comparing us to." Asking for clarification when you genuinely need it is not weakness — it is intellectual honesty. Do not pretend to know a company you have never heard of.

Scenario you haven't thought through: "I haven't specifically worked through that scenario. Thinking through it now — if [X] happened, we would probably [Y] because [one-sentence reasoning]. But that's real-time thinking, not something I've stress-tested."

Data you haven't measured: "We haven't measured that yet. Here's why we prioritized [other metric] instead, and here's when we plan to start measuring [the gap metric]."

Based on patterns across rejected founder interview accounts, these are the questions most likely to produce unknown answers — and what to have ready:

Gross margin: Many founders know revenue and burn but have not calculated gross margin explicitly. Calculate it before your interview: (Revenue - Direct COGS) / Revenue. Know the number and know what is in your COGS.

CAC by channel: Many founders know total customer count but not cost per acquisition by channel. Before your interview, estimate CAC for your primary channel even roughly: hours spent × founder hourly rate estimate + any direct spend.

Day-30 retention: If your oldest customers are less than 30 days old, you genuinely cannot have this number. Acknowledge that clearly and give Day-7 instead.

Specific competitor capabilities: Partners sometimes name competitors you have not researched. Do not fabricate. Ask for context or acknowledge you are not familiar with them and explain why you have focused your competitive research where you have.

"What would you do if [large company] entered your market?" If you have not thought through this, say so and think through it in real time. "I haven't specifically worked through that scenario. My first thought is [reasoning]." Real-time honest thinking is more credible than a polished answer to a scenario you clearly have not considered.

Market size calculation methodology: Partners sometimes ask how you arrived at your TAM. If you cited a report without doing the bottom-up calculation, acknowledge that and walk through a bottom-up estimate in real time.

The instinct to cover a knowledge gap — to answer confidently when you are not certain — comes from a reasonable assumption: that appearing knowledgeable is better than appearing ignorant. In most contexts, that assumption holds. In a YC interview, it does not.

Partners are not evaluating whether you know every answer. They are evaluating whether you are the kind of founder who engages honestly with uncertainty — because that is exactly what building a startup requires. Every week of building involves decisions made with incomplete information. The founders who thrive are the ones who know what they know, know what they do not know, and move forward clearly in both cases.

A founder who says "I don't have that number yet — here's why and here's what I do have" is demonstrating exactly the cognitive style that building a company requires. A founder who fabricates a confident answer is demonstrating the opposite — and when the fabricated answer breaks down under follow-up, it damages the credibility of everything else they have said.

The founding team that is honest about uncertainty is more trustworthy, not less. Partners invest in trustworthy founders.

"What is your gross margin?" If you know it: State it. If you haven't calculated it: "I haven't calculated it formally yet. Our revenue is ₹64,400/month. Our direct costs are hosting at ₹3,000 and one part-time support person at ₹15,000. So rough gross margin is around 72%. I should have this calculated properly — I'll have it clean before the batch starts."

"Tell me about [competitor you've never heard of]" "I'm not familiar with them — what do they do? I want to make sure I'm not conflating them with someone else." Then after the partner explains: "That sounds similar to [known competitor] in terms of [feature]. Our differentiation from that approach would be [specific reason]."

"What would your Month-6 retention look like?" If you only have Month-2 data: "We don't have Month-6 data yet — our oldest customers are 4 months in. What I can tell you is Month-2 retention is 89% and we haven't seen significant dropoff through Month-4 in our current cohort. We'll have Month-6 in 8 weeks."

"Why haven't you raised outside capital before this?" If the honest answer is that investors passed: "We've had conversations with 4 angels and one pre-seed fund. None of them converted — the primary feedback was that we needed more traction. Since those conversations we've grown from 3 to 23 customers and from 0 to ₹64K MRR. We'd like to have that conversation again."