YC interview questions cluster into a handful of predictable categories: traction, product, market, competition, business model, team, why-now, and vision. The interview is 10 minutes over Zoom, so the winning move isn't memorizing answers. It's having a two-sentence framework ready for each category that you can fill in with your specifics on the spot.
Most articles hand you a list of forty questions and wish you luck. That is close to useless, because in a fast-moving interview you will never predict the exact wording, and you don't have time to recall a scripted answer anyway. What works is a framework per category: a fixed shape you drop your real numbers and insight into, so any phrasing of the question hits the same well-prepared muscle.
The categories YC interviews reliably probe
YC publishes the format (10 minutes, over Zoom, 2–3 partners)ycombinator.com/interviews but not a question script. YC partners have said the questions concentrate on team, market, and traction; the course's interview lesson breaks that into six preparation buckets (solution, customer, market, defensibility, timeline, and the YC program itself) and lists the exact questions the instructors were asked in their own interview. The categories below give you what each one is really testing and a framework you can fill in tonight.
| Question | What it tests | A framework you can fill in |
|---|---|---|
| Traction | Is anything actually happening yet? | Lead with your single sharpest number, then its growth rate, then the time window: “X today, up from Y a month ago.” One real metric beats five vague ones.Common miss: Listing every metric you have instead of the one that matters. |
| Product | Do you deeply understand what you built and why? | One sentence on what it does, one on the hardest thing you solved, one on what users do the moment they get it.Common miss: Describing features instead of the user’s changed behavior. |
| Market | Can this get big, and why now? | Name the specific wedge you start with, then the adjacent expansion, then the shift that makes today the right time.Common miss: “It’s a $50B market” with no path from your wedge to it. |
| Competition | Do you see the landscape clearly? | Name the real alternative (often a spreadsheet or the status quo), then your unique insight: the thing you believe that they don’t.Common miss: Claiming you have no competitors, which reads as naïveté. |
| Business model | Do you know how this makes money? | State who pays, how much, how often, and why that number is defensible. Rough and honest beats precise and invented.Common miss: A pricing page you’ve never tested on a real buyer. |
| Team / founder-fit | Why you, specifically? | Tie your background to this problem: the unfair advantage, the years of context, or the personal stake that makes you the right team.Common miss: Generic “we’re hard-working” with no link to the problem. |
| Why now | What changed that makes this possible today? | Point to one concrete shift (a new technology, regulation, cost curve, or behavior) that opened a window that was closed two years ago.Common miss: No answer, implying the idea could have been built anytime. |
| Vision | Where does this go if it works? | Describe the world after you win in one vivid sentence, then the very next concrete step you’ll take toward it on Monday.Common miss: Grandiosity with no believable next move. |
Rehearse against a fresh eye first.
Read your written answers for specificity and clarity before you say them out loud.
How to actually rehearse
Preparation for this interview is a physical skill, not a reading exercise. Three habits separate founders who freeze from founders who flow:
- Answer in two to three sentences, out loud, on a timer. If you can't make the point in fifteen seconds, you don't have the point yet.
- Lead with the specific, then explain. "We're at $4k MRR, up from $900 last month" earns the follow-up question. "We have some early traction" ends the thread.
- Have your single unique insight memorized cold. When partners push on competition or why-now, this is the answer that makes them lean in: the thing you believe about your market that most people don't.
Module 5 · How to Ace the YC Interview · “The Interview”
The course's interview module walks the real ten-minute rhythm: the exact questions the instructors were asked, their opening answer word for word, and a full practice question bank.
How the ten minutes actually run
The course's interview lesson reconstructs the format first-hand, and several details change how you should prepare:
- The first question is almost always a variation of "what do you do?" It is the one answer worth spending 20–30 seconds on. It should be plain enough for someone outside your industry, ideally with a concrete example. The lesson quotes the instructors' own opening answer word for word.
- You will not control the direction. It's rapid-fire; if you ramble, partners cut you off and move on. One to two sentences per answer is the working ceiling, and hitting it reliably takes timed practice.
- Know your numbers cold. Pausing to look one up reads badly and burns time you don't have. Pre-launch companies should know which metrics will matter at launch and say so.
- Don't preemptively expand. Partners have run thousands of these interviews; if they need to double-click on something, they will ask. Answer, then stop.
- Have your product running before the call. A live demo request is uncommon but real, and it comes in the second half, so don't spend ninety seconds starting a server.
- The decision comes the same day. A yes arrives as a phone call from your group partner, and YC starts immediately. A no arrives as an email with a detailed explanation, which becomes the backbone of a reapplication.
The co-founder choreography
Partners are screening the co-founder relationship as much as the company, because co-founder breakups kill more startups than competition does. Two practical rules from the lesson: take the interview from the same room if possible (founders have flown to the same city just for the call) and divide question ownership beforehand (one founder takes business questions, the other technical), so you never talk over each other. Interrupting your own co-founder is one of the strongest negative signals you can send in ten minutes.
Two more preparation notes from the lesson. First, on weaknesses, it quotes Paul Graham: concealing flaws can backfire, because a reviewer who spots an issue you haven't acknowledged assumes you overlooked it. Naming your weak point with a hypothesis for handling it reads as self-awareness. Second, the window between applying and interviewing is itself a test: showing growth, new customer conversations, or even an honest "our research killed the original idea" in that window signals the pace partners fund. The lesson includes the story of a founder who tried to cancel his interview after concluding his idea wouldn't work. YC insisted, accepted him with no idea at all, and he closed one of the strongest Demo Day rounds in the instructors' batch.
What partners push on, and how to hold up
The pushback is the interview. Partners are not trying to be hostile; they are stress-testing whether you know your company at the level a founder should. Three kinds of pressure come up in nearly every account of the room:
- The number behind the number. You say users are growing; the follow-up is how many, from what, over what period, and how you count them. If a metric is in your application, know its denominator, its window, and its weakest interpretation.
- The uncomfortable comparison. "Why won't [the obvious big company] just do this?" is not an attack, it's an invitation to state your unique insight. The bad answer is that they're slow. The good answer names the structural reason this opportunity looks unattractive or invisible to them, and why it doesn't to you.
- The premise challenge. Sometimes a partner disagrees with your framing outright. Defending a position with evidence is strong. Instantly folding is weak, and so is refusing to engage. The move is to hold your view while showing you understand theirs.
A useful drill: list the three weakest points in your own application, because those are the likeliest targets. Prepare the honest answer for each, not the deflection. Partners have read your application; they know where the soft spots are, and naming them plainly before being cornered reads as self-awareness, which is exactly the trait the pressure is probing for.
The format, from YC directly
YC publishes the interview format: a 10-minute conversation over Zoom, with 2–3 YC partners on the call, and all founders present.ycombinator.com/interviews Ten minutes is less time than it sounds. With introductions and partner follow-ups, most answers get 15–30 seconds. That is why every drill above optimizes for compression: fast, specific, honest answers from founders who know their company cold. The instructors sat this interview as W23 founders, and the course's interview module reconstructs the room first-hand: how it opens, how partners trade off questions, and what the ten minutes feel like from the founder's chair.
A last-week checklist
In the final days before your slot: write your one-liner and your single best number on an index card; do five timed mock interviews with a co-founder or a friend playing a skeptical partner; pre-decide your answer to "why now" and "who's your competition"; and re-read your submitted application so your interview never contradicts it. Then stop optimizing and get some sleep, because a tired founder gives slow answers.
When you're ready to zoom back out, the full path to getting in ties the interview back to the written application, and the application guide shows how a strong written answer sets up an easy interview answer. And remember the base-rate encouragement hiding in YC's own numbers: about half of every batch applied more than once, so an interview that ends in a "no" is a draft, not a verdict.