You’re an entrepreneur and your startup is based on an amazing business idea. You’ve struck “creative gold,” and now you are ready for the next stage: developing your app.
One of the most important steps—maybe the most important step—is to find a great team: a team that shares your enthusiasm and complements your skillset. For many business-savvy entrepreneurs, one of the first key hires is a technical co-founder.
However, deciding which specific type of technical expert to bring into your startup can be a tough call. Having worked in this industry for nearly 17 years, I have seen entrepreneurs struggle with this. Companies that have thought through the four questions below have fared better than most. Taking the time to go through these questions will help you make the right decisions moving forward:
If someone on your team knows how to read code, this section is not for you. This “someone” can be the founder, an employee, an advisor, or a contractor. If your team includes at least one person who can read code, skip to Question 2.
If code literacy is nonexistent in your current team, then keep reading.
This may not seem obvious, but as a first step, I recommend that you find someone who can read code and make them part of your team as a part time technical advisor. This person will ideally be a seasoned, senior-level person who has seen both success and failure in software development teams. Perhaps they are a serial entrepreneur, or a member of a tech team at an established company.
The key to this first step is that the technical advisor will join your team in a part-time capacity. Why? Because this drastically widens your net of possible candidates. A technical advisor can work two hours a week for you (for either pay, equity, performance based-bonus, or bartered services) and keep their day job.
In terms of how and where to find a part-time technical advisor, I’d recommend asking your network, and your network’s network. This is not something you will post a job ad for. Searched your LinkedIn, Twitter, and Facebook connections, and see who you know. See who your network knows. Tell everyone you know that you are looking for a technical advisor.
Starting this way—bringing in a part-time collaborator to help evaluate the jargon-filled, code-riddled world of technical expertise—is less expensive and less risky than hiring a technical co-founder or a CTO right off the bat. Having this person on your team will pay dividends, and here’s why: finding a competent technical co-founder without the advice of an internal, code-literate member will be extremely difficult. However great your idea, if you cannot read the code a technical candidate presents to you, you will not be able to know whether they will develop your plans the way you envision.
Next, consider this:
This question assumes you have a team member who can read code (aka a technical advisor). Either you found them via Question 1, or someone on your existing team can read code.
Now you are close to hiring someone to build your application. Maybe you don’t have a single line of code written yet. Maybe you already have some code and are looking to raise Series A funding. Or, maybe you have secured funding and are building an MVP in order to get traction with customers.
In any case, I’d recommend sitting down with your advisor or code-literate team member and writing down your answers to the following questions. This exercise will help you think about your near and long-term goals:
With questions 1 and 2 taken care of, you are now ready to find a technical co-founder. Which brings us to the following questions:
In truth, at the end of the day, regardless of title, the job description is the same: this person will be responsible for the creation and upkeep of your code base. If your company grows, this person will be responsible for building out a tech team, and they may or may not manage this team. If your company does not grow, the role of this person will remain close to the code on an ongoing basis.
You and your advisor can decide whether you should title the role Lead Developer, CTO, or Technical Co-founder. I’d recommend actually posting several jobs, some for a Technical Co-founder, some for a CTO, and some for a Lead Developer. I have seen multiple job titles attract different candidates, even if they all have identical descriptions.
How do you know when you’ve found the person you are seeking? It is your advisor’s responsibility to vet the technical abilities of candidates. And it is your job to vet the candidates’ nontechnical qualities. (Going forward, your advisor will also help evaluate the performance of this hire, other technical hires, and any tech-related partnerships.)
Check out these related posts:
I recommend creating a set of acceptance criteria prior to talking to the first candidate. This way, if you find a candidate who passes both the technical and nontechnical vetting rounds, you can be confident that the person is a good fit.
In terms of compensation options, you have multiple arrangements to choose from. You can hire someone full-time, part-time, or contract-to-hire. You can pay salary, hourly, equity, bartered services, or bonus. (Note: There are laws regarding which types of compensation and employee classifications can be tied to specific types of work arrangements. For advice on this, please email me.)
As you embark on hiring a technical co-founder, the last question to consider is:
Finding the right technical expert takes time. Expect it to take about three months. But in direct conflict with this is the fact that startups thrive on getting products to market quickly.
Luckily, the time spent getting product developed doesn’t have to depend on the time spent searching for an employee. You can move forward with your product development while you make your technical hire.
Many entrepreneurs have effectively bridged the three-month gap and bought themselves time to “hire slowly” by outsourcing the first three months of development. They do this by hiring a local consulting firm to pump out high-quality code. Note that this process is not the same as offshoring product development. Rather, it is a means of maintaining the hyperproductivity inherent in all startups.
Someone once told me it was like “renting a brain,” and that’s basically what you are doing. You are paying for experts to come in. You are taking advantage of a team of developers who have worked together already, know how to build high-quality code using modern programming languages and modern technology practices. The word “local” is key. You want people you can physically meet with in person. You are building your vision, and whether it’s in your head, in a Word doc, or in a prototype, it’s still fuzzy and unclear. Colocating, at least part of the time, with the consulting firm is the most effective way to benefit from the three-month “bridge the gap” plan.
As a bonus, while you vet and onboard technical candidates, the consulting firm may be able to help with interviewing and onboarding.
In summary, I recommend that you:
These Stories On People & Culture