Developers: How to get Hired by Every Startup You Contact

http://www.amazon.com/dp/0596529325?tag=loucalnet-20&cam...;

There are three reasons why I would suggest that you don't emphasise the proficiency in Ruby. The first is, as mentioned above, that you're probably overestimating the effort required to switch platform at this point. The second is that a good programmer who just happens to have no/limited experience with Ruby will probably be able to adapt pretty fast, provided he has experience with similar technologies. By limiting your search to those that already know Ruby well, you're avoiding a lot of potential.

But the main reason why I think it's a bad idea, is because you are making decisions that I believe is the domain of a CTO to make. By doing so, you are sending a signal that you don't respect/trust him to make that decision. That is going to make the type of person you'd want onboard think twice about joining. I'm not suggesting that you actually feel this way (I don't know you, so I couldn't pass that judgement), but you should be aware of the way it will read to - at least some - people in your target demography.

I would be extremely wary about joining a tech start-up that has to go through an open job application process for a CTO. If the founder can't make enough of a believer out of someone within his or her own network to join, I would see that as a bad sign -- not just in terms of the start-up's idea but also the founder's ability to sell his or her idea. If it's the case that the founder doesn't know viable candidates in his or her own network, then I'd be doubly concerned: it's a tech start-up and a strong network within tech circles will be necessary for other resources down the line (future engineering hires, advice, potential investors that add value to the company, etc). Additionally, if s/he isn't really plugged in to the tech community, I'd worry that s/he doesn't truly understand the business, my skills as it relates to the business, and the value that I bring to the table. And in this particular case, I'd also be concerned that social networking is what this start-up revolves around and the founder (again, from my limited view on the outside) doesn't appear to be able to network effectively enough to at least get introductions to suitable CTO candidates through secondary connections.

I'm not saying that this is necessarily the situation here but that's my thought process just based on the information available. I consider things like sales ability, existing network and hiring ability to be essential things for a non-technical founder to bring to the table before I would consider working for him or her -- otherwise, I'm almost as well-off starting my own thing and own a hell of a lot more equity.

There are a handful of non-technical people I know that I would join in short order if one of them ever called to talk about a job at his or her start-up. And if I declined I would refer them to other people I know that might be interested because I know no matter what he or she is doing, s/he has a great chance of succeeding. If you're not the kind of person that inspires that level of loyalty, being a lone non-technical founder at a tech start-up seems like it would make an already arduous journey incredibly difficult.