Are you browsing oDesk looking for WordPress help?
Are you one of the countless folks who heads over to oDesk to look for a WordPress developer? Did it surprise you when you realized just how many developers there were?
The hard part, of course, is figuring out which one to hire, right?
After all, some are really inexpensive, while others are pretty expensive. Some are in the US, while others are halfway around the world.
With so much variance, how do you find someone that's right for you?
Finding the right oDesk WordPress Developer
1. Start with the search term “WordPress”
Rather than looking up Web Development, or any of its sub-categories, use the search at the top of oDesk's website, and type in WordPress. You'll filter down all the potential candidates so that you're only looking at WordPress folks.
2. Use the feedback score as a filter
There's no reason not to use the feedback score as a way to make sure you only review candidates who have made others happy. So I suggest using the 4.0 and above criteria. It will filter out tons of folks that may also be great, but your time is valuable. Getting a smaller list as fast as possible is key.
3. Look for experienced folks
I know you might be tempted to pick someone based on their rate, but don't do it. Instead, head to the experience filter – where you can pick how many hours they've worked as part of oDesk. Pick those with thousands of hours. If you want to make sure these folks are currently “active,” make sure you check the “within the last 6 months only.”
4. Dig into Profiles
Step into the profiles of the remaining list to read the reviews and see people's work history. As you read their bio, you'll discover the difference between SEO / WordPress and PHP / WordPress people. Some folks are users, others are developers. Keep an eye out for that.
5. Narrow things down with questions
As you bring the list to a small group, you'll next want to contact a few developers. To do that, you'll need an account. But once you have it, you'll be able to reach out to contacts and talk about your job. Give them details about your job, and ask for projects that are like it.
6. The final suggestions….
My last suggestion is maybe the most important. And it comes in two parts.
First, don't hire people for your actual project. Hire them for a sample project, small enough that you can afford to lose the money. This is a trial run so that you can determine if they communicate enough, clearly enough, and often enough to your liking. It will also highlight how they work with code (do they give it to you, just show it to you, show the results on their server but not your own, etc).
The more you know and learn, the better off you'll be when you decide to give them your real project.
Secondly, don't hire just one person. Hire 2 or 3 people for the same sample job. Yes, I'm telling you to plan to throw away funds for 3 sample projects up front.
But it will help you compare different developers, see how things work, and help you land on the best person to actually hire for your big project.
Using oDesk can be scary, but these six or seven tips should help you navigate the largest land mines.