YC Interview Questions: What They Ask and How to Prepare

Most advice on YC interview questions treats the interview like a quiz you can cram for: here are the hundred questions, here are the model answers, memorize them. That's the wrong frame. If you walk in with scripted answers, the partners will find the edge of your script in about ninety seconds — because they don't ask one question, they ask the follow-up to the follow-up.

The interview isn't testing whether you have good answers. It's testing whether you know your own business well enough that you don't need them. The questions below are real and worth knowing, but learn them to find the gaps in your own understanding, not to prepare lines. Here's what gets asked, why, and how to actually be ready.

What is the YC interview, really?

The Y Combinator interview is a roughly ten-minute video call, conducted over Zoom, with a panel of two or three YC partners who have read your application and keep it open in front of them. All of your co-founders are expected to be on the call. There is no pitch, no deck, and no small talk — the partners start asking questions almost immediately and keep going until time runs out. They may ask to see the product. Decisions come fast, often the same day or soon after, and YC typically sends written feedback whether you're accepted or not.

Two facts about the format change how you should prepare. First, it's short and dense: ten minutes with three sharp people means you might field fifteen or twenty questions, so long wind-ups kill you. Second, the partners drive. You don't get to steer the conversation toward your strongest material — they go wherever your answers are weakest, because that's where the signal is. Reapplying the next batch after a rejection is common, and YC runs several batches a year, so a no is rarely the end of the road.

What questions does YC actually ask?

The exact wording varies, but the questions reliably fall into six categories. Each one is the partners probing a different thing they need to believe before they fund you. Knowing the category behind the question is more useful than memorizing the question, because it tells you what they're actually trying to learn.

1. What are you building? (clarity)

The near-universal opener is some version of "What are you working on?" or "What does your company do?" They want to hear you describe the business in one or two plain sentences, with no jargon, fast. Related questions: why you chose this idea, and what the product does today versus what you plan to build. If you can't explain what you do clearly in ten seconds, nothing else in the interview lands.

2. Who are your users? (users)

Expect questions about where your users come from, what makes someone try the product, and why a reluctant user would hold back. YC is checking whether you actually talk to your users or just imagine them. Specifics win: "we got our first forty users from three Slack communities, and the ones who stick all have this one problem" beats any abstract description of a target market.

3. What's your traction? (metrics)

Growth, usage frequency, retention, revenue, and unit economics. Partners want real numbers, said without hedging, and they may verify what you claim afterward. If you're pre-launch, they'll probe what you've actually built and shipped. Know your metrics cold — not on a slide, in your head — because fumbling your own numbers reads as either not knowing them or not being honest about them.

4. What have you learned? (insight)

Questions like "What have you learned from your users?" and "What surprised you?" This is where YC separates founders who are heads-down building and learning from founders who are theorizing. The best answers are counterintuitive things you only know because you shipped something and watched real people use it.

5. What about the market and competition? (market)

Expect "What's wrong with the existing products?", "Who are you most afraid of?", "Why isn't someone already doing this?", and "How does this become a huge company?" Vague answers sink here. It's not enough to say your product is easier to use — you have to explain exactly how, and name the real competitors specifically rather than waving them away.

6. Why this team? (team)

How the founders know each other, how long you've worked together, who does what, and why you're the right people to build this. If there's a technical co-founder, the partners want to know who writes the code. A practical one that catches international founders off guard: whether you'll reincorporate as a US company. Co-founder dynamics show here too — one person dominating while the others sit silent is a flag.

How should you prepare for the YC interview?

Preparation is real, but it's not rehearsal. You're not memorizing answers; you're closing the gaps between what you say and what you actually know. Here's the order that works:

1. Get fluent in your business, not your pitch. Go through the six categories above and, for each, ask yourself the follow-up to your own answer three times. Wherever you run out of a real answer, that's a gap to close before the interview — not a line to invent.
2. Put your key numbers on one page. Growth, retention, usage, revenue, burn, whatever you have. Glance at it; don't memorize it. The goal is to say any metric instantly and accurately, including the ones that aren't flattering.
3. Decide who answers what. Agree in advance which founder leads on users, which on metrics, which on the technical and product questions. Pick a default lead for the opener, usually the CEO, and make sure every founder has a real role on the call.
4. Have the demo ready to share. Partners may ask to see the product. Don't open with it — have it one click away for when they ask, ideally in the second half.
5. Write one honest paragraph about your biggest obstacle. The fastest way to lose a YC panel is to pretend you have no problems. Name the hardest thing about your business in a sentence or two, and what you're doing about it.
6. Ship something between applying and interviewing. Visible progress since your application is one of the strongest signals you can send. Even a small, real improvement tells the partners you execute.

What not to do in a YC interview

• Don't give a prepared speech. The partners want a conversation, not a monologue. A rehearsed pitch signals that you can't think on your feet about your own company.
• Don't bring slides or lead with a screencast. There's no deck in a YC interview. Opening with a demo before you're asked wastes your scarce minutes.
• Don't over-rehearse. Marathon mock interviews make founders robotic and defensive. A couple of run-throughs of the opener is plenty.
• Don't answer a question that wasn't asked. Partners ask tight questions on purpose. Answer the one in front of you, then stop — rambling eats the clock and signals you're dodging.
• Don't let one founder dominate. If you have co-founders, they need to speak. Silence from half the team reads as a weak partnership.
• Don't wave away the hard parts. Glib dismissal of obstacles, competitors, or risks is the single most common tell. Candor is a feature here, not a weakness.

The Fluency Test: what the interview is really measuring

Here's the frame that makes all of this click. The YC interview is a Fluency Test — a check of whether you can answer any question about your own business instantly, specifically, and honestly, without a script. Fluency is what you have when you've talked to enough users, shipped enough product, and stared at enough of your own numbers that there's no question about your company you have to stop and construct an answer for. You just know.

This is why cramming answers backfires and why fluent founders look relaxed in a famously stressful ten minutes. A fluent founder isn't retrieving a memorized line; they're describing something they live inside every day. The partners can tell the difference instantly, because a script has edges and fluency doesn't. The good news: fluency is earned by doing the work, which means the best interview prep isn't prep at all — it's building, selling, and learning in the weeks before, so that when the questions come fast, the answers are just true.

The shorter version

The YC interview is ten minutes, two or three partners, no deck, rapid questions across six areas: what you're building, your users, your traction, your insight, your market, and your team. You can't out-script it, because the partners follow up until they find what you don't know. So don't prepare answers — get fluent. Know your numbers cold, decide who covers what, keep the demo one click away, name your biggest obstacle honestly, and ship something real before you walk in. Pass the Fluency Test and the specific questions take care of themselves.

Frequently asked questions

What questions does Y Combinator ask in the interview?

YC partners ask fast, specific questions in six areas: what your company does (clarity), where your users come from and why they use it (users), your growth and retention numbers (metrics), what you've learned from users (insight), what's wrong with existing products and who you fear most (market), and how your founding team knows each other and who does what (team). Common openers include "What are you working on?" and "How does this become a huge company?" They ask follow-ups until they find the limit of what you actually know.

How long is the YC interview?

The YC interview is roughly ten minutes, conducted as a video call over Zoom with two or three partners who have already read your application. It's short and dense — you may field fifteen to twenty questions — so concise, specific answers matter far more than a polished pitch.

How do you prepare for a YC interview?

Get fluent rather than rehearsed. Work through the six question categories and find the gaps in your own understanding, put your key metrics on one page you can glance at, agree in advance which founder answers which kind of question, have the demo ready to share if asked, and be able to name your biggest obstacle honestly in one sentence. Shipping visible progress between applying and interviewing is one of the strongest signals you can send.

Do all co-founders need to attend the YC interview?

Yes. YC expects all co-founders on the interview call. The partners want to see how the team interacts, and they want each founder to answer questions in their area. One founder dominating while the others stay silent is a common red flag, so make sure every co-founder has a real speaking role.

What are the most common mistakes in a YC interview?

Giving a prepared speech instead of a conversation, leading with slides or a screencast, over-rehearsing until you sound robotic, answering questions that weren't asked, letting one founder dominate, and waving away obstacles or competitors instead of addressing them candidly. The underlying mistake is treating the interview as a performance rather than an honest, fast conversation about a business you know cold.

What happens if you fail the YC interview?

YC usually sends written feedback explaining the decision, and reapplying in a later batch is common — plenty of accepted companies got in on a second or third try. YC runs several batches a year, so a rejection is a timing signal more often than a final verdict. Use the feedback, show real progress, and apply again.

Should you demo your product in the YC interview?

Only when asked, and ideally in the second half. Don't open with a demo — it burns your scarce minutes before the partners have even understood what you do. Have it one click away so you can show it instantly if they ask, but let the conversation get there first.

The interview rewards founders who are already known quantities — people whose thinking, progress, and point of view the partners can feel before the call even starts. That's not luck; it's presence, built in public over months. Long before any ten-minute interview, investors and users form an impression of you from whatever they can find. That's what Invisible Keyboard builds for founders: a credible, consistent presence that does the introducing for you, so you walk into every room already recognized.See how Invisible Keyboard works

Related reading

More for founders in the YC orbit: What YC is accepting now · What YC startups are building in 2026 · Moving to San Francisco for YC: what to bring