Accelerator Interview Preparation: Build a Clear, Evidence-Backed Brief

Prepare for an accelerator interview by explaining the company plainly, knowing your current evidence, and practicing a real conversation. The goal is to answer the program's questions, not recite a pitch that ignores them.

This workflow turns an application, company notes, and program instructions into a preparation brief and rehearsal log. It can support YC interview preparation, but it is not affiliated with YC and does not predict selection or reveal a private question bank.

What you will leave with

A shared company explanation, an evidence sheet, a list of unresolved questions, and a practical rehearsal plan. Every founder should know which facts are current and which person can explain each part of the business.

You need: the submitted application, actual interview invitation, current company evidence, an honest product description, and the program's official guidance.

You approve: every company claim, materials shared with the program, outgoing messages, and the final preparation brief. Aurora can help organize and practice; it does not submit an application or speak for your team in the interview.

1. Read the actual instructions

Record the date, time zone, participants, meeting link, requested materials, and any stated format. Use the organizer's invitation as the source of truth.

YC's interview advice emphasizes plain language and conversation rather than a prewritten pitch. That article is older general guidance, not proof of a current time limit or interview format. Check YC's current interview page and your invitation for current instructions.

The startup accelerators directory can help compare programs. Once you have an interview, preparation should focus on the specific program and company, not a generic accelerator list.

2. Align the company explanation

Each founder writes a two-sentence answer independently:

We help [customer] do [job] with [plain-language product]. Today, [honest product and business state].

Compare the versions. Resolve differences in customer, product scope, business model, and current progress before rehearsing harder questions. The interviewer should not need to reconcile competing descriptions from your team.

3. Build the evidence sheet

Topic	Current answer	Supporting record	Owner	Open question
Product	Available scope and what is still being built	Current demonstration or product record	Founder	Unresolved limitation
Customer	Who uses it or whom you are testing with	Approved customer or research evidence	Founder	Segment uncertainty
Progress	Results within a stated period	Source record and definition	Founder	Missing or ambiguous measure
Business model	What exists today and what is still a hypothesis	Current commercial evidence	Founder	Untested assumption
Team	Relevant experience and responsibilities	Confirmed biography	Founder	Ownership gap

If a metric is unavailable, say what you are measuring next. Interviews, signups, paid customers, and revenue are not interchangeable forms of traction.

4. Practice a conversation, including interruptions

Use the questions below as an original preparation exercise, not an asserted list of questions any program will ask:

1. What does your company do, and who needs it?
2. What have you learned from real users or research?
3. What can the product do today?
4. What is the most important unresolved assumption?
5. Why is this team suited to the problem?
6. What would meaningful progress look like next?
7. Why is this program useful for your current situation?

Have a teammate interrupt with a request for clarification. Answer the question before returning to any prepared story. If you do not know, distinguish what is known from what you plan to test.

5. Use a rehearsal log

Question	First answer	Evidence gap	Clearer version	Follow-up owner
What do you do?	Actual wording	Jargon or unclear customer	Plain-language answer	Name
What progress exists?	Actual wording	Missing period or definition	Supported answer	Name
What remains uncertain?	Actual wording	Unacknowledged assumption	Honest next test	Name

One useful rehearsal is better than repeatedly memorizing a weak answer. Stop adding material when the important questions can be answered clearly. Use remaining preparation time to resolve evidence and logistical gaps.

Give Aurora the preparation assignment

Use this application, company evidence, and interview invitation to prepare a one-page accelerator interview brief. Separate verified facts, hypotheses, and unanswered questions. Suggest practice questions based on the company, not an alleged private program question bank. Flag contradictions across documents and draft concise answers from the supplied evidence. Do not invent traction, change the application, contact anyone, or claim a selection probability.

Aurora can help organize supplied materials and supported connected context. Keep the approved brief, relevant people, and next steps together in Finta CRM. The founders review the answers and own the interview.

Final check and follow-through

Confirm the meeting time and participants, test the joining setup, and have requested materials ready. Bring a concise list of genuine questions about the program rather than questions answered clearly on its public website.

After the interview, record requests and dates while they are fresh. Send only requested or useful follow-up, with accurate attachments and reviewed claims. The meeting-preparation workflow supports that broader context; this page focuses on the accelerator-specific evidence and rehearsal job.