You’ve decided to hire Ruby on Rails developer, and you’re starting to wonder how to go about it. You know that the best programmers in the world come from all over the globe, but how do you find them? How do you make sure they can deliver the quality of work you need? How do you keep them on board when their job has ended? This article will help answer your questions and get your hiring process off to a good start!
Things to know Before Hiring Ruby Developer
1) Do you have solid technical documentation?
Even for jobs that don’t require technical writing skills, it’s essential to have technical documentation at your disposal before you even begin interviewing candidates. The best developers will know how to code, but they may not always be familiar with best practices in other areas such as security or scalability. If your Ruby Developer doesn’t understand these things already, then you should definitely develop internal documentation that they can consult while they work on your project.
2) Are your deliverables clear?
The ability to communicate clearly is one of the most important skills in any role. What you think you’re saying doesn’t always match up with what your teammates and clients hear, so it’s essential to speak carefully.
3) What technologies do you use?
In recent years, web development languages and frameworks have become complicated enough that it’s worth asking up front exactly what kind of experience your potential new hire has. Some of today’s most popular programming languages (Python, C#, Objective-C) are all coded quite differently from one another; you don’t want to end up hiring someone who knows nothing about Ruby when you were expecting Python.
4) Do you outsource development?
Whether you’re building an app or tweaking your website, one of your first considerations should be: Do I outsource development? While outsourcing is not for everyone, it does have its advantages. When you hire remote workers from places like Ukraine and India, you can get top-notch work for prices that are sometimes 90% less than what you would pay in North America or Europe.
5) Who will be working on my project?
Make sure you understand who will be working on your project. The reason is simple: if there’s no one actually working on your project, it doesn’t matter whether it has good or bad code. And if you don’t know who will be building your project, run away! That should be an immediate red flag that you need to find someone else.
6) Do you respond quickly when I need help?
The #1 reason I will not hire you is because you don’t respond to my emails and phone calls quickly. I don’t care how busy you are, I don’t care if you get a lot of emails every day – in fact, that shows me you’re probably very successful at your job.
7) How long should it take to develop what I want?
The answer to that question will depend on what you’re looking for. If you already have your own design, but want some help bringing it to life, you can expect things to take anywhere from 3-6 months. If you don’t have an idea of what you want built yet, we’ll spend time getting to know each other, then I’ll give a formal estimate once we know more.
8) Have you ever worked with freelancers?
Freelancers can be great, but it’s important to make sure they are trustworthy before you hire them. Make sure you’re clear on expectations and timelines before you begin working with freelancers; otherwise, there is no incentive for them to hold up their end of things. Be firm about deadlines and spelling out exactly what you want from freelancers when working with them—otherwise, it will all fall apart at some point along your project.
9) Is there an upfront fee?
One of my first questions to all potential clients is, Do you have a budget in mind? I don’t want to waste your time and mine if there isn’t enough money available for what we’ll need to accomplish. Is it an hourly project? A fixed price with milestones along the way? If you have an investment in your idea (that is, it will make or save money for your company), be prepared to pay up front.
10) When can we start our first meeting?
It’s great that you have somebody in mind, but don’t start calling them right away. Make sure they are available and ready to meet with you before you arrange anything. It’s only polite to give them time to respond, after all. Give them at least 24 hours notice; 48 is even better!