A short list of the right questions, asked before you sign anything, will tell you more about a web developer than hours of browsing portfolios. Here's what actually matters, grouped by what each question is trying to uncover.
Questions about experience and fit
- "Have you built something similar to what I need before? Can I see it live?"
- "What technology would you use for this project, and why that choice specifically?"
- "What's the biggest challenge you'd expect on a project like mine?"
Questions about process and communication
- "How often will you update me, and through what channel?"
- "What do you need from me to keep the project on schedule?"
- "How do you handle scope changes once the project has started?"
Questions about ownership and cost
- "Who owns the final code, design files, and any third-party licenses?"
- "Is your quote fixed, or could it change once work begins? Under what conditions?"
- "What support is included after launch, and what's billed separately?"
What to listen for in the answers
Specific, confident answers are a good sign. Vague reassurance ("don't worry, we'll figure it out") on scope, ownership, or pricing questions is worth pushing back on before you commit — those are exactly the areas that cause disputes later.
Putting it together
A short, direct set of questions upfront saves far more time than it costs, because it surfaces mismatches before money changes hands. If you're preparing to hire for your own project, feel free to get in touch and I'm happy to talk through what to ask.