YC Application Tips: What the Best Founders Do Differently
Practical advice for Y Combinator applicants. What partners look for, how to nail the interview, and what sets successful founders apart. Y Combinator gets thousands of applications each cycle. Most get rejected. The ones that make it share a few patterns you can replicate. **What YC Partners Actually Read First** The application is short on purpose. Partners skim the top three fields before anything else: the problem, the solution, and the founder bios. If those don't click in under a minute, the rest doesn't matter. The problem should be specific. "Enterprises waste money on bad software" is weak. "Construction firms lose 12% of project revenue to manual change orders" is better. Partners want to see you've talked to real users and found a pain that has a cost attached. The solution matters less than the problem. YC funds teams, not features. A mediocre solution to a real problem beats a clever solution to a fake one. Founder bios get read for evidence of grit, not pedigree. A Stanford CS degree helps, but so does "built a moving company at 19, ran it for three years, sold it." They're looking for people who do things, not people who talk about doing things. **How to Write the Application** Write like you talk. If you wouldn't say it in a bar, don't write it in the application. Partners read hundreds of these in a weekend. Short sentences, concrete numbers, no fluff. For the "why now" question, give a real reason. "AI got cheaper" is not a reason. "We ran 200 customer interviews and 40% said they'd pay today" is a reason. Don't pad. If a question asks for one sentence, give one sentence. If you have nothing to add, skip it. Empty space reads as confidence. **The Interview: What They're Testing** The interview is ten minutes. Three partners, rapid-fire questions. They're not testing your pitch. They're testing how you think under pressure. Expect questions like "Why is this hard?" and "What breaks if you get 100 customers tomorrow?" They want to see you reason out loud. If you don't know, say "I don't know" and then walk through how you'd find out. Partners also test conviction. If they push back on your pricing, don't fold immediately. Defend your reasoning, then acknowledge what you'd change if evidence showed otherwise. They want founders who can hold a position without being stubborn. The worst thing you can do is recite your application. They've read it. They want new information, or at least a deeper version of what you wrote. **What Sets Successful Founders Apart** The founders who get in tend to have three things in common, but not in a neat package. First, they've done something hard before. It doesn't have to be a startup. It could be a marathon, a thesis, a side project that took two years. The point is they know what sustained effort feels like. Second, they have a specific insight about their market. Not a trend, an insight. Something they noticed because they worked in that industry or lived that problem. "I was a nurse for six years and I know exactly why shift scheduling software fails" beats "I researched the healthcare market." Third, they're honest about what they don't know. The best interviews include moments where the founder says "we haven't figured that out yet" without flinching. Partners trust that more than a polished answer that dodges the question. **A Few Practical Tips** Apply early. The batch fills up, and later applications get read faster, which means less attention per application. Don't use the optional video unless you have something real to show. A demo of a working product is good. A founder talking to camera for two minutes is not. If you get rejected, apply again next cycle. A third of the companies in any batch applied more than once. Rejection doesn't mean your idea is bad. It means the application didn't land. The process is noisy. Good teams get rejected, weak teams get in. Your job is to make the signal clear and hope the noise works in your favor.