Y Combinator Interview Questions and What They Test

The YC interview is built like a pressure valve, not a conversation. Ten minutes on Zoom, 2 to 3 partners who've already read the application and keep it open on screen while they talk, rapid-fire questions, constant interruptions, no slides, no pitch, no small talk make up the whole format. No ramp-up, no rapport-building, no "tell us about yourselves."

The pace and the interruptions are the test itself. They're the test itself. A founder who can only perform well when nobody cuts them off is a founder who can't close a skeptical customer, negotiate with a sharp candidate, or survive a tough board meeting, and the interview compresses all three of those future moments into ten minutes.

What the format measures, according to YC's own published interview guide, is clarity under speed, how close a founder actually is to their users, honesty about what isn't working, and how fast the company is moving. Idea quality matters, but it's one input among four, and it's not even the one partners spend the most time probing.

Heavy rehearsal backfires before founders even walk in. Partners can tell, almost instantly, when someone is answering a question they prepared for instead of the question they were actually asked. The guide is explicit that the format is designed to need very little preparation. That's a strange thing to hear if every instinct says to over-prepare for the biggest ten minutes of a company's life, but it's the whole logic of the exercise: YC isn't buying a script, it's buying the ability to think out loud under fire.

Every question cluster that follows, product, growth, team, character, vision, funding, is a diagnostic wearing the costume of small talk. None of it is random. Once that clicks, the rest of the interview stops looking like an obstacle course and starts looking like a test with an answer key.

What "What are you working on?" measures

Almost every interview opens with some version of "What are you working on?" and, according to YC's own guide, founders fail this question constantly. That's a strange thing to fail. Every founder knows this question is coming.

Memory is not what's being tested. It's whether a founder can describe the business in plain sentences, cold, with no runway and no slides to lean on. Two or three sentences, clearly stated, then a full stop while the next question lands. That's the standard.

Most founders don't meet that bar because they've rehearsed a pitch built to run for two minutes uninterrupted, but the interview allows rapid-fire questions and frequent interruptions, with no slides, no pitch, and no small talk. So the founder either plows through the rehearsed version anyway, ignoring what was actually asked, or freezes because the script doesn't fit the moment. Both read as the same failure: an inability to listen and adjust in real time.

YC's guide puts a fine point on the bar for specificity: "It's not enough to say that you're going to make something that's more powerful, or easier to use. You should be able to explain how." Vague superiority claims don't survive contact with that standard. A founder needs to say, concretely, what the product does and what competitors get wrong, not gesture at being "better" or "faster" and hope the partners fill in the blank.

This opening question is doing double duty. It sets the tone for the follow-up that almost always comes next, "Why did you pick this idea?", which is really asking about founder-problem fit: why this person, out of everyone who could have built this, and why now. A founder who nails the opener has usually already set up the answer to that one too, because clarity about the what tends to come bundled with clarity about the why.

How product questions test whether founders treat the MVP as a beginning, not an end

Once the interview moves past "what is this," it shifts into "do you actually understand what building this requires." Narrowing is the one discipline the product questions test above all others. What's the simplest version of this idea. What gets built first. What metric moves because of it.

Take "What metric will improve with this feature?" The feature itself isn't really what that question is checking. It's checking whether the founder has a habit of connecting product decisions to measurable outcomes, rather than building on instinct and hoping it works out. A founder who can't name the metric usually hasn't thought past "this seems like a good idea."

"How long is your product development cycle?" does something similar from a different angle. It's a reality check on a founder's time estimates, because optimism that hasn't been tested against an actual shipping cycle tends to be wildly, confidently wrong. This question is how they find out which kind of founder they're talking to.

Both questions test a distinction YC cares about a lot: product development, the loop of iterating, measuring, testing, and improving, is not the same thing as shipping an MVP. The MVP is where the loop starts. Founders who treat it as the finish line, the thing they built and are now waiting to be rewarded for, tend to give static, backward-looking answers when asked what comes next.

None of this requires traction to score well. YC has said publicly that about 40% of the companies it accepts are still at the idea stage with zero revenue. What matters is clarity about what's being built and why it's built that way. A founder with no customers yet can still ace this cluster by showing they understand the loop they're about to run. A founder with impressive early numbers can still fail it by showing they've stopped thinking past the thing they already shipped.

Why growth and retention questions are scored as two separate signals

This is the busiest stretch of the interview, question-wise. Where do new users come from. What gets them to try the product. Why do the reluctant ones hold back. What does growth actually look like. How much are people using it. Do they come back. What are the unit economics. It can feel like a single long interrogation about "growth," but it's actually measuring two different things, and conflating them is where a lot of strong-sounding answers fall apart.

On the acquisition side, YC's guide is looking for one specific, repeatable channel that's demonstrably working. A founder who says "every customer comes from one specific referral loop, and here's the number that proves it repeats" is describing a mechanism.

Retention is graded on its own axis entirely, separate from how fast new users show up. The question of whether customers are one-and-done or come back can quietly wreck an otherwise impressive growth story. Strong acquisition paired with fast churn doesn't read as "good at getting users." It reads as a founder who hasn't yet figured out why people actually want the product, because if they had, more of those people would stay.

Then there's the question that functions almost like a lie detector: "What's the most surprising thing you've learned since you launched or talked to users?" There's no good way to fake an answer to this one. A founder who hasn't talked to real users recently has nothing specific to say, and partners notice the gap immediately. This is what YC's guide means by user intimacy: founders who can say exactly where their users come from, why those users stick around, and what caught them off guard are demonstrating real contact with the people they're building for.

What co-founder questions are probing beneath the surface

The team questions sound like getting-to-know-you material. How did the founders meet. How long have they known each other. Who does what. What's the equity split and why. What's the biggest disagreement they've had. None of it is small talk. It's a stress test of whether the relationship at the center of the company can survive pressure.

Co-founder chemistry gets treated as close to a precondition for funding, because a company already has enough challenges without also managing a fragile partnership between the people running it. YC's evaluation approach treats that relationship as load-bearing infrastructure.

One specific anti-signal appears often enough in interviews to be documented: a single founder doing all the talking while co-founders sit quietly in the background. That's a flag, not a stylistic quirk, and YC's preference is for every founder on the call to answer at least one question directly. Silence from a co-founder reads as either disengagement or an imbalance of power neither founder has been honest about.

Founders face the same scrutiny over how equity was split. The actual percentages matter less than whether the split was arrived at through honest, direct conversation. An unexplained split, or visible discomfort when the topic comes up, signals unresolved tension that hasn't been dealt with, just avoided.

Solo founders aren't automatically penalized. Roughly 10 to 15% of each batch is solo founders, typically accepted when that founder is technical, has already shipped product, and can show an ability to recruit. But "Have you looked for a co-founder?" still demands a real, considered answer. Waving the question off reads worse than admitting the search didn't work out.

The trait YC calls "Friendship" in its evaluation framework, drawn from Paul Graham's writing, uses the co-founder relationship as a stand-in for something bigger: intellectual honesty, the ability to disagree without it turning into contempt, and the kind of intensity that makes people want to build something difficult together. Founders who describe their partnership in glossy, press-release language, "we've never had a real disagreement," "we're perfectly aligned on everything," tend to score worse than founders who describe an actual fight they had and how they got through it. Performed harmony is less convincing than honest friction, every time.

How determination and flexibility questions reveal whether a founder is coachable under pressure

Determination questions aren't a contest for the most dramatic backstory. What YC's evaluation framework is actually listening for is texture: did this founder, faced with something going wrong, give up and regroup with a new plan, or find an actual way through the specific obstacle in front of them?

The answers that score highest are oddly specific. A name. A date. A number. A concrete outcome. Something that makes the stakes feel real instead of abstract. Founders who answer with phrases like "pushing through the uncertainty" or "staying resilient" tend to score low, because that kind of vagueness is usually a sign the experience wasn't as formative as the founder is claiming it was.

Flexibility gets asked right alongside determination for a reason: "How would you handle it if your current approach stopped working?" YC has backed some of the most dramatic pivots in startup history, and its own framework cites them directly. YouTube started as a video dating site. Slack was an internal tool built for a video game company. Instagram was built on the bones of a Foursquare clone. None of those companies would exist if their founders had treated the first version as sacred.

What scores well here is a founder who can describe specific experiments they already killed, plus the logical next direction that followed from killing them, not a declaration in the abstract that they're open to pivoting if things go sideways. The evaluation framework has a name for this: a body count of dead ideas. A founder with a body count has already proven they can let go of something that isn't working, which is a much stronger signal than a promise to do so someday.

Determination and flexibility are really testing the same underlying thing from two directions: judgment. This founder's judgment shows in whether they can tell the difference between a hard moment worth pushing through and a wrong direction worth abandoning. The accountability questions late in the interview, "Why haven't you made more progress?" or "Why haven't you grown faster?", test that exact same judgment under a different name. Founders who've internalized a habit of setting and reviewing weekly goals tend to answer without getting defensive, because they already know the answer. Founders who haven't built that habit tend to reveal it the moment the question lands.

What the "unconventional insight" question screens for that no other question does

One question does something none of the others manage: "What's unconventional but true about your market?" It's quieter than the growth or product questions, and it rewards a slower kind of thinking, but it's arguably the hardest one in the whole interview to fake.

The question separates founders who've actually reasoned from first principles from founders who've absorbed whatever the industry already believes and are repeating it back with more confidence. Most founders, under time pressure, default to the second mode, because conventional wisdom is what comes to mind fastest.

YC's evaluation framework draws a clean line here: if the answer could show up word-for-word in a mainstream industry report, it's failed the question. A good answer makes an experienced investor pause, because it sounds wrong on first hearing and only becomes defensible once the founder walks through the evidence behind it.

This is also where two earlier threads tie together. "Why did you pick this idea?" and "Why are you the right person to solve this problem?" converge right here, because founder-problem fit was never really about résumés or industry credentials. It's about whether the founder found the problem by living inside it, felt the friction personally and repeatedly, and ended up with no real choice but to go fix it.

A related question, sometimes framed as a story about bending rules to get something done, tests an adjacent muscle: the instinct to find loopholes, outmaneuver slower-moving competitors, and do things larger organizations had already declared impossible. The evaluation framework has a phrase for this quality: a piratical gleam. Combined, the unconventional-insight question and the rule-bending question are checking for the same foundation, a genuinely original view of the world, which is where any defensible competitive advantage actually starts.

What the team-scaling questions reveal about a founder's vision ceiling

Once the interview is confident the founder understands their current product and users, it pivots to a different question entirely: has this founder thought about what the company looks like after it outgrows what it is today? Who's the boss. Who's the next hire. How does the team expand to keep building product. These sound operational. They're actually about ambition.

The clearest example is the question, "What is the biggest idea you can convey on how this niche product grows into something huge?" It's the most forward-looking question in the whole interview. The answer doesn't need to be a guaranteed roadmap. It needs to be bold and still believable, a claim about what happens after the current niche gets dominated, not a hand-wave about "going global eventually."

YC's preference for at least one technical co-founder appears again in this cluster. Non-technical solo founders are accepted in very few cases, and usually only when deep domain expertise, a technical partner recruited along the way, or a no-code MVP already carrying paying users makes up the difference. The scaling questions assume someone on the team can actually keep building the product as it grows, and if that's unclear, the vision answer rings hollow no matter how big it sounds.

The "next hire" question quietly works as a separate self-awareness check. A founder who answers "we need a great engineer" is giving a generic answer that could apply to any company on earth. A founder who answers "we need someone who's scaled a marketplace through several orders of magnitude of user growth" is naming the exact ceiling the company is about to hit. That specificity is the signal. It shows the founder already knows where the current team runs out of road, which is a different and more valuable thing than simply wanting to hire more people.

How to understand what YC is testing when it asks about funding and traction

Funding questions make founders anxious in a way that's slightly out of proportion to what's actually being measured. "Have you raised funding?" isn't really a status check.

YC's standard deal runs through exactly those instruments: $500,000 total, split into $125,000 for 7% equity on a post-money SAFE, plus $375,000 on an uncapped SAFE carrying a Most Favored Nation clause, which converts at the best terms of any SAFE issued before the next priced round, or at the terms of that priced round itself if no earlier SAFE exists. A founder fumbling basic SAFE mechanics in the interview is a founder about to sign a document they don't fully understand a few weeks later.

Traction questions carry a similar undertone. Numbers get checked afterward, so the honest move is to know them cold rather than estimate under pressure and hope nobody asks twice. Credibility doesn't come from the size of the number. It's whether the founder can explain, clearly and without flinching, why progress looks the way it does right now.

That habit, tracking real numbers weekly and being able to explain them without flinching, takes time to build. Founders should build that discipline long before any interview is on the calendar. Founders who've already built that habit tend to walk into the ten minutes with nothing to rehearse, because they've been answering the hard questions, out loud, to themselves, every week already.