Blog / 19 November 2026 / 6 min read
Questions to ask a web developer before hiring
14 questions to ask a web developer before hiring, grouped by experience, process, tech, ownership, cost and support, with good answers and red flags.
Joe
Director and Lead Software Engineer

The best questions to ask a web developer before hiring are about how they work, who owns what at the end, and what happens after launch, not just their portfolio. Below are 14 questions grouped by topic, with what a good answer sounds like and the red flags to listen for.
You don't need to be technical to use them. You're listening for clear, specific answers from someone who has done this many times before.
The short answer
Ask about relevant past work, who will actually do the work, how the project is run, what technology they'd use and why, who owns the domain, code and accounts, what's included in the price, and what support looks like after launch. A good developer answers plainly and puts the important parts in writing.
Experience questions
1. Can you show me work similar to what I need?
Good answer: A few relevant examples, with an explanation of the problem each one solved and their role in it. Our case studies are an example of the kind of detail worth looking for.
Red flag: A gallery of screenshots with no context, or sites that are no longer live.
2. Who will actually work on my project?
Good answer: Named people and their roles. If parts are subcontracted, they tell you up front.
Red flag: Vague answers, or a senior person who sells the project and then disappears.
3. Can I speak to a past client?
Good answer: Yes, with an introduction to someone relevant.
Red flag: Reluctance, or only anonymous quotes on a website.
Process questions
4. What does your process look like from start to launch?
Good answer: Clear phases (discovery, design, build, testing, launch), how long each takes, and when you'll be asked for input. Our guide on how long it takes to build a website explains what's typical.
Red flag: "We'll just get started and see how it goes."
5. What do you need from me, and when?
Good answer: A list: content, images, logins, feedback within agreed windows, one decision-maker.
Red flag: No mention of your responsibilities. Projects stall when nobody explains what the client needs to provide.
6. How will we communicate, and how often?
Good answer: A regular rhythm, such as a weekly update and a shared place to see progress and give feedback.
Red flag: No structure, or everything handled by ad hoc phone calls with nothing written down.
Technology questions
7. What would you build it with, and why?
Good answer: A recommendation tied to your needs: who will edit the site, how fast it needs to be, what it must connect to. They should mention alternatives and trade-offs.
Red flag: The same answer for every client regardless of need, or jargon with no explanation.
8. How will you handle speed, accessibility and SEO?
Good answer: Specifics, such as performance targets, testing with a keyboard and screen reader, proper headings and metadata, and redirects from old URLs.
Red flag: "We'll add SEO at the end" or "accessibility isn't needed for a site like yours".
9. How easy will it be for my team to update the site?
Good answer: An offer to show you the editing experience, with training included.
Red flag: Every small text change needs the developer.
Ownership questions
10. Who will own the domain, hosting, code and design files?
Good answer: You will. Accounts are set up in your business's name, and the contract assigns the intellectual property to you once paid. We explain why this matters in who owns my website.
Red flag: The developer registers the domain in their own name, or the contract is silent on ownership.
11. Can another developer take over if needed?
Good answer: Yes. The code is in a repository you can access, uses common tools, and is documented.
Red flag: A proprietary platform only they can work on.
Cost questions
12. What exactly is included in the price, and what isn't?
Good answer: A written scope listing pages, features, rounds of revisions, content entry, training, hosting and launch support. They explain how changes are priced. For context on typical budgets, see how much a website costs in the UK.
Red flag: A single number with no breakdown, or a price that seems far below everyone else's with no explanation.
13. What are the ongoing costs after launch?
Good answer: A clear list: hosting, domain renewals, CMS or platform fees, plugins or apps, and any maintenance plan.
Red flag: "It's basically free to run." There is almost always something to pay for.
Support questions
14. What happens if something breaks after launch?
Good answer: A warranty period for fixing their own bugs, then an optional support arrangement with clear response times and costs.
Red flag: No answer, or support that depends on the developer having a free afternoon.
Other red flags to watch for
- Pressure to sign quickly, or discounts that expire in days
- No written contract or scope
- Large upfront payments before any work, with no staged milestones
- Promises of guaranteed first-page Google rankings
- Criticising every previous developer without explaining what they'd do differently
How to compare the answers
Ask every developer you're considering the same questions, ideally in writing, so you can compare like for like. The cheapest quote isn't always the best value, and the most polished pitch isn't always the best team. Look for clear thinking, honesty about trade-offs, and a willingness to say "that's not something we'd recommend" when it's true.
It helps to send each developer the same written brief first, covering your goals, audience, must-have features and budget range, so the answers are based on the same information.
If you're interviewing developers now, we're happy to answer any of these questions for your project. Tell us what you're planning and we'll give you straight answers.