As Iâ€™ve spoken to new business-side entrepreneurs recently (even those, like me, with advanced engineering degrees), one of the most frequently asked questions has been: â€œHow do I build an engineering team?â€
It’s a very tough question! In this post, I’ll describe my team’s experience.
REMEMBER – YOU’RE BUILDING A TEAM
When my co-founder and I decided to pursue Catapulter, we knew it was going to be a complex technology, so we couldn’t just run out and â€œfind some engineersâ€. We needed to build a team.
For some perspective on what NOT to do:
Here’s how we did it:
- Ask Experts Who We Need
- Post Jobs & Network
- Get Lucky (Networking &Â PerseveranceÂ Make Luck Happen)
WHO DO WE NEED, ANYWAY?
The first step was figuring out what the Perfect Team would include.
We had a good idea, but we wanted to defer to those who knew from experience. We reached out to as many people as we could find in the entrepreneurial community, to figure out what types of folks would really make the most sense to round out our team.
We met with developers, startup CEOs, VCs, and even a mathematician at Apple, and after a few meetings, we narrowed it down. Besides the fact that we knew we needed a talented CTO (see here why you need a technical co-founder), we specifically needed a mathematician / algorithm guru, and a CTO who could knock out the front-end, but also work with some heavy data processing on the backend.
JOB POSTING & NETWORKING
Now that we knew who we were looking for, we started networking and posting jobs everywhere we could think of.
The easiest way to find a high-quality co-founder is through someone whose opinion you respect.
We basically set up as many discussions as possible with folks in the entrepreneurial community, particularly developers, to find someone who might be interested.Â First, we asked friends who they knew, then asked those people who they knew. (Whether or not you find someone, youâ€™ll definitely learn something!)
You may have the â€œperfect personâ€ in mindâ€¦but the best folks usually have plenty of projects to work on. Thereâ€™s likely going to be quite a bit of luck involved â€“ whoâ€™s super-pumped about your idea, who happens to have the right experience, and whoâ€™s available.
Another way to find folks is by posting to job boards and email lists.
We received a number of quality applications through both entrepreneurial email lists like the Philly Startup Leaders and school job boards like UPennâ€™s. (We also got a lot of noise, so be prepared to screen!)
With school job boards, thereâ€™s a timing consideration based on when each of the various divisions of the school searches for jobs. It turned out that one specific engineering school was recruiting when we posted our Algorithm Developer position, and we received a huge number of applications from that group.
For tips on job postings / intro emails, check outÂ this post from a Penn CS Major.
One important note: If youâ€™re not a developer yourself, there are going to be some people who tell you youâ€™re just a â€œbusiness personâ€, you’re useless, and no engineer should ever talk to you. There are certainly folks for whom thatâ€™s trueâ€¦just donâ€™t let it be you!
We found our first team member (our Lead Algorithm Developer) through a school job listing. He wrote one of the few cover letters we received (about his genuine interest in algorithms!), had excellent routing/networking experience, and was a leader going in. We interviewed a number of folks, but he stood out at the interview. He didnâ€™t overpromise, he told us what he could and couldnâ€™t do, but was confident that he could figure out anything.
And he freaking rules.
From the same job board, we found a few students who were interested in the CTO position. We ended up selecting one particularly energetic student before a final round startup accelerator interview…
GETTING LUCKY, PART I
In our interview, the partners of the accelerator gave us the business, and really pushed to figure out how talented our new teammates were. A few days later, our new CTO called and told us, without explanation, that he was out. Shortly after, the incubator called and told us they liked the idea and the teamâ€¦except for our CTO.
At the time, we were bummed out. We were so close…but now we were a tech startup without a CTO! We didn’t realize how lucky we were to have another opportunity to find the right person.
In any case, we knew we needed to figure it out, FAST!
GETTING LUCKY, PART II
We hit the phones again, now networking with people we knew who already had great jobs. We knew it would be tough, but we also knew we had a fantastic idea, an awesome algorithm developer, and a real opportunity.
Running out of network, I called up one of my college buddies, a super-talented engineering classmate of mine who already had a fantastic job. There was no chance he’d leave, so I decided to ask if he had any friends who might be interested.
Howeverâ€¦by an amazing coincidence, it turned out he had recently built a trip planning website in his spare time! AND he was the jack-of-all-trades type of guy who could knock out the front end but work on the heavy processing in the background. AND he happened to be casually looking to join a startup. Booyah.
Thatâ€™s what networking gets you. You make your own luck. And now we had a CTO.
GETTING LUCKY, PART III
With the new team, we spent the summer at Betaspring building our alpha product and beginning to test with users. At this point, our database was rapidly expanding, and we wanted an experienced engineering leader to focus on managing the growth of our technology, and our growing data acquisition and storage needs.
Over the summer, we had continued to network and post on job boards, but hadnâ€™t found anyone. We had been interviewing a number of candidates through the normal channels, but none really fit the team
Then one day, while cleaning out my email, I found one that had slipped past…
Well after we had selected a CTO and began at our accelerator, a really talented candidate who fit the bill had sent us an email. He had experience as VP of Tech/Product at other heavy-data startups, where he had guided nascent technologies through rapid growth.
It only took a couple of phone calls and a video chat with the writer of this email, but it was clear he was the man for the job.
PIECE OF CAKE, REALLYâ€¦
And like that, we had three killer engineers making up Catapulterâ€™s core team.
The perfect team needed a jack-of-all-trades CTO, an algorithm developer, and an experienced data-processing guru and technology leader, and somehow we got them all.
The main take-away for me: you have to network, and you have to try everything. It took a ton of legwork, but as a result, we built the absolute perfect team.
It was totally worth it.