3 ms·
There’s a right way to do this and a wrong way to do this. More than a decade ago I started out as a developer on an offshore team for a US based product start
by carlsborg 9y ago
There’s a right way to do this and a wrong way to do this.
More than a decade ago I started out as a developer on an offshore team for a US based product startup. We grew from 2 people to 19 people and the US based company did well in its market and got acquired in a successful exit a few years later.
There are numerous success stories like this for every engagement gone wrong.
Now days I run an India based offshore team from Europe. The cost model has changed dramatically over time, but the premise that you can ship quality code with an India team is very much viable. Every large tech company does it. I’m happy to chat offline if you want.
- maxk42 9y agoI've hired a lot of remote developers over the years and it has pretty much been a flop 2 / 3rds of the time. I had some reasonably good success with Columbian developers a few years back, but the two most outstanding devs I hired on a remote basis were based out of Utah and Connecticut. I hired one a few months ago from Ukraine who absolutely blew the competition away when it came to the coding test, but then failed to actually put in the work hours when he started the job. Any advice for interviewing / hiring remote devs that don't suck?
- carlsborg 9y agoI think the engagement model is equally if not more important than the recruiting. Tie their growth into yours. The startup I mentioned above gave the India team stock options.
- pebcakID10T 9y agoEvery large tech company does not do it. I have worked with more than a few large tech companies whose Indian teams deliver abysmal quality code on a regular basis.