So you’ve done all the hard work to source your Ruby on Rails developer candidates. This might have involved making lasting relationships in the developer community. It might have also involved you combing through GitHub projects and finding who had the best commits. It might have even been a referral from one of your other developers. However you found your candidates, you now need to find the right one to fit the position you are trying to fill.
But there’s a catch. Technical interviews take up the valuable time that your current developers could use to build your product. To keep moving forward, you want to hold as few interviews as possible. And there is a solution.