If you’ve ever spent any time looking for a web developer, you know how difficult it can be. I just did a quick Google search for “Denver web developer” and got nearly 4,000 results.
So how do you narrow your often overwhelming choices? Just like any college or company would when reviewing applicants: create some benchmarks and throw out everyone that falls short. Here are 5 things you should look for when hiring your next web developer:
- Location
- Good communication
- Responsiveness
- Someone who understands your business
- Good policies
#1. Think about location
What if you find someone you really like, but that person is in another state, or even another country?
In my experience, it’s possible to conduct almost any web-related business remotely. Services like WebEx allow you to share your computer’s desktop, while DropSend and plain old FTP allow you to send large files with ease. You can always call or email your developer for everything else.
If distance isn’t a limiting factor, then don’t let it get in the way. If, however, you prefer meeting face to face with your developer (as some of our clients do), then you should limit your search. Pick a maximum distance from your office that you are willing to travel, and limit your search to that distance.
#2. Your developer should speak your language
One of the biggest complaints we hear from clients is that their former developer was hard to understand, that he or she didn’t “speak my language.”
Before hiring anyone, be sure to have at least a phone call or an email exchange with that person. The phone call is your chance to build rapport with the developer, and to see how he or she communicates. If you find yourself feeling frustrated or lost while talking to him, chances are you’ll feel frustrated during the project.
A good developer adjusts his language to your level of expertise so you never feel confused or overwhelmed.
An email exchange with your potential hire is essential. For one, it helps shed light on how quickly he or she responds to emails. A quicker response indicates that he is more likely to be responsive during a project (see below). An email exchange will also show you how he writes. Ideally, your developer will write as clearly as he speaks.
#3. Your developer should get back to you, and quickly
Response time is key, especially for projects with tight deadlines. You should be able to rely on your web developer to get back to you same day, ideally within one to three hours by email (sooner by phone) during business hours.
You should expect this response time because, at any given moment, the typical web developer is within one to five feet of his or her computer, email client open and flashing anytime a new message arrives. If you don’t hear back within 24 hours, you should probably move on to the next prospect.
You don’t need to hire someone to find out how responsive he or she is. Shoot an email to a prospect asking for a time to chat, then see when (or if) you hear back.
#4. Look for someone who understands your business
The best developers aren’t merely code jockeys; they are consultants who work with you to further your business goals.
Let’s say you’re an office manager for a large doctor’s office, and you’re looking to hire someone to build a website for your practice. Who would you rather hire: a developer who has a number of medical websites in his portfolio and who understands HIPAA compliance, or a developer who has no particular specialty?
A phone call with your potential hire should give you this information. The potential hire should ask you questions about your business, not tell you things about his. If you’re not doing most of the talking, then something is wrong. Even the most experienced developers need to ask questions, since every project is different.
Your developer should prioritize results over style. If you don’t feel like your developer wants to take ownership of your problem and help you create a solution, then you should find someone else.
#5. Make sure your developer has good policies
Imagine going through the interview process and selecting someone, only to find out at the last minute that he or she wants payment in full, up front, for every project.
This might have been specified in that person’s payment policies, but if you didn’t bother to look at them, you’ve just wasted a lot of time.
Every good developer has policies, not just for receiving payments, but also for pricing, how work is scheduled, and how and when ownership of work transfers to you. In the absence of policies, a developer can create whatever rules he wants and surprise you with them at the last moment. Having well-defined policies makes it easier to do business.
Your potential developer should be happy to direct you to his policies and to explain them. If you sense reluctance or get a blank stare, it’s time to thank the person for his or her time and move on.
Conclusion
These are just a handful of my recommendations, borne from a few years in the business and some time on both sides of the “developer search.” If you have any recommendations of your own, or if you have stories to share about your searches, I’d be happy to hear them.
Post a Comment