First, drive. I agree with what he says. What I would like to see him do is to actually suggest ways to follow his suggestions, and some examples of how he ac

First, drive. I agree with what he says. What I would like to see him do is to actually suggest ways to follow his suggestions, and some examples of how he actually followed his philosophy. I've asked him in the comments about this. Such ideas are echoed loudly in business articles, leadership articles, programming articles, and college admissions articles. However, what ends up happening is people still hire those who are "like" them. I've often read many publications and felt like the logic made sense. However, the actions by those people and organizations were heavily biased. I've often read 'literature' and have known that I am that person the organization is looking for. However, people then come up with some crazy reasons to reject those who are different: such as, "if that person was X, he would have done Y by now." All of a sudden, you throw that person's drive and achievements in many different fields out the window, and instead choose based on arbitrary metrics most familiar to them. It's almost like the publicity department and the actual selection committees are two different sets of people... which usually, is actually the case. So, while Marc's observations (similarly echoed by other publications and blogs) are true, the only way to apply these things is to follow Paul's advice: move to wherever the action is so people meet you personally. I'm learning that is the best advice to follow, whether you're applying to college, a job, starting a business, looking for partners, or whatever else. Second, curiosity. Now that Marc mentions that he likes well-rounded individuals with all sorts of backgrounds and a lot of proven drive in many different fields, he says curiosity is next important. He mentions that somebody applying for an Internet company is supposed to have heard about REST, the Facebook API, Google's API, etc. He makes two assumptions in this section: 1) all the best developers have all tried to create a social network with Ruby on Rails in the past 6 months and know about those technologies! 2) if you're young, then therefore you must be using Ruby on Rails to create a web application that implements Google Maps and Google AdSense! That advice is going to eliminate 90% of smart programmers out there. What if they're Windows programmers (probably most of the people out there?) Now, before startup school, I still knew about Amazon S3, REST, and some of Google's API. But I didn't know about techcrunch, or have any interest in creating web applications until I attended startup school. Somebody driven like me, has easily analyzed some of the top frameworks and played with the Facebook API by now, and has had no problems creating a tool in the framework. But I think that's what other people would be able to do, as well! What he's describing is checking for fluency in the "silicon valley scene", not for 'curiosity'. That's great, but at least acknowledge that. Since I am curious, I applied to Startup School and am now more fluent in the "silicon valley scene" because of Startup School, news.yc, and techcrunch. But I couldn't have known web apps were feasible without hearing about those sources. The problem is, his interpretation of what curiosity is, is going to take all those people with "drive" and eliminate them from consideration. In part 1, he says the previous careers and experiences don't matter, but what the person was able to accomplish on his initiative. Then in part 2, he holds the person's current job against them. To paraphrase: "If they are at that job, then maybe they don't really want to work for a cutting-edge Internet company, after all?" HELLO! THAT'S WHY THE GUY APPLIED TO YOUR COMPANY. I see colleges and organizations say they are looking for those well-rounded, self-driven people who are curious and successful in many different fields, saying that what you do matters more than where you came from, then going right on and worrying more about their college ranking in US News and World Reports, or selecting people with an impressive college on their resume, or those who are similar to themselves, and completely disregarding all of the real-world metrics of success they themselves defined in their promotional literature. The reason given? "If that person was X, he would have done Y by now." No--if that person has been successful in many different areas, and you like those that overcome difficulties, then what you're saying is contradictory and self-fulfilling. Third, ethics. I agree with another YC user who says that there is no absolute knowledge. If somebody tries to explain something they know in the best way they can, it doesn't mean they have no ethics. In fact, I would say that's a disservice to the company to judge people like that. Do basic skill tests. It's amazing how many people come in and interview for jobs where their resume says they're qualified, but ask them basic questions about how to do things in their domain, and they _flail_." If you're in agriculture, they may be a good candidate. A lot of people come in and interview for programming jobs who, at their core, can't program. And it's such a breath of fresh air when you get someone who just goes, oh yeah, a linked list, sure, let me show you. Why does he treat young people like they are morons? I would expect somebody who is 24 to understand good UI design, understand the target market, have completed and sold his or her own shareware, understand that results and a quality product matter more than linked lists. As far as programming goes, I would want someone who can build something without errors as they go along. Somebody who understands that criticism from those not in the target market don't matter whatsoever. Somebody who is more concerned about helping to make the world a better place than trying to create the coolest algorithms ever. Somebody who has no problem talking with the actual target market and bouncing ideas, talking to the users, etc. That's just what is expected. For a breath of fresh air, it would be cool if the person has used similar technology in the past, as that wouldn't be too important. In conclusion, I've asked Marc to write some examples where he chose driven, successful, well-rounded candidates who overcame some barriers and different careers (what he writes about in part 1) without penalizing them for not knowing about what's hot in the Silicon Valley right now, or holding the fact that they're trying to work for your company against them--please assume people are intelligent, and if you know they're hard-working and they want to work for your company, then why hold that against them? It's simple insecurity--similar to somebody thinking that if a hot girl hits on them, it must be because she has every single STD. "How dare these smart and driven programmers want to work at this company or attend this college? This is an outrage! They must be applying to this new and very challenging environment because they are lazy and not curious whatsoever!"