Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Buyer guide

How do I check a freelance developer is good if I am not technical?

In short

You do not need to read code to vet a developer. Ask to see products they built and still run, ask them to explain a past decision in plain words, check that they ask good questions about your business, and start with a small paid job. Ask what security practices they follow and whether they would put them in writing.

  • Written for founders and business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Who is this guide for?

Non-technical founders and managers who have to choose a freelance developer and cannot judge the code themselves.

Judge the explanation, not the jargon

A good developer can explain a technical choice in words you understand, including what it costs you and what could go wrong. If every answer is a stack of terms, or every answer is yes, take note.

Ask: what would you do differently on my project if the budget were smaller, and what would you give up? A thoughtful answer has a trade-off in it.

Look at what they have built and still run

Ask for live products, apps in the stores or websites you can open, and for permission to speak to someone they built for. A product that is still running shows that the work lasted beyond the handover.

Open what they show you on your own phone. Does it load, does it work, does it feel finished? You are a user, and your judgement as a user counts.

Check how they start

A careful developer asks about your business before they quote: who the users are, what happens when something breaks, what you already have. A quote given immediately with no questions is a guess.

Ask how they will keep you informed, what you will see every week or two and how they handle changes to the plan.

Ask about security

You can ask about secure development without being technical. NIST publishes a Secure Software Development Framework, a set of practices to reduce vulnerabilities in released software, grouped around preparing the organisation, protecting the software, producing well-secured software and responding to vulnerabilities.

A fair question is: how do you handle updates and security problems after launch, and what will you do if one is found? The OWASP Application Security Verification Standard is another reference: it is a list of security requirements that you can name in an agreement.

Red flags

Be careful with anyone who asks for all the money before any work, who will not let your accounts and repository be in your name, who will not put scope in writing or who criticises every previous developer without evidence.

None of these proves a problem alone. Together they are a pattern.

Test with a small paid job

A short, paid first task, such as a written review or one small feature, tells you more than any interview: how they communicate, how they estimate, whether they deliver on time and how they react to feedback.

If you have a technical friend, ask them to look over the result. An hour of an independent expert's time is cheap next to hiring the wrong person.

How do the options compare?

CheckWhat good looks likeWhat worries me
ExplanationPlain words with trade-offsJargon or yes to everything
Past workLive products you can use and a referenceOnly screenshots
First conversationQuestions about your businessAn instant quote
SecurityA clear answer about updates and problemsWaving the question away
OwnershipAccounts and code in your nameTheir accounts hold everything
Small first jobDelivered clearly and on timeExcuses and silence

What should I check before I sign?

  • You have used something they built on your own device.
  • You have spoken to someone they worked for, or seen a live result.
  • They asked about your business before quoting.
  • They explained a trade-off in plain words.
  • You asked how they handle security and updates.
  • Accounts and code will be in your name.
  • The first job is small, paid and clearly defined.

How pricing works

I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.

What else do people ask?

Do I need a technical person to help me choose?

It helps. Even an hour of an independent expert reviewing the shortlist and a first deliverable can save a lot.

Are reviews and ratings enough?

They are a start. Combine them with a live product, a reference and a small paid trial.

Should I ask for a coding test?

For a business owner a paid trial job is more useful, and it respects the developer's time.

What if they will not show past work?

Sometimes work is under confidentiality. Then ask for a reference, or a description of what they built and a conversation with the client.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want a written quote to compare?

A discovery call within 48 hours, then a scope and a price in writing.