Where is the best place to recruit Ruby developers?

Here's what you need to do to recruit any cofounder: 1) Prove or at least instill *high* confidence that you can fund the business or raise the funds required; 2) Demonstrate that you are someone worth following. What have you done previously that clearly shows to others that you have what it takes to succeed? 3) Credibly demonstrate that your idea can create massive success. An idea by itself, no matter how interesting is woefully insufficient. 4) Spend every day making outreach (cold emails, LinkedIn, dribbble, etc) to people, meeting at least 3 a week. You will "kiss many frogs." It's likely you have to meet at least 100 people to find the right person and that assumes you have 1-3. By the way, in order to actually *meet* 100 good people, you'll have to make outbound to at least 400 people. 5) Negotiate equity and compensation (pre and post funding) and ensure written alignment on how decisions are made between the two of you. Cofounder relationships are as intense as marriages. And just like getting married, it requires a lot of dating to build the trust. I'm *totally* unconvinced that two people can find a person they haven't known previously, and become effective cofounders. I think you're better off finding the money to hire someone than actually find a cofounder. The main reason? You probably won't find someone as passionate as you are about what you're building. And keep in mind, I have no idea who you are or what you're building so that's no judgement on you or the idea, just the reality I've observed over 20 years of startups.

If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!

I have advised a number of Clarity members on this question exactly. LinkedIn can be a great place to find your technical cofounder. I would look for someone who has been at their current company longer than 18 months and has relevant experience or interest in the problem you're looking to solve. Reaching-out "cold" can work, if you keep your message short and relevant. Here's what a technical cofounder will need to see in order to feel comfortable joining you: 1) That you can fund and/or have raised sufficient money to cover the expenses up to and past launching the first version of your product. 2) That - in their assessment - you have what it takes to raise multiple rounds of funding (if the business is reliant on VC) or that you have what it takes to successfully bootstrap the business. 3) That you are realistic or at least credible in your assessment of the opportunity and have done sufficient customer development to ensure there is a viable market for your product or service. 4) That you and the technical cofounder have sufficient personal chemistry so as to want to and be able to survive an incredibly stressful and emotionally intensive journey together. Happy to talk you through any of this in detail in a call and go into the specifics related to your location, background, and type of product or service you're looking to recruit a cofounder to.

You have to be careful on selecting your co-founder. I know it's an already cliché to mention it, but selecting one is like selecting a spouse to marry. You need to know the person first, and even some investors and accelerators dismiss automatically startups because the founders didn't meet before working together in the startup. If you're doing a tech startup, the co-founder should have a technical background if you don't have it. That will save you a lot of money when you're bootstrapping as well as making sure you deploy a great product as soon as possible. Once you want to work with someone, my best advice is to hire them to do a project or a task inside the startup. More than words, you need to see them in action and that way you can evaluate your chemistry as a team. When you already worked the details and decided to create a startup together, you need to be smart about the plans. You need to sign a partnership agreement and put the equity in a vesting option. In Silicon Valley, the standard vesting period is 4 years with a one year cliff. After one year, the founders fully own of the 25% of their shares. That means if they leave the company before the first year, they will not have equity in the company. Having all that in mind, I think it will help you select the best co-founder possible and also be a better bet to investors if you ever decide to raise money. I hope it helps!

Nearly every high-profile speaker has a website outlining their process, fees, and requirements for speaking engagements. They also have instructions on how to contact and book them.