Interviews · 12 min read

What YC Partners Think About During Interviews — Insider View

Short answer

The YC interview is 10 minutes. Partners are not running through a checklist. They are forming a single, continuous impression across every answer, every hesitation, every moment of honesty or deflection. Understanding what is happening in a partner's mind during those 10 minutes — what they are weighing, what specific signals they are collecting, what moments shift their assessment — gives founders a fundamentally different preparation target than memorising question-answer pairs.

The Partner's Core Question

This page draws on publicly available partner accounts, YC essays, and patterns reported across thousands of founder interviews to give founders the clearest available picture of what partners are actually evaluating.

Partners are not asking "is this a good company?" They are asking one question across 10 minutes:

"Would I bet on these founders to figure this out?"

Not: will this specific product succeed? Not: is this the right market? Not: do I understand this technology? All of those things can change. What partners are evaluating is whether these specific people, with what they currently know, have the intellectual honesty, execution speed, and founder-problem fit to keep solving the right problems until they find something that works.

Every sub-question in the interview is a probe of that central question.

The Answer Layer: What Partners Are Weighing in Each Section of the Interview

First 60 Seconds — "Can These Founders Think Clearly?"

The first question is almost always a simple version of "what do you build?" Partners are not listening for a good answer. They are listening for clarity. Can this founder take a complex thing and state it simply? Do they lead with the thing that matters most? Do they stop when they have answered the question?

What shifts assessment positively in the first 60 seconds:

One sentence that is specific, not generic
No jargon that requires domain knowledge to decode
An immediate stop after the answer — no filling the silence

What shifts assessment negatively:

A three-minute pitch to a one-sentence question
An answer that is technically accurate but requires the listener to work to understand the product
Opening with the market size rather than the product

Minutes 1-5 — "Is the Evidence Real?"

This is the core of what partners are evaluating. Every question about customers, revenue, retention, and growth is a probe of a single thing: are these numbers real, and does this founder genuinely understand what is driving them?

The internal question partners are asking: "If I called one of their customers right now, would that customer describe the product the way this founder described it?"

What partners are looking for:

Numbers that match the application exactly or are explained if they have changed
A founder who can go from the metric to the mechanism: "our retention is 62% because users who complete the inventory setup in session 1 have 3x the retention of users who don't"
Evidence the founder has talked to churned users and knows specifically why they left

What partners notice but rarely say aloud:

When a founder rounds numbers, they note it. "Around 20" when the application said 23 raises a flag.
When one cofounder states a different number from the other, they note it and will probe.
When a founder's eyes move before answering a metric question — searching memory rather than knowing — they note it.

Minutes 5-7 — "Does This Founder See Something Real?"

The insight and competition questions are probing whether the founder has a genuine non-obvious understanding of their market or whether their insight is something anyone could derive from reading an industry report.

What partners are weighing here:

Is the insight specific enough to have only come from direct experience?
Can the founder describe what competitors do well without becoming defensive?
Does the insight connect directly to a specific product decision — proving it is embedded, not just claimed?

The internal thought when insight is genuine: "I wouldn't have known that. Only someone who has been inside this industry or done this level of user research would know that."

The internal thought when insight is thin: "That's basically saying the incumbents are slow. Every startup says that. That's not an insight, that's a complaint."

Minutes 7-9 — "Would I Want to Work With These People?"

Team and strategy questions are partly informational but largely relational. Partners are working with 100-200 companies per batch. They are evaluating whether these specific founders are people whose judgment they trust, whose self-awareness they respect, and with whom they want to have a close working relationship for the next several years.

What signals trust in this section:

A founder who acknowledges what their cofounder does better than them specifically
A founder who names their biggest risk without hedging
A founder who has a clear, honest answer to "what have you gotten most wrong so far"

What signals distrust:

Excessive positivity about everything — a founder who has no weaknesses, no uncertainties, no risks is not being honest
A cofounder who has nothing to add — it raises whether they are actually contributing
A "why YC" answer that is generic — it signals the founder has not thought carefully about what they actually want from the relationship

Minute 9-10 — "What Is the One Thing Most Likely to Be Wrong?"

The final hard question is deliberate. Partners want to see how a founder responds to discomfort. Can they engage honestly with the worst-case scenario for their company? Do they become defensive? Do they answer too quickly with a polished response that was clearly prepared?

What a strong final answer looks like: Specific, honest, immediate. Not the smallest possible risk reframed as a strength. The actual risk that keeps you up at night, stated clearly, followed by what you are doing about it.

What a weak final answer looks like: "Our biggest risk is competition, but we have a strong team." That is not an answer. It is deflection with positive framing.

The Data Layer: Specific Signals Partners Weight Heavily

Based on partner accounts, essays, and patterns across thousands of reported interviews, these are the signals that most consistently shift partner assessment:

High-weight positive signals:

Knowing a specific metric (not rounded) without hesitation
Naming a mistake they made and what they specifically changed
Naming a churned customer and exactly why they left
Describing a cofounder's strength with a specific observable example
Having a non-obvious insight that is traceable to a specific experience or data point

High-weight negative signals:

Numbers that change between the application and the interview without explanation
One cofounder being silent for more than 3-4 minutes
Inability to name what a competitor does well
"We don't really have competition" — partners have never found this to be true
A long answer to a simple factual question — signals narrative management rather than genuine mastery

Signals that are neutral but founders think are positive:

Impressive academic credentials (partners are interested in what you have built, not where you went)
A large addressable market stated confidently (partners have heard this for every company)
A well-designed product demo (good design is table stakes; retention data matters more)
Name-dropping advisors or investors (partners weight what you have done, not who you know)

The Context Layer: The Internal Deliberation After Your Interview

Understanding what happens in the 10 minutes after your interview — when partners discuss your company — helps founders understand what is worth preparing for.

How the discussion typically goes:

One partner states their primary positive signal: "The retention numbers are exceptional — 62% Day-30 organic is the best I've seen in this category in a year."

Another partner states their primary concern: "The cofounder split felt off. The technical cofounder answered every product question. I don't have a clear picture of what the commercial cofounder actually does day to day."

The discussion resolves one of three ways: the concern is outweighed by the positive signal (fund), the positive signal does not overcome the concern (reject), or more information is needed (follow-up question or waitlist).

What this means for preparation:

Your job in the interview is to make the positive signal as strong as possible and to preemptively address the most predictable concerns before they become the primary concern in the post-interview discussion.

The most predictable concerns are always the same: weak retention, unclear cofounder roles, thin competitive insight, and a "why YC" answer that sounds like any startup's answer. Address all four proactively in the interview before partners flag them.

Keep reading

More on Interviews

Founder Stories

Long-form, sourced stories from real YC founders.

Essay

Paul Graham: Do Things That Don't Scale.

Framework

The Mom Test — talk to users without lying to yourself.

Go deeper

Want the full data behind this answer?

Our YC database tracks 5,000+ companies, every batch, with application patterns, founder backgrounds, and pivot stories — the raw material we built this answer on.

Open the database →

FAQ

Frequently asked questions

What is the single most important thing YC partners are evaluating in an interview?

Whether they would bet on these specific founders to figure out a large, hard problem. Not whether the current product is perfect, not whether the market analysis is airtight, not whether the deck is polished — whether the founders demonstrate the intellectual honesty, execution speed, and domain clarity that characterises founders who keep iterating until they find something that works. Every question in the interview is a probe of this single underlying assessment.

Do YC partners make their decision during the interview or after?

After — in a brief group discussion with the other partners who were present, held immediately after the interview block ends. Most decisions are reached within minutes of the discussion starting because the relevant information was collected during the interview itself. The discussion is synthesis, not research. For borderline cases, the discussion may take longer or prompt a follow-up question to the founders before a decision is made.

What do YC partners find most impressive in a founder interview?

Intellectual honesty paired with operational mastery. A founder who can state their retention rate to one decimal place, explain exactly what drives it, name a churned user by first name and the specific reason they left, and then describe the precise product change they made in response — that founder is demonstrating that they are close to their business, honest about its weaknesses, and actively managing them. This combination is rarer than founders expect and more impressive than any amount of market analysis or vision articulation.

What is the most common mistake founders make that costs them in the partner deliberation?

Not addressing their biggest vulnerability proactively. Partners identify the primary concern in post-interview deliberation based on what the interview raised but did not resolve. Founders who address their vulnerability head-on — "I know our month-2 retention is lower than we want, here is exactly why, here is what changed in our last cohort, and here is what we expect from the next one" — remove the concern from the deliberation table. Founders who wait for partners to raise the concern give it full weight in the post-interview discussion.

Do YC partners read the application again just before the interview?

Yes. Partners review the application in the 30-60 minutes before each interview block. This review is what generates the specific follow-up questions — the things the application raised but did not clearly answer. Understanding this is important: your application shapes your interview. A vague application produces probing questions about things that were left unclear. A specific, honest application means partners can spend interview time on forward-looking strategy rather than clarifying basic facts.

How do YC partners weigh a strong insight against weak traction?

This depends on the stage and the partner's read of the founders. For very early companies (pre-revenue, prototype stage), a genuinely compelling insight paired with a credible team can outweigh weak traction — because the insight suggests the founders understand something that will allow them to find traction quickly. For companies that have been operating for 12+ months with weak traction, a strong insight is less compelling — partners will ask why the insight hasn't translated to traction yet and whether the team can actually execute on what they claim to understand.

What does it mean when a YC partner asks a lot of follow-up questions?

It is not a reliable signal of either acceptance or rejection. Partners ask many follow-up questions when they are genuinely curious and engaged — which can mean they are excited about the company or that they have a specific concern they are trying to resolve. Partners who have already mentally rejected a company sometimes ask fewer questions because there is less they want to know. Do not attempt to read the volume or intensity of follow-up questions as a signal of the outcome.

What do YC partners think when they see both cofounders for the first time?

They are immediately assessing complementarity — do these two people seem like they are doing fundamentally different things, and do they seem like they have a real working relationship rather than a convenient one? They are also assessing engagement — does each cofounder seem equally interested in what the other is saying, or is one clearly the lead and the other clearly secondary? The strongest team first impression is two cofounders who clearly respect each other's specific contributions and who engage naturally rather than performing a rehearsed dynamic.

How do partners feel about founders who have clearly prepared very thoroughly for the interview?

Positively, if the preparation shows as deep knowledge rather than scripted answers. Thorough preparation that results in precise metrics, clear one-sentence answers, and natural handling of follow-up questions looks like mastery. Thorough preparation that results in long polished answers that cannot be interrupted, deflection of specific follow-ups back to prepared talking points, or robotic delivery looks like over-rehearsal and signals that the knowledge is shallow underneath the polish.

What is the thing YC partners most want founders to understand about what they are evaluating?

That they are evaluating the founders, not the deck. The product, the market, the insight, the competition — all of these things can change and in many cases will change after YC. What cannot change is the fundamental quality of the founders' thinking, honesty, and execution instincts. Partners have funded companies that pivoted entirely from their batch pitch to something different. They have passed on companies with impressive initial products because the founders did not demonstrate the qualities needed to navigate the hard moments that come after the batch. The founders are the investment.

How do partners decide between a "yes" and a "waitlist"?

The waitlist typically reflects genuine interest paired with one specific unresolved concern — usually a concern that could be addressed by more time or more information rather than a fundamental problem. A waitlist communication often includes a specific question: "Can you share updated retention data from your last 30 days?" or "Can you clarify the cofounder equity structure?" A yes without a specific outstanding concern. A no when the concerns outweigh the positive signals and more time or information is unlikely to change the fundamental assessment.

What do partners think when a founder says "we don't have competition"?

It is an immediate credibility concern. In over 15 years of YC interviews, partners have never encountered a company that genuinely has no competition — because competition includes the manual process, the adjacent tool, and the status quo. When a founder says "we have no competition," partners hear one of two things: either the founder has not done sufficient competitive research, or the founder defines "competition" so narrowly that they are obscuring the real competitive landscape. Neither interpretation is positive. The right answer names specific competitors, acknowledges what they do well, and explains precisely why your specific user is underserved by their approach.

← all YC Q&A

An independent resource · Not affiliated with Y Combinator · Last updated 2026-08-04