Choosing a software developer, from the person you would hire

I am usually the developer on the other side of this decision, which makes this a slightly odd thing for me to write. But I have watched plenty of projects go well and plenty go sideways, and most of the advice that actually matters is not what people expect.

The tech stack is the least of your worries

Clients often lead with technology. Do you know this framework, can you build in that one. Fair questions, but honestly the framework is near the bottom of the list. A competent developer can pick up a new tool in a week. What is genuinely hard to find, and impossible to fake for long, is someone who listens properly, tells you the truth when your idea has a hole in it, and still cares about the project after the fun part is over.

Hire for judgment and character. The tools sort themselves out.

Look at real work, then look past the screenshots

A portfolio matters, but do not stop at the pretty pictures. Anyone can show a nice landing page. Ask about one project in particular. What was hard about it. What did they decide, and what did they get 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 before you pay them

The way someone answers your first message is a preview of the whole project. Are they clear. Do they ask good questions, or just say yes to everything. Do they reply like a human or hide behind jargon. If getting a straight answer feels like work now, while they are trying to win you over, it only gets harder once the money has changed hands.

Be honest about budget, and reward honesty back

Tell a developer your real budget and your real timeline. I know the instinct is to hold that back to get a better price, but it usually just wastes everyone's time and produces a proposal built for a project that does not exist. And when a developer is honest with you in return, when they tell you something will take longer than you hoped or is not worth building yet, take that as a good sign. That is the person you want.

Be suspicious of the yes-man

A developer who agrees with every single thing you say is not being agreeable. They are being careless, or they have already checked out. You want someone who will occasionally push back, who will tell you that a feature you are excited about is not worth the cost, or that there is a simpler way to get what you actually need. That friction is not difficulty. It is someone thinking about your project instead of just taking the order.

Ask what happens after launch

Going live is not the finish line. It is where real people start using the thing and showing you everything you missed. Ask who is around for that part. A developer who disappears the moment the invoice clears leaves you alone with exactly the problems that are hardest to solve. The good ones expect to stay and fix the rough edges.

The short version

Pick someone who listens, tells you the truth, builds things that hold up, and sticks around. The rest, the frameworks and the buzzwords, is noise. Get the human right and the technology tends to follow.