I talk to a lot of startups. I have a lot to say about what (not) to do if you are on the hiring side of this exchange, but for now I'll cover the minimum set of information you should be prepared to discuss if you want to hire a developer for your early-stage company. This is the first real interaction you'll have with a potential coworker. If you struggle with convincing someone to join your company, you can bet you'll struggle with convincing someone to buy your product or service, so you should be prepared with the information a potential hire will want to know. These are questions I will pretty much always ask you about your startup in an interview, and they're pretty similar to what a VC would want to know. When I say "I" below what I really mean is "any developer" but it's more convenient to write in the first person.
But I have this little note at the top of
I've been building open-source social networking software for the past four years, which has given me the unique opportunity to be involved in a wide variety of projects to build social networks and related tools. My experience has revealed a number of insights into the way that user interaction patterns are designed on websites that encourage a website's engagement and adoption to the point that it can grow organically from almost nothing – or, conversely, that doom a website to silent irrelevance in a distant corner of the web.