Gino Ferrand


This article is a part of our encyclopedia, and is editable by you. Edit ➜


Gino Ferrand is an American entrepreneur. Gino started TECLA in 2013 and is based in Seattle, WA.[1]

Gino Ferrand, founder of TECLAGino Ferrand, founder of TECLA

Company

TECLA

Twitter

@ginoferrand (132 followers)

Career

Early Career

No early career info added yet...

TECLA

Gino started TECLA in 2013. They detail the beginnings of their company in their Starter Story interview: [1]

Q: How did you get started on TECLA?

I started TECLA fortuitously, and as a result of working (and failing) on a completely different business. In 2011 and 2012, I was working on an online mobile (sim) game that was going to be published in the AppStore and PlayStore. I was studying at the University of San Diego at this point and in my senior year. My skills were mostly in iOS programming, UX and UI design and so I was badly in search of backend software engineers who could work with me to bring this game to life, but I had some technical challenges:

  1. I didn’t want to outsource the project to an agency. I wanted to build my own team.
  2. I didn’t have the right network to find a co-founder.
  3. Most of my friends in the Computer Science department were already being hired by Facebook, Google, and other tech giants in Silicon Valley and they had no interest in working on a mobile game.

So...

I did what a lot of people do in similar situations. I started running Google searches looking for ways to hire backend software developers. Got into Upwork (previously oDesk), Guru, Elance and some other sites that offered freelance talent.

> Not every startup needs VC investment, and growth doesn’t have to “explosive” for a venture to be a good business.

It was a hit or miss process on those freelancing sites. For me, at least. But the whole process validated a few things:

  1. There are very talented engineers all over the world
  2. The sourcing and recruiting process on these sites can be hit or miss, inefficient, and too time-consuming
  3. Time zones made it extremely difficult to collaborate with my team in real-time

Then, I got a big break, and through a mutual connection in Lima, I ended up meeting our current CTO. When this happened, I remember asking myself, “Why in the world have I not been recruiting back home in Lima?”

The game was eventually released and we got about 100k installs. It was a minor, but worthwhile success.

(Bear in mind this was in 2011/2012)

how-i-started-a-85k-month-business-connecting-companies-with-tech-talent-in-south-america PRO Footballer: the mobile game we published in 2012

After a decade of living in the U.S., I decided to move back to Lima. I would lower my living costs substantially, and build a remote team based out of South America to continue working on the game.

I hired a great backend engineer with 10+ years of experience who lived in Chile and an iOS developer who lived in Lima who had previously worked on projects for Google and IBM. I decided not to spend cash on an office, and so we all worked from home.

how-i-started-a-85k-month-business-connecting-companies-with-tech-talent-in-south-america Early 2011/2012 team

Game Version 2.0 was looking promising...

But, before we could even work on the game for a full two months, I already had other small companies reaching out interested in me building a remote team in South America for them. All through word of mouth and LinkedIn.

I continued working on the game for some time, but I quickly realized that the process I had developed for remote recruiting in South America was something that addressed all of my own pain points, and it seemed that other companies had been struggling with the same issues when it came to remote hiring (time zones, sourcing, and efficiency).

My recently hired team liked the vision I proposed for TECLA, and we went with it!

how-i-started-a-85k-month-business-connecting-companies-with-tech-talent-in-south-america Early presentation deck 2012

how-i-started-a-85k-month-business-connecting-companies-with-tech-talent-in-south-america

Source [1]

References