Evaluate the engineers before committing
The client interviewed proposed .NET specialists. Two selected engineers then completed a 40-hour trial so the client could assess their suitability for the product.
Case study · Healthcare
A US medical software company added two dedicated .NET engineers to its internal product team, with weekly task delivery and a communication process designed around a 15-hour time difference.

The situation
The client had a partially developed .NET SaaS product built by its internal R&D team. It sought additional development capacity to move the product forward while retaining control of requirements and technical direction.
The internal team remained responsible for business analysis and high-level specifications. Shinetech engineers completed the development tasks assigned each week.
The approach
The client interviewed proposed .NET specialists. Two selected engineers then completed a 40-hour trial so the client could assess their suitability for the product.
The client’s team defined requirements and technical specifications, while Shinetech delivered the weekly engineering tasks. The recorded environment included .NET 3.5, SQL Server 2005 and Media Player Server.
A Shinetech consultant helped establish the collaboration process. Engineers raised questions for the next day’s tasks in advance so answers could be available when their working day began.
Project context
Technologies and working practices used in this engagement.
The result
Two .NET engineers joined the delivery model supporting the client’s internal team.
Advance clarification addressed the operational challenge of a 15-hour time difference.
Requirements and high-level product direction remained with the internal R&D team.
Tell us about your software, workflows and delivery requirements.
Discuss your project