News for hackers. Stuff that matters.
Re:What We Should Have Said To PG by mindcrime on Monday July 09, 2012 @01:43PM (#4219317)
Sure, I get that. What I was saying is, would it not potentially be better go give the founders some time to give their thoughts in the order they have them in... before starting to go off on tangents and probe specific areas? Especially considering that the question you're about to ask, may be something they're going to be answering anyway.

I guess that if pg and crew believe that they learn something by intentionally knocking people out of their planned routine, then that's one argument for it. That is, if the idea is "we want to evaluate your ability to think on our feet, react to unplanned questions, etc." then OK.

Re:What We Should Have Said To PG by pg on Monday July 09, 2012 @03:40PM (#4219996)
They've already explained their ideas in the form they chose in the application. So the interview starts with questions we had after reading it.

We don't try intentionally to knock people about to see how they respond. We don't have the time or the energy for such games. We just have a lot of questions and not much time to get them answered, and empirically the questions we have almost never turn out to be the ones answered in prefabricated pitches.

Re:What We Should Have Said To PG by mindcrime on Monday July 09, 2012 @04:04PM (#4220114)
We don't try intentionally to knock people about to see how they respond. We don't have the time or the energy for such games.

That's good to know. I think some people have somehow gotten the perception that you guys do just that.

We just have a lot of questions and not much time to get them answered, and empirically the questions we have almost never turn out to be the ones answered in prefabricated pitches.

Fair enough.

Re:What We Should Have Said To PG by hef19898 on Tuesday July 10, 2012 @02:28AM (#4222406)
Do I understand it right then that what one might call "idea pitch" has already been passed once you are being interviewed? Because in this case it makes sense to ask "random" questions.

Before I read the discussion I kind of shared the op's point. But seeing it from the other perspective, it almost seems like the basic "fault" (if you might call it that) the op made was preparing for a test he already passed.

Re:What We Should Have Said To PG by drupeek on Tuesday July 10, 2012 @11:22AM (#4224204)
In my preparation between the accepted application and the interview, I was cautioned that the interviewers will not remember your application when you walk in the room.

Is there truth to this?

Re:What We Should Have Said To PG by why-el on Monday July 09, 2012 @02:04PM (#4219460)
As I understand it, random access just means asking you about different facets of your products, probably in the same way you and your teams have been thinking about and solving problems related to your product. You did not sit during Day 1 and outlined every single problem and feature you will support did you? There is randomness involved in your journey towards evolving a products, and that randomness already answered most of the questions PG might have asked.
Re:What We Should Have Said To PG by wilfra on Monday July 09, 2012 @01:59PM (#4219426)
Remember that YC backs founders much more than ideas. Also remember that they've already vetted both the founders and the idea, with the help of YC alumni, prior to the meeting. I would also imagine they have a strong aversion to BS and a well-honed BS detector.

Ignoring the pre-packaged pitch you have spent months preparing and asking you some unexpected questions would seem to be a great strategy to quickly figure out what they really want to know - which may or may not have any relation to what you want to tell them.