Justin Kan is going to be the new spokesman for YC and handle the PR requests we get.
We have a lot of new additions to the team to announce.
Tim Brady is joining YC as a Partner. Previously, he was a Partner at ImagineK12. Tim was Yahoo’s first employee and spent 8 years as the company’s Chief Product Officer. Tim was also the CEO of QuestBridge, an educational startup that helps bright low-income high school students gain admissions and aid to many of the nation’s best colleges. Tim has an MBA from Harvard and a BS in electrical engineering from Stanford.
Chris Clark is joining YC Research as head of operations. Chris previously ran operations at Loopt, which was funded by Y Combinator in 2005 and acquired by Green Dot in 2012. More recently, he was Mayor of Mountain View and still serves on the city council. Chris has a BA in Political Science from Stanford University.
Bill Clerico is joining YC as a Part-time Partner. Bill is the co-founder and CEO of WePay (YC S09), a payment company for two-sided marketplaces and software platforms that helps them manage risk. Previously, Bill was a technology investment banker and studied CS at Boston College.
Cadran Cowansage is joining the YC software team. Cadran most recently worked for MongoDB, Inc. in NYC. She has a Master's in Biomedical Informatics and previously worked in several industries, including healthcare, intermodal transportation and finance.
Jason Kwon is joining YC as a lawyer. Before joining Y Combinator, Jason was the Assistant General Counsel at Khosla Ventures, and prior to that, an attorney at Goodwin Procter. In his past life he was also a coder and product manager at several startups.
Karen Lien is joining YC as Edtech Principal. Karen was previously at Imagine K12, which she joined in 2011 to help launch its first cohort of edtech startups. Before Imagine K12, Karen was the Director of College Relations at QuestBridge. Prior to QuestBridge, she briefly taught high school chemistry, getting a first-hand taste of the challenges and rewards of working as an educator. Karen has a B.S. in astronomy and physics from Yale University and an M.S. in astronomy from UCLA.
Brad Lightcap is joining YC Continuity. Brad brings experience in both finance and operations. He joined Dropbox in 2013 where he worked on projects ranging from product/partnership analytics to corporate finance and M&A. Prior to Dropbox, Brad was an analyst with J.P. Morgan's Healthcare Investment Banking group in New York.
Sharon Pope is joining YC as a Part-time Partner. Sharon is currently the Chief Marketing Officer at Green Dot Corporation (a pro-consumer financial technology innovator), where she has worked to conceptualize and launch products for Americans who seek alternatives to big banks. Prior to Green Dot, Sharon was the head of marketing and communications at Loopt (acquired by Green Dot, 2012).
Tom Sparks is joining the YC software team. He is a systems and network engineer with over 20 years of experience in the field. He's worked for Microsoft, realtor.com, some of the Fortune 100, an early groundbreaking music startup and was one of the founders of one of San Francisco's largest ISPs. He cofounded Cryptoseal (YCS11), which was later acquired by Cloudflare.
Finbarr Taylor is also joining the YC software team. Finbarr previously co-founded Shogun and worked for Pebble, Exec and Groupon. Before that, he studied CS at Strathclyde University in Scotland.
Catherine Uong is joining YC as an Associate. Catherine was previously at ImagineK12, and is passionate about learning and the power of creativity to help unlock students’ potential. Catherine has a B.S. in Business Administration and a B.A. in East Asian Languages and Cultures from University of Southern California.
We've modified our fundraising strategy advice to YC founders. In the interest of everyone having the same information, here is the email I sent to the current batch this morning.
Founders--As Y Combinator's prominence has grown in recent years, we've seen a flood of new investors who are very focused on investing in YC companies in the current batch. Some of these investors are very aggressive and offer attractive terms with no diligence. There are obvious good things about this, but there are really bad ones too. We're now about a month away from Demo Day, which is when the investor outreach usually starts in earnest (as we've said before, we recommend politely deferring these requests to meet until closer to Demo Day).
We’re going to try something new—our first Request For Research.
A new trend in Y Combinator applications is that an increasing number of applicants have already been through some sort of accelerator or “pre-accelerator” program. As we’ve dug into this trend, we’ve found that many of the applicants did these programs not because they needed the money or advice but because they thought it might help them get into YC (and specifically that some programs market themselves as a "way to get into Y Combinator).
Actually, it's much harder to get in to YC if you’ve already been through another accelerator. We assume that a group that has already been through an accelerator should have been accelerated, and that if they don't have impressive progress something must be wrong. (A smaller issue is the extra dilution on the cap table.) We now have enough data to know that the track record of companies that go through multiple accelerators is much worse than companies that just do YC.
We fear that there may be cases where groups are hurting themselves by participating in bad accelerator programs that don't accelerate them and yet also raise the threshold they'd have to get over to get into YC. It’s certainly not a deal-breaker—and we are extremely sympathetic to the need to raise money in any way possible—but it does increase our expectations quite a bit.
So we want to remind everyone explicitly: if you want to get into Y Combinator, just apply to Y Combinator or the YC Fellowship. In both cases, we like funding very early-stage companies. You don’t need to “prepare” to apply to YC in any way. You should only do an accelerator if you need the money to survive or think that the resources of the accelerator will help you be more successful; you should never do one as a way to get into YC.
Speaking of that, since we can’t yet fund every good company in the world, here is some general advice about evaluating accelerators:
*Talk to the alumni and ask how strongly they recommend it. This is the best possible data you can get.
*Look at the accelerator’s track record (it’s important to distinguish between companies that went through the accelerator and cases where the investment firm made a small late-stage investment in the company). This will give you a feeling for how good the accelerator actually is, and also a sense of how much external validation you’ll get by participating.
*Look at the strength of the alumni network. You want to join an accelerator that has (1) eminent alumni who (2) really care about helping other companies in the family. You’re joining a network, and more than anything else except perhaps the advice, this is where you’re going to get value.
*Pay attention to how an accelerator treats you before you join, when they should be on their best behavior—it’s likely to be an indicator of how they’ll behave later. Doing founder-unfriendly things like presenting exploding offers does not correlate with good behavior down the road.
Y Combinator now has 5 major groups—YC Fellowship, YC Core, YC Continuity, YC Research, and Hacker News—and we’re putting one person in charge of each group.
Paul Buchheit is taking over for me as managing partner of the core YC program.
We’re going to continue doing YC Fellowship (!), and Kevin Hale is going to be the managing partner of that.
As we’ve already announced, Ali Rowghani is the managing partner of YC Continuity, and Dan Gackle runs Hacker News.
As YC's President I will spend my time across the three investment programs (YC Fellowship, YC Core, and YC Continuity), and will also run YC Research until we find someone to run it full-time.
Additionally, Kirsty Nathoo is going to be the CFO across the entire YC group, and Carolynn and Jon Levy are going to be the General Counsels across the YC group too.
While we’re on the topic of who does what, I wanted to share two other roles that people outside of YC ask about a lot. Each partner at YC is responsible for specific areas, but these are the ones that interface with external people most often.
Dalton Caldwell is going to be responsible for admissions to the core program and also for our efforts to stay engaged with alumni companies.
Kat Mañalac is responsible for the outreach efforts we do to meet potential new founders, and she'll also be working closely with Kevin on the Fellowship.
Finally, we have a few new additions to the team to announce.
Matt Krisiloff is working with Kevin on YC Fellowship (he’ll also be doing some work on YC Research). Matt previously co-founded a mental health directory that helped people find good therapists, and before that he studied at University of Chicago.
Denis Mars is working with Dalton on admissions for YC Core. Denis is a YC alumni (he was the founder of Meetings.io) and the founder of several other successful companies. He was also the Chief Engineer of a Formula 3 championship-winning team.
Verena Prescher is working with Kirsty as the Controller of YC Continuity. Prior to joining Y Combinator, Verena was the Controller at Felicis Ventures. Previously, Verena was a tax manager in PwC’s Asset Management practice, providing tax compliance and consulting services to investment partnerships with a primary focus on the venture capital and real estate industries.
YC will fund its 1,000th company this year, and many of these companies are now scaling their organizations, revenue, and operations. Though years removed from our program, these founders continue to come to YC for advice and support, and we would like to do more to help them.
To that end, I'm delighted to share that Ali Rowghani has joined YC as a full-time partner. Ali has quickly become a trusted advisor to many of our growth-stage companies, and is helping a great deal with our vision of continued support for our alumni companies after they finish our program.
Also, in response to requests from a number of YC founders, we've raised a new fund called the YC Continuity Fund, which Ali will be running. This fund will allow us to support YC companies well after Demo Day in two primary ways.
First, we're going to do our pro rata investment for every YC company in every round with a valuation below $300 million. We believe we generally pick good companies for YC, and we want to be able to continue to support them in future financings.
Second, we will consider leading or participating in later stage growth financing rounds of YC companies. We are open to taking Board seats where it makes sense for founders, but do not expect to do so in every investment. We hope to be a founder-friendly partner for maturing companies in the same way we have been a founder-friendly early-stage investor. Also, there are some companies we think are very good and important to support with growth-stage capital that traditional investors are less excited about, and we're looking forward to being able to do that. Finally, we look forward to being a very long-term focused investor in a sector where most players are not.
We also want to be very clear on what we're not doing. We are not pursuing investments outside of the YC portfolio. We are also not leading seed or traditional Series A rounds or trying to otherwise disrupt early-stage VCs, whose participation in the ecosystem is very valuable. It'd be the wrong thing for our companies, as it would both create massive signaling issues for companies we didn’t fund and deprive companies of valuable additional advisors. By doing pro rata in every company, we should avoid any signaling issues.
Our mission at YC is to be the organization that enables the most innovation in the world. Capital — especially long-term capital willing to invest outside of the current trends — is an important ingredient in that mission, and I'm excited we are now able to better support some of our companies. In doing so, I hope that joining YC is an even better deal for companies just starting out.
I'm delighted to share that Jared Friedman is joining YC as a full-time partner. Jared co-founded Scribd, the world's online library, which was funded by Y Combinator in 2006. He was the CTO there. Jared has also been an investor in more than 30 YC companies. Before Scribd, he studied computer science at Harvard.
There are now 16 full-time partners at YC.
Our mission at YC is to enable as much innovation as we can. Mostly this means funding startups. But startups aren’t ideal for some kinds of innovation—for example, work that requires a very long time horizon, seeks to answer very open-ended questions, or develops technology that shouldn’t be owned by any one company.
We think research institutions can be better than they are today. So we’re starting a new research lab, which we’re calling YC Research, to work on some of these areas.
We’re going to start YCR with one group (which we should be ready to announce in a month or two) and if that goes well, we’ll add others.
YCR is a non-profit. Any IP developed will be made available freely to everyone. (The researchers will, of course, have full discretion over when they’re ready to release their work, and we’ll have a process in place to address technology that could be dangerous.) Because of the openness, the researchers will be able to freely collaborate with people in other institutions.
We’re not doing this with the goal of helping YC’s startups succeed or adding to our bottom line. At the risk of sounding cliché, this is for the benefit of the world. As we’ve seen throughout history, new technological breakthroughs help all of us. Fundamental research is critical to driving the world forward, and funding for it keeps getting cut. 
To start off, I’m going to personally donate $10 million, and we will raise more money for specific groups soon.
YCR researchers will be full-time YC employees (instead of us making grants to other organizations). We’ll especially welcome outsiders working on slightly heretical ideas (just like we do for the startups we fund) and we’ll try to keep things small—we believe small groups can do far more than most people think. Also, smallness usually means less politics, which has plagued science in recent decades.
The researchers will have full access to YC and the YC network. YC has a very high problem flux at this point—we fund hundreds of companies per year. Compensation and power for the researchers will not be driven by publishing lots of low-impact papers or speaking at lots of conferences—that whole system seems broken. Instead, we will focus on the quality of the output.
We plan to do this for a long time. If some of these projects take 25 years, that’s perfectly fine with us.
We’re very excited to see what comes out of this.
 Funding for technological development is actually relatively high, but funding for fundamental research keeps getting cut. Investors want to fund incremental progress—and the world has gotten very good at delivering that. This is more valuable than it sounds; incremental progress compounds quickly.
But it’s not all we need—we are dependent on the unpredictable breakthrough jumps to drive humanity forward. Technology startups today work very well for making a super-efficient piston engine, but they are unlikely to fund the kind of open-ended R+D required to develop a jet engine.
The HN community feels like it owns HN, and we like it that way. HN has become an important institution in the tech community, and though it was initially developed for YC founders it's clearly evolved into much more than that.
We've always felt that the best way for HN to benefit YC is simply for it to maximally benefit the community, which mostly means keeping the story and discussion quality as high as possible. We read it ourselves, so we want that as much as anyone.
In that spirit, we have a couple of announcements to make: an organizational one from Sam, and a moderation one from Dan.
Making HN autonomous within YC (Sam)
We're going to factor out Hacker News into its own autonomous unit of YC. It has de facto been like that, but it feels like a good idea to make it official. Going forward, HN will no longer formally be part of the investment branch of YC, but will be its own separate thing.
Everyone at YC knows that it's vital for HN to have full editorial independence, and we have absolute trust in Dan's decision-making in product, engineering, and moderation. Dan will report directly to me, though I don't plan to be very involved--other than as an enthusiastic user (who would, however, prefer that it be easier to read on a phone) and someone who's always happy to bounce around ideas. We're also setting it up so that Dan will have the option of reporting directly to the YC Board of Overseers instead if he ever decides to.
Dan is an incredibly talented person who really understands the art and science of HN; I'm excited to see what he has planned for the future.
Modnesty I: More Community Moderation (Dan)
HN's approach to moderation has always been three-pronged: software automation where possible, human intervention where necessary, and as much community moderation as users can provide. Our long-term vision for HN is to have the site be as self-regulating as possible, and we've been working on a project code-named Modnesty (for 'moderation amnesty') to develop new ways to do that. Today we're releasing the first experiment from this project. The idea is to let the community make the final call on decisions made by HN moderators and software.
Currently, when an account is banned, a software filter trips, or enough users flag a post, the post goes [dead], meaning only users with 'showdead' turned on in their profile can see it. The trouble is that some posts end up [dead] when they shouldn't be. Banned accounts sometimes post good comments, software filters sometimes have false positives, and users sometimes flag things unfairly.
Today's new feature lets users rescue [dead] posts on a case by case basis. Beside the 'flag' link, you'll see a 'vouch' link to click when a post should not be [dead]. When enough users vouch for a post, the software will unkill it. Think of vouches as the inverse of flags: a flag says that a post shouldn't be on HN; a vouch says it should.
We'll review all vouched posts to make sure that they don't violate the HN guidelines. If we notice abusive vouches, we'll take away vouching rights (again, by analogy with flagging), so please vouch responsibly! Only rescue civil, substantive contributions to the site.
You need a little karma (currently 30) to see flag links, and the same threshold applies here. If you don't have 30 karma but would like to participate, email firstname.lastname@example.org and we'll try to help.
I called this feature an experiment above. We'd like everyone to understand that when we say 'experiment', we really mean it. It's important to us to be able to roll out new ideas and drop the ones that turn out lame. HN's simplicity is its core design value, and we shudder at the thought of only adding features and never removing them. The freedom to retract bad experiments (like we did recently ) enables us to try more things, which benefits HN most in the long run. So if Modnesty turns out to have unintended bad consequences--which I hope won't happen, especially since we've been testing it for a while--we'll withdraw it. As always, whether it turns out bad or good is mostly a function of your feedback, so please be generous with it!
1. See my edit of https://news.ycombinator.com/item?id=10223645.