You can not scale your R&D with copies of your employees

Serengeti

Business

10.07.2019.

featured image

True story: The software product development team is 8 people. The average age in the R&D is 31. All engineers work for the company for at least 3 years. Everybody in the team can jump on various tasks like database, middleware, UI, report generator – even testing! Team needs to grow for 2 or 3 more engineers. Job ad published on several portals for already 10 months but no candidate matches the desired skill profile.

Sounds familiar? Here's why...

Your expectations on the labor market are not realistic

The skill profile you are asking for does not exist outside of your own company. No one except you uses the same combination of technologies. Well, maybe your competitor does...

Alternative: Nearshore software development?

Your thinking: Ok, the DACH market lacks about 1 million IT experts. That might be the reason why no candidate with matching skills apply. Let's outsource some work to one of the 5000 custom application development companies in South or East Europe!

That must be possible, right? Short: nope!

Characteristics of custom application development companies

A successful nearshore software service provider is highly optimized for 3 things:

  • recruiting new talents from a big pool
  • have experts available for their clients in zero-time
  • avoid people to sit around a client scales team down

As you can imagine "a good C++ developer with WPF experience and some Oracle PL/SQL knowledge" is not something a service company is very eager to offer.

  • recruiting such profiles is not a standard process. It's more looking for the needle in the haystack. It takes time, doesn't for the standard recruiting process and is therefore expensive.
  • since the recruiting process takes long such candidates won't be available to the client in zero-time. Very likely the client moves on before a candidate can be identified.
  • Due to this very individual skill requirement, there's a very high risk that when the client scales down at some point the candidate has no follow-up project with another client. A lose-lose situation for the service provider and for the engineer.

That is the reason why it is very unlikely to find those special skills within software services companies.

So, what's left? How to solve this problem?

There is no short term solution to the problem. The mid term solution is to leave the existing comfort zone and realize as soon as possible that such engineers can't be employed nor subcontracted.

A reorganization in the software development team is needed to be open and ready for scale. Existing team members, even if they are allrounders, have to specialize and build subject matter expertise instead. A new team member, employed or subcontracted, with a limited but realistic set of skills can join a subject matter teams instead of being an allrounder.

Subject matter-centric documentation, onboarding and trainings, as well as a smart assignment of tasks are required to make that shift.

Few nearshore software development companies (Serengeti is among them!) do help their clients on that journey in regular coaching sessions while doing a real project together.

Contact us if you are facing similar challenges.

While you are here, you can download the Checklist - Choosing the right nearshore partner for your software product development:

RELATED

19.07.2019.

Checklist: Choosing the right nearshore partner for your software product development

What's Inside?

  • Why product development is different 
  • Top non-skilled-based requirements 
  • Pick your favorite from 5000 in CEE
Read more

01.07.2019.

A Guide: How to successfully manage a distributed software development team

Rise of distributed team popularity, especially in software development, is sometimes due to specific project needs, but in most cases, it's driven by the inability to hire the appropriate talent locally. Therefore, the need for establishing and successfully managing a distributed team is steadily becoming increasingly important.
This guide encompasses relevant experiences, practices, and recommendations, all of which aim to facilitate the art of successfully running a distributed software development team.

Read more

03.06.2019.

The importance of engineering team stability

Turnover can be especially bad for engineering / development teams, because losing crucial knowledge from a dev team can set back the entire road map. If a great performer in marketing leaves, that would also be a loss, but the tactics of marketing can usually be picked up by the rest of the team. When a great developer leaves, though, you lose both knowledge and skill that can have massive implications for future product/service development.

Read more