/apply
YC Application Questions.
Every question on the YC application for 2026, what reviewers actually look for, and side-by-side good vs bad answer examples. Built from public YC partner talks, accepted application teardowns, and reverse-engineered rejection patterns.
Question 1
What is your company going to make? Please describe your product and what it does or will do.
What YC actually wants
A one-paragraph, jargon-free explanation. They read 20,000 of these. They want to understand what you do in 15 seconds.
✓ Good answer
"We make a payment API for African e-commerce. Merchants in Nigeria, Kenya, and Ghana integrate one SDK and we handle all local payment methods (M-Pesa, USSD, bank transfer, cards) plus FX, settlement, and fraud. Live with 47 merchants doing $2.1M GMV/month."
✗ Bad answer
"We're building the future of fintech for emerging markets, leveraging AI and blockchain to revolutionize cross-border payments through a vertically-integrated platform."
→ Note: Concrete > visionary. Numbers > adjectives. If you're live, lead with traction. If pre-launch, lead with what the user clicks.
Question 2
Why did you pick this idea to work on? Do you have domain expertise in this area? How do you know people need what you're making?
What YC actually wants
Personal connection to the problem + evidence that real people have it. They're sniffing for fake passion and made-up market demand.
✓ Good answer
"I worked at Stripe on the Atlas team for 3 years and saw 400+ African founders struggle to accept payments from their own customers. I personally helped them duct-tape solutions together. We talked to 60 merchants before writing a line of code; 38 said they'd pay $200/mo on day one."
✗ Bad answer
"We saw the market for African fintech is projected to be $40B by 2030 and we're passionate about emerging markets."
→ Note: Market size projections are a red flag. They want 'I lived this' or '60 customer interviews.' Quantify everything.
Question 3
What's new about what you're making? What substitutes do people resort to because it doesn't exist yet (or they don't know about it)?
What YC actually wants
Honest competitive analysis + the 'before' state of your customer's day. They want to know you've actually thought about why now and why you.
✓ Good answer
"Today merchants integrate 4–6 separate APIs (Flutterwave for cards, Paystack for Nigeria, Stripe for international, manual bank reconciliation, etc.) and write their own router. Average integration: 6 weeks. Ours: 1 day. The 'new' part is unified settlement in USD with auto-FX hedging — nobody else offers that for sub-$10M GMV merchants."
✗ Bad answer
"There are no real competitors. The space is wide open."
→ Note: Saying 'no competitors' = instant rejection. It means you haven't looked. Always name 3 competitors and explain your wedge.
Question 4
How do or will you make money? How much could you make?
What YC actually wants
A real revenue model, not a vibe. They want to see you've done the math on whether this can be a $1B+ company.
✓ Good answer
"2.9% + $0.30 per transaction, same as Stripe. Average merchant does $50k/mo GMV → $1,750/mo revenue. 10,000 merchants in Africa with $50k+ GMV = $210M ARR opportunity. Realistic 5-yr capture: $50M ARR."
✗ Bad answer
"We'll figure out monetization once we have users. The market is huge."
→ Note: Even pre-revenue, show you've thought about it. Pick a model, defend it, do the math out loud.
Question 5
If you've already started working on it, how long have you been working and how many lines of code (if applicable) have you written?
What YC actually wants
Evidence you ship. They prefer founders who built something in a weekend over founders who've been 'planning' for 6 months.
✓ Good answer
"Started 4 months ago. ~28,000 lines of TypeScript. Live product, 47 paying merchants, 99.7% uptime over the last 60 days."
✗ Bad answer
"We've been working on this for 18 months and are still in stealth, finalizing our architecture."
→ Note: Long timeline + no shipped product = death. Better to apply with 6 weeks of work and a live demo than 2 years of slides.
Question 6
Tell us something surprising or amusing that one of you has discovered.
What YC actually wants
An insight you couldn't have had without doing the work. This is where they separate real founders from theorists.
✓ Good answer
"47% of African merchants we onboarded had been manually copying payment data from screenshots their customers sent on WhatsApp. One had a full-time employee whose entire job was reconciling WhatsApp screenshots."
✗ Bad answer
"We discovered the market is bigger than we thought."
→ Note: Specific, weird, true. The more it sounds like 'you can't make this up,' the better. This question is a tell for whether you've talked to users.
FAQ
The questions founders ask about the questions
How many questions are on the YC application?
The written YC application has around 15 questions plus a 1-minute founder video. Most questions expect 2–4 sentences; the founder, product, and progress sections carry the most weight in review.
What YC application questions matter most?
The three highest-signal questions are: what you're building (clarity of the product), what you've done so far (velocity and traction), and why this team (founder-market fit). Weak answers here almost always kill an application even when the rest is polished.
How long should each YC application answer be?
Short and specific beats long and general. YC partners have said publicly they read fast — 2–4 tight sentences with concrete numbers, named users, and dates outperform paragraph-long prose every time.
Do YC partners actually read every application?
Yes. Every submitted application is read by at least two partners. That's why specificity matters — reviewers skim hundreds of forms and remember the ones with sharp, verifiable details.
Can I edit my YC application after submitting?
Yes, until the batch deadline. YC encourages founders to update their application with new traction, launches, or user numbers up until interview decisions go out — the 'updates' field is one of the most under-used levers in the process.
What's the biggest mistake in YC applications?
Vague answers. 'We're building the future of X' or 'We use AI to help Y' with no numbers, no user names, and no concrete wedge is the fastest way to a rejection. Every strong answer names something specific — a user, a metric, a date, a demo link.
Keep reading
Playbook
How to Apply to YC →
Application questions, video tips, and what partners look for.
Playbook
YC Application Examples →
Airbnb, Stripe, Reddit — real accepted YC applications, decoded.
Timeline
YC Application Deadlines 2026 →
W26, S26, F26 dates, timelines, and what to submit when.
Data
YC Acceptance Rate →
1–2% overall, ~20% after interview — the real numbers batch by batch.
Playbook
YC Co-Founder Matching →
How to work YC's 150K+ profile platform to find a co-founder who ships.
Batch
YC 2026 Batches →
W26, S26, F26 timeline, deadlines, and what to expect.