Choosing a Software Developer, From the Person You Would Hire

I'm usually the developer on the other side of this decision, which makes this a slightly odd thing for me to write. I've watched projects go well and projects go sideways, though, and what separates them is seldom what people expect.

The Tech Stack Matters Less Than You Think

Clients often lead with technology, asking whether I know a particular framework. It's a fair question, but the framework belongs near the bottom of the list. A competent developer can pick up a new tool in a week or two. What is hard to find, and impossible to fake for long, is someone who listens properly and tells you plainly when your idea has a hole in it. Ideally they still care once the exciting part is over.

Look Past the Screenshots

A portfolio matters, but don't stop at the pictures. Anyone can show off a nice landing page. Ask about one project in particular, what was hard about it and what they got wrong the first time. A developer who can talk honestly about a mess they cleaned up tells you far more than a wall of polished thumbnails.

Watch How They Communicate

The way someone answers your first message is a preview of the whole project. Notice whether they ask good questions or simply agree to everything. If getting a straight answer is hard work now, while they're trying to win you over, it won't get easier once money has changed hands.

Be Honest About Budget

Tell the developer your real budget and your real timeline. I understand the instinct to hold them back in the hope of a better price. In my experience it mostly wastes everyone's time, and you end up with a proposal for a project that doesn't exist. When a developer is honest in return and tells you something will take longer than you'd hoped, take it as a good sign.

Beware the Yes-Man

A developer who agrees with everything you say probably isn't thinking very hard about your project. You want someone who will push back now and then, perhaps to say that a feature you love isn't worth what it costs, or that there's a simpler route to what you need. Boxing has a version of this. A cornerman who only says nice things between rounds is of no use to anybody in round eight.

Ask What Happens After Launch

Going live is where real people start using the thing and showing you everything you missed. Ask who will be around for that part. A developer who disappears once the invoice is paid leaves you alone with the problems that are hardest to solve. The good ones expect to stay and smooth the rough edges.

If I had to boil all of this down, I'd choose the person over the technology every time, since a good developer will learn whatever framework the project needs.