The best questions to ask web developer candidates are about process, ownership, security, communication and life after launch, not about technology buzzwords. Twelve well-chosen questions will tell you whether a freelancer or agency can deliver your project and leave you in control of it. Use the list below, and compare answers side by side.
Questions to ask web developer candidates: before you start
Good answers depend on a good brief. Before you contact anyone, write one page covering what the website must achieve, who uses it, the pages or features you know you need, any systems it must connect to, your deadline and your rough budget range. You do not need technical language; you need clarity.
It also helps to decide what you will not compromise on. For some businesses that is ownership of the code, for others it is a fixed price or fast turnaround. Knowing this lets you read answers against your priorities rather than being swayed by the best presentation. For a wider view of options, the guide on WordPress versus a custom website helps you understand what kind of build you are asking for.
Scope and process questions
1. How will you turn my brief into a written scope?
You want to hear about a discovery step: questions, a list of pages and features, and a document you approve before building. Vague answers such as we will figure it out as we go are a warning sign for fixed-price work.
2. What does your process look like from kickoff to launch?
Look for stages: discovery, design, build, content, testing, launch. Ask when you will see working pages and how many rounds of feedback are included.
3. What happens when my requirements change?
Change is normal. A good developer has a simple method: describe the change, estimate its effect, you approve it, then it is done. Ask how extra work is priced.
4. Who will actually work on my project?
With an agency, find out whether the people in the sales meeting are the people who build, and whether any work is subcontracted or sent overseas. Neither is automatically bad, but you should know.
Ownership and access questions
5. Who owns the website, code and design when it is finished?
Do not assume. The answer should be in the contract, and for important details such as ownership transfer you should get legal advice from a qualified adviser. Ask also about third-party themes, plugins and fonts, which you often licence rather than own.
6. Will the domain, hosting and accounts be in my name?
You should be the registered owner of your domain, with administrator access to hosting, analytics and any other service. A developer who keeps these in their own name has leverage over you. If something goes wrong, you want to be able to move on.
7. Will I get the source code and documentation?
Ask for access to the code repository and a short document explaining how to run, update and deploy the site. The article on documentation and handover describes what good looks like.
Security and maintenance questions
8. How do you handle security?
You are not looking for jargon, you are looking for habits: updates, strong authentication for admin users, safe handling of forms and payments, backups, and a plan if something goes wrong. If your site collects personal data, ask how it is stored, and check current privacy requirements with the official regulator or an adviser.
9. What happens after launch?
Ask who fixes bugs found in the first weeks, how long defects are corrected free of charge, and what ongoing care costs and covers. Our overview of what a website maintenance plan should include gives you a checklist to measure their answer against.
Communication and reporting
10. How will we communicate, and how often?
Look for a named contact, a regular update rhythm, a shared place for feedback and a stated response time. Ask how they handle disagreements and delays. Silence during a project is a better predictor of trouble than any technical choice.
11. How will I see progress?
The best answer is a staging site you can visit while the project is underway, with demos at agreed points, rather than a reveal at the end. Ask what you will need to supply and when, such as text, images and decisions, because delays on your side affect the timeline too.
References and evidence
12. Can I see relevant work and speak to someone who has hired you?
Ask for examples similar to your project in size and kind, and ask what the developer's role was in each. A reference who can describe how the project went matters more than a polished screenshot. When you assess portfolio work, look beyond appearance:
- Open the live sites on a phone and check speed and behaviour.
- Test forms, navigation and any interactive features.
- Ask what was hard about the project and how it was solved.
- Check whether the sites are still maintained and working.
You can see how we present work on our portfolio page, and the same scrutiny applies to anyone you consider.
How to compare answers
Put the quotes and answers side by side in a simple table. Score each candidate from one to five on the criteria that matter to you.
| Criterion | What good looks like | Warning sign |
|---|---|---|
| Scope | Written, approved before work | Vague, we will see |
| Ownership | You hold domain, hosting, code | Developer keeps accounts |
| Quote | Itemised, with exclusions listed | One lump sum, no detail |
| Communication | Named contact, regular updates | Slow or evasive replies |
| After launch | Defined support and fix period | Nothing mentioned |
A quote should itemise what is included and excluded, the payment schedule, the number of revision rounds, what you must supply, and what happens after launch. The cheapest quote often leaves things out, so compare like with like.
Putting it together
Ask every candidate the same questions, in writing if you can, and give weight to clear and honest answers, including admissions of what they will not do. Shortlist two or three, then do a small paid discovery or scoping step before committing to the full project. If you want to see how a scoping conversation might go, read about our work with Australian businesses or send a brief through the contact page.
Frequently asked questions
Should I ask for references?
Yes. Ask for one or two clients with projects similar to yours, and ask them how communication, deadlines and problems were handled. Be aware that references are chosen by the developer, so also test live work yourself and ask what the developer's actual role was on each project.
What should a quote include?
A useful quote lists the scope in plain terms, what is excluded, the payment schedule, how many revision rounds are included, what you must supply, the timeline assumptions, ownership terms and what happens after launch. If a quote is a single line with a total, ask for more detail.
How do I assess portfolio work?
Visit the live sites on your phone and a computer, check speed, navigation and forms, and ask what was difficult about each project. Look for work similar in size and kind to yours, and confirm what the developer personally did, since agencies often show team output.