When is it worth it to hire remote developers

When seeking to build a technology business, you require terrific talent. Whether it’s a startup or a massive enterprise, it can be exceptionally challenging to discover premium technical skill. Nevertheless, while planning to hire the very best developers, 2 things must be thought about– cost of hiring and time taken to hire. Often, people try to hire in-house at first and discover that it is expensive and time-consuming. As well as if talent is successfully hired in-house, the efficient hourly rate of that individual when trip, ill time and other benefits are factored in can be higher than that of a contractor.

Nevertheless, outsourcing through freelancers and development agencies (especially with overseas developers) provides its own difficulties and mistakes. Companies typically hire abroad developers since they think they can save cash. The process commonly appears like:

  • Company posts a task on a site like oDesk/Elance/CraigsList/ etc. and gets responses from droves of low-cost developers.
  • Company understands much better than to hire the outright most inexpensive (probably less than $5/hr), so he/she hires a tier above believing that these guys charging more must an indication of quality.
  • Employer’s hires are unqualified and the project begins going south (generally long before the company notifications).
  • Company remains in an code audit/refactor/sunk cost problem.


The issue is that people typically incorrectly think that a larger team is a much better team; that more is more when it concerns hiring programmers. They believe that the ‘right’ hire is a cheap hire. And I think that’s a crucial misconception.

Creating software is more complex than trimming a lawn– just since you hire x more individuals to code does not mean that you will get things done x times faster. It typically suggests that you’re simply spending for x times more code which, at best, is just the incorrect metric to be taking a look at and, at worst, can get you into an impossible refactoring mess where you find yourself learning unscalable and buggy items. Excellent hiring practices aren’t about more; they’re about better.

The phrase ’10x engineer/coder/programmer’ enters your mind: it’s the phenomenon that terrific developers end up being an order of magnitude more productive than their average-level equivalents, since the skill-to-production curve is superbly non-linear. And these 10x engineers– leading developers– can definitely be found overseas, too.

Unfortunately, when companies do hire these senior developers from overseas, I frequently see them incorporated in the wrong methods. It generally goes something like:

  • Company X employs a number of (say three) low-quality, inexpensive developers.
  • Company X then works with a senior developer (who costs essentially as much as the remainder of the group) to handle the others, hoping his/her abilities will increase the performance of the whole group.
  • Company X’s new senior developer invests almost all of his/her time cleaning up after the 3 sub-par associates– the space in class crushes efficiency and the senior engineer can not work his magic.


At the start, the company will think they have made an excellent move by hiring 4 for the price of 2 (i.e. three low-grade and one senior at the price of two senior engineers). However they really haven’t made a fantastic group at all– they’ve simply made a big team. And I believe that the entire will not deserve more than the amount of its parts. I in some cases think about writing code like writing a book; just how much would it help a Pulitzer Prize winning author to have three semi-illiterate colleagues working alongside him? I believe he ‘d be much better off working alone rather than investing his time attempting to make use of what the others have actually done.

To that end, you need to take a look at making overseas hires in a different light and avoid searching for the least expensive– they’re seldom worth your time or money. The preference needs to always be to make in-house/on-shore hires, however when that becomes a severe difficulty (most likely about 5 minutes after you first think you want to build something …), then searching for remote skill can be an excellent option. Recognize that the performance of working with remote talent is getting asymptotically near that of dealing with in-house developers– if the overseas hires are amazing, senior programmers who know what they’re doing; if they can communicate effectively, and take pride in their work. Hire one leading engineer over 3 no ones; and, when you’re ready, group him up with another leading engineer.

Use the best, not the least expensive, and you’ll produce abroad groups who are 10x in their totality: your group’s whole will deserve far, much more than the amount of its parts.

Post a comment