How to hire a software developer

Freelancer vs agency vs in-house developer

• Freelancer: usually the lowest cost and quick to start. Best for a well-defined job with someone on your side who can review the work. The risk is that one person covers everything, and if they get busy or move on, the project stalls.
• Agency or development company: a team that covers design, development, testing and project management, with someone accountable for delivery. Costs more per hour than most freelancers, but you are not managing individuals. Best when you have no technical staff.
• In-house employee: the most control and the deepest knowledge of your business over time. Also the highest fixed cost once you add salary, benefits, recruiting and tools, and one hire rarely covers every skill a project needs. Best when software is central to the business and there is steady full-time work.
• Staff augmentation: developers supplied by an agency who join your team. Useful when you already have a technical lead and need extra hands.

How to hire a software developer, step by step

1. Write a one-page briefDescribe the problem, who will use the software, the must-have features, your budget range and your timing.
2. Pick the type of hireChoose freelancer, agency or in-house based on the size of the work and whether anyone can manage a developer directly.
3. Build a shortlistAsk your network first, then look at freelance marketplaces, agency directories, local tech groups and job boards.
4. Review real workAsk to see live software they built, not just screenshots, and ask what their part in it was.
5. Talk to referencesSpeak to two or three past clients, ideally ones whose project is still running.
6. Run a small paid testGive the top one or two candidates a short, paid piece of real work and judge communication as much as code.
7. Put it in writingAgree scope, price, ownership, support and how either side can end the arrangement before the main work starts.

Interview questions to ask

You do not need to be technical to learn a lot from these. Listen for clear, specific answers and honest trade-offs.

• Walk me through a project like mine that you built. What went wrong, and how did you handle it?
• What would you need from me before you could give a realistic estimate?
• How will you show me progress, and how often?
• What happens when I ask for a change halfway through?
• How do you test your work before I see it?
• Where will the code and the hosting live, and whose accounts will they be in?
• Who else will work on this, and what happens if you are sick or leave?
• What happens after launch? Who fixes bugs and how much does it cost?
• What would you not recommend building, and why?

Red flags when hiring a developer

• A firm price or timeline before they understand what you need.
• No questions about your business, only about features.
• Pressure to pay most of the money up front.
• Reluctance to put the code in an account you own.
• No live examples or references they are willing to share.
• Vague answers about who will actually do the work.
• Promises that sound too good, such as a complex app in a couple of weeks for very little money.
• Slow or unclear communication during the sales process. It rarely improves after you sign.

What to put in writing

Whatever kind of developer you hire, agree on these points in a written contract: what is in and out of scope, how changes are handled and priced, the payment schedule tied to milestones or time worked, who owns the code, designs and data, where the code is stored and who has access, confidentiality, what support looks like after launch, and how either side can end the agreement and hand over the work. This is general guidance, not legal advice, so have a lawyer review the contract before you sign.

When not to hire anyone yet

Sometimes the right move is to wait. If you cannot yet describe who the software is for and what problem it solves, spend a few weeks talking to the people who would use it. If an off-the-shelf tool might do the job, try it first. And if you are hiring to build a product you hope to raise money on, consider whether you are really looking for a technical cofounder rather than a contractor.