7 Critical Questions to Ask Before Hiring a Web Developer (2025)

You've found three developers. They all seem qualified. Their portfolios look good. Their rates are similar.

How do you choose?

Most business owners pick based on price or "gut feeling." Then 3 months later they're dealing with missed deadlines, poor communication, and a website that doesn't work on mobile.

After building 150+ websites and working with hundreds of clients, I can tell you: the interview questions matter more than the portfolio.

Here are the 7 questions that separate great developers from disasters—and more importantly, what the answers actually mean.

Before You Start: What NOT to Ask

Bad questions waste time and tell you nothing:

❌ "How long have you been coding?" (Years ≠ skill) ❌ "What's your favorite programming language?" (Who cares?) ❌ "Can you build X?" (Everyone says yes) ❌ "Do you guarantee the work?" (Meaningless without specifics)

Instead, ask questions that reveal:

• How they work
• How they handle problems
• How they communicate
• Whether they understand business (not just code)

Let's get into the actual questions.

Question #1: "Walk me through your development process from start to finish"

Why This Question Matters:

This reveals:

• Whether they have a process at all
• How organized they are
• What you can expect
• Red flags in their approach

🚩 Red Flag Answers:

"I'll just start coding and we'll figure it out as we go" → No plan = missed requirements, scope creep, blown timeline

"I build the whole thing then show you when it's done" → You'll have zero input, likely won't get what you want

"I follow agile methodology with sprints and standups" → Buzzwords without specifics = doesn't actually have a process

✅ Green Flag Answers:

"Here's my typical process:

1. Discovery call to understand your goals and requirements
2. Written proposal with clear scope, timeline, and milestones
3. Design mockups for you to approve before I code anything
4. Development in phases with regular check-ins
5. Testing across devices and browsers
6. Training on how to update content
7. Launch and post-launch support"

→ Clear, structured, involves you at key points

What to Listen For:

✅ Mentions gathering requirements BEFORE coding ✅ Includes design/mockup approval ✅ Shows you work-in-progress (not waiting until done) ✅ Has testing phase ✅ Provides training ✅ Offers post-launch support

Follow-up: "At what points will I see progress and give feedback?"

Good answer: "You'll see mockups before any coding, a staging site halfway through, and reviews at each milestone."

Question #2: "What happens if I'm not happy with the result?"

Why This Question Matters:

• Tests their confidence
• Reveals fairness of terms
• Shows how they handle conflict
• Separates pros from amateurs

🚩 Red Flag Answers:

"All sales final, no refunds" → They don't stand behind their work

"You sign off at each stage so you can't complain later" → Technically true but adversarial relationship

"We'll keep revising until you're happy" → Sounds good but no boundaries = project never ends

"You can always file a dispute on the platform" → They're expecting problems

✅ Green Flag Answers:

"I offer [3-5] rounds of revisions within scope. If I miss requirements we agreed on, I'll fix it at no cost. If you're not satisfied after good-faith effort, we can discuss partial refund or bringing in another developer to review."

→ Clear boundaries + fairness + problem-solving approach

"I have a 100% money-back guarantee if I don't deliver what we agreed on in the proposal."

→ Extreme confidence in their work

What to Listen For:

✅ Specific revision policy (not "unlimited" or "none") ✅ Willing to fix their mistakes without charge ✅ Some kind of satisfaction guarantee ✅ Collaborative problem-solving tone (not defensive)

Follow-up: "Has a client ever been unhappy? What happened?"

Good answer: Honest story about a challenge and how they resolved it professionally.

Question #3: "Can you show me similar projects you've built?"

Why This Question Matters:

• Tests if they've done THIS type of work before
• Reveals quality standards
• Shows if they understand your industry

🚩 Red Flag Answers:

"I've built all kinds of websites, I can do anything" → Jack of all trades, master of none

Shows you 5-year-old websites that no longer exist → Clients didn't maintain relationship (why?)

"I can't show you my best work due to NDAs" → Maybe true, but convenient excuse

Portfolio is all flashy animations but sites load slowly → Pretty over functional

✅ Green Flag Answers:

"Here are 3 [your industry] websites I've built. This one solved [specific problem similar to yours]. Let me show you how [specific feature] works."

→ Relevant experience + understands your problem

Shows you live websites from the past 2 years → Recent work, sites are still maintained

Explains decisions: "This client needed fast load times for SEO, so I used X approach"** → Thinks strategically, not just aesthetically

What to Listen For:

✅ Portfolio includes projects like yours ✅ Can explain WHY they made certain choices ✅ Sites are still live and well-maintained ✅ Focus on results, not just "looks nice"

Follow-up: "What were the business goals for this project? Were they achieved?"

Good answer: Actually knows the business outcomes, not just "client was happy."

Question #4: "What's included in your price, and what costs extra?"

Why This Question Matters:

• Prevents surprise costs
• Tests honesty
• Reveals if they understand scope
• Shows professional vs amateur pricing

🚩 Red Flag Answers:

"Everything is included" → Too vague, will lead to scope disputes

Unrealistic low price (£500 for e-commerce site) → Either low quality or surprise charges coming

Can't give any estimate without full spec → True for complex projects, but should give range

Long list of items "not included" → Hidden costs add up to more than custom quote elsewhere

✅ Green Flag Answers:

"My £3,500 quote includes:

• Up to 8 pages
• Contact forms
• Mobile responsive
• Basic SEO
• Training
• 30 days of minor revisions
• Hosting setup (you pay hosting directly)

NOT included (costs extra):

• Content writing (I can recommend someone)
• Logo design (can add for £400)
• Additional pages beyond 8 (£200 each)
• E-commerce (separate quote)
• Custom integrations (quote per integration)"

→ Crystal clear what's in and out

What to Listen For:

✅ Specific deliverables listed ✅ Clear exclusions ✅ No surprises ✅ Optional add-ons with prices ✅ Separate things YOU pay directly (hosting, domain)

Follow-up: "What has historically caused projects to go over budget?"

Good answer: "Usually clients adding pages or features midway. That's why I recommend finalizing scope before starting."

Question #5: "What happens if you get sick, have an emergency, or can't finish?"

Why This Question Matters:

• Tests their professionalism
• Reveals risk management
• Shows if they're freelancer or have backup
• Indicates financial stability

🚩 Red Flag Answers:

"That won't happen" → Naive or dishonest. Life happens.

"The platform will refund you" → They're not taking responsibility

"You'll have to wait until I'm back" → No backup plan

Gets defensive: "Why are you asking that?"** → Unprofessional

✅ Green Flag Answers:

"I have a network of developer colleagues who can step in for emergencies. For a short absence (few days), I'd let you know immediately and adjust timeline. For longer issues, I'd either finish remotely when able or help you transition to another developer with your code and documentation."

→ Has thought this through, has backup

"I've been doing this 6 years full-time and never missed a deadline, but if something catastrophic happened, I'd refund any unearned portion and provide all work completed so far with documentation for your next developer."

→ Professional, fair, realistic

What to Listen For:

✅ Has actually considered this scenario ✅ Has backup plan ✅ Communicates proactively ✅ Fair refund policy ✅ Provides code/documentation if they can't continue

Follow-up: "If I need someone else to update the site later, how easy is that?"

Good answer: "The code is clean and documented. Any developer familiar with [technology] can work on it. I don't use proprietary systems or lock you in."

Question #6: "How do you handle communication and updates?"

Why This Question Matters:

• Sets expectations
• Reveals if they'll ghost you
• Tests if they understand client service
• Shows timezone/availability compatibility

🚩 Red Flag Answers:

"I'll update you when there's something to show" → You'll be in the dark for weeks

"I'm online 24/7, message me anytime" → Unrealistic promise, likely burns out

Takes 3 days to respond during initial conversation → Will only get worse

"I don't do calls, email only" → Might work for some, red flag for complex projects

✅ Green Flag Answers:

"I send progress updates every Friday via email. I'm available for a quick call once a week if needed. I typically respond to messages within 2-4 hours during my workday ([timezone], 9am-6pm). For urgent issues, you can WhatsApp me and I'll respond within an hour."

→ Clear expectations, reasonable availability

"We'll have a kickoff call, design review call, and pre-launch call. Between those, I send weekly written updates via email or project management tool. Questions via email usually answered same day."

→ Structured communication, very responsive

What to Listen For:

✅ Specific response time expectation ✅ Regular update schedule ✅ Multiple communication channels ✅ Availability during your business hours (or overlap) ✅ Emergency contact method

Follow-up: "What if I need urgent changes after launch?"

Good answer: "Minor text changes you can handle with training. Urgent technical fixes I can do within 24 hours. Major new features we'd quote separately."

Question #7: "What do I need to provide, and when?"

Why This Question Matters:

• Reveals if they understand project management
• Shows what's YOUR responsibility
• Tests if they'll blame delays on you
• Identifies potential bottlenecks early

🚩 Red Flag Answers:

"Just tell me what you want and I'll build it" → No structured requirements gathering

"I need everything before I start" → Rigid, doesn't work iteratively

"Just give me content whenever" → Recipe for delays

Asks for full payment upfront → All risk on you

✅ Green Flag Answers:

"Before I start:

• Logo (if you have one)
• Brand colors and style preferences
• List of page names and rough description
• Examples of sites you like

During development:

• Feedback on design mockups (within 3 days)
• Page content for each section (I'll provide templates)
• Product photos or descriptions (if e-commerce)
• Your domain/hosting login (at launch)

I'll give you deadlines for each item so we stay on track."

→ Clear, organized, realistic timeline

What to Listen For:

✅ Provides content templates or examples ✅ Gives you specific deadlines ✅ Breaks deliverables into phases ✅ Accommodates "content in progress" ✅ Offers to help find resources (photographers, copywriters)

Follow-up: "What if I don't have content ready?"

Good answer: "We can use placeholder content to keep development moving, then swap in real content before launch. Or I can connect you with a copywriter."

Bonus Red Flags That Disqualify Immediately

Some answers should end the conversation:

🚨 Can't show ANY previous work → Might be new (which is okay if prices reflect it) or lying about experience

🚨 Gives drastically different timeline than others (10 websites for £200 in 2 days) → Either scam or completely unrealistic

🚨 Asks for 100% payment upfront → All risk on you, no incentive for them to finish

🚨 Defensive or rude when you ask questions → This is their SALES behavior. Imagine working with them.

🚨 Can't explain technical choices in plain English → Doesn't understand it or can't communicate

🚨 Too eager to start before understanding requirements → Will build wrong thing

🚨 Badmouths previous clients → Will badmouth you next

🚨 Makes promises that sound too good to be true → They are.

Bonus Green Flags That Indicate Excellence

Some answers make developer stand out:

⭐ Asks YOU lots of questions → Trying to understand your business, not just build something

⭐ Gives honest advice even if it costs them the job → "You don't need custom, a template would work fine for your needs"

⭐ Suggests starting small → "Let's build MVP first, add features later based on user feedback"

⭐ Talks about business outcomes, not just features → "This will help you get more leads" vs "This will have 12 pages"

⭐ Shares what can go wrong and how they'll prevent it → Experienced and honest

⭐ Offers a trial project or paid discovery phase → Test relationship before big commitment

⭐ Provides references or testimonials without asking → Confident in their work

How to Actually Conduct the Interview

1. Start with a Written Question (Filter)

Before scheduling calls, send these 3 questions via email:

1. "Can you share 2-3 websites similar to what I need?"
2. "What's your availability over the next 4 weeks?"
3. "What's your typical project process?"

Filter out candidates who:

• Don't respond within 48 hours
• Give one-sentence answers
• Don't actually answer the question

Schedule calls with candidates who:

• Respond thoughtfully
• Show relevant work
• Sound professional

2. Schedule 20-30 Minute Call

Ask the 7 questions above. Take notes.

Rate each answer 1-5:

• 5 = Green flag answer
• 3 = Okay answer
• 1 = Red flag answer

Anyone with a "1" answer: skip them

Highest average score wins (assuming price is comparable)

3. Check References

If seriously considering them, ask:

"Can I speak to 1-2 previous clients?"

Ask those clients:

• "Was project delivered on time?"
• "Would you hire them again?"
• "Any surprises or issues?"

Sample Scorecard

Question	Developer A	Developer B	Developer C
Process	5 (detailed)	3 (vague)	4 (good structure)
Unhappy clause	5 (money-back)	2 (no refunds)	4 (fair terms)
Portfolio	4 (relevant)	5 (perfect match)	3 (some relevant)
Pricing clarity	5 (crystal clear)	3 (many exclusions)	4 (mostly clear)
Emergency plan	4 (has backup)	2 (no plan)	5 (very thorough)
Communication	5 (very responsive)	3 (slow response)	4 (good)
Your deliverables	4 (organized)	3 (unclear)	5 (super clear)
TOTAL	32/35	21/35	29/35

Result: Developer A wins (even if slightly more expensive)

What About Price?

"Okay, but shouldn't I factor in cost?"

Yes, but smartly:

If prices are within 20% of each other:

Choose based on answers above, not price.

Example:

• Developer A: £3,000, score 32/35
• Developer B: £2,600, score 21/35

Choose Developer A. £400 difference is worth the reduced risk.

If one is significantly cheaper (40%+ less):

Ask why:

Maybe they're:

• New (less expensive, higher risk)
• Based in lower-cost country (good deal if skilled)
• Misunderstanding scope (will request more later)
• Too good to be true (it is)

If one is significantly more expensive (2x+):

Ask what extra value you're getting:

Maybe they:

• Include things others charge extra for
• Are extremely experienced/specialized
• Include ongoing support
• Have premium service

Is the extra value worth it for YOUR project?

My Answers to These Questions

Since I wrote this guide, let me answer them about my own services:

Process: Discovery call → Written proposal → Design mockup → Development in phases → Testing → Training → Launch + 30 days support

If you're unhappy: 100% money-back guarantee if I don't deliver what we agreed. Up to 5 revision rounds within scope.

Similar projects: View portfolio with 150+ completed websites, filterable by industry

Pricing: Clear packages with included features listed. No hidden costs.

Emergency plan: 6 years full-time freelancing, never missed a deadline. Code is well-documented. Network of colleagues for true emergencies.

Communication: 2-hour avg response time during business hours (can work UK/EU timezone). Weekly progress updates. Kickoff, design review, and pre-launch calls.

What you provide: I'll send you templates for content. Flexible on timing—can use placeholders. Payment in milestones (30% start, 40% midway, 30% completion).

Get your free quote →

Key Takeaways

These 7 Questions Reveal Everything:

1. Process question = are they organized?
2. Unhappy clause = do they stand behind their work?
3. Portfolio = can they actually do this?
4. Pricing clarity = will there be surprise costs?
5. Emergency plan = what if things go wrong?
6. Communication = will they ghost me?
7. Your deliverables = what's my responsibility?

Choose Based On:

• ✅ Answers to these questions
• ✅ Professionalism in initial contact
• ✅ Relevant portfolio work
• ✅ Clear communication
• ❌ NOT just lowest price
• ❌ NOT just fanciest portfolio
• ❌ NOT just who responds first

Remember:

A £500 website that doesn't work wastes more money than a £3,000 website that generates leads.

The right questions help you find developers who deliver results, not just code.

Ready to Skip the Interview Process?

I built this guide so you know what to look for. But if you want to skip straight to working with someone who gives all the green-flag answers...

Here's What You Get Working With Me:

✅ Clear fixed pricing – No surprises, no hidden costs ✅ 100% money-back guarantee – If I don't deliver as promised ✅ 2-hour response time – Questions answered fast ✅ 150+ completed projects – Proven track record ✅ Weekly updates – Always know where your project stands ✅ Full code ownership – No lock-in, you own everything ✅ 30 days free support – Minor updates after launch

Choose Your Package:

Professional Business Website – £420 Perfect for: Service businesses, consultants, small businesses 5-8 pages, mobile responsive, SEO optimized, contact forms

Mini Site Package – £1,500 Perfect for: Startups, new businesses, simple needs 3 custom pages, mobile optimization, basic SEO, 2 weeks support

Custom Web Application – From £1,500 Perfect for: Unique business needs, SaaS, complex features Custom features, integrations, scalable architecture

E-Commerce Store – £4,200 Perfect for: Online shops, product businesses Full e-commerce functionality, payment processing, inventory management

View all services →

How It Works:

1. Contact me with your project details
2. Free consultation call (20-30 min) to discuss your needs
3. Detailed proposal with timeline and pricing
4. Design mockup for your approval before coding
5. Regular updates as I build
6. Launch + training + 30 days support

Average time from first contact to launch: 3-4 weeks

Get your free quote →

---

Additional Resources:

• First-Time Hiring a Freelancer Guide – Complete hiring process walkthrough
• How Much Does a Website Cost? – Pricing breakdown and budgeting guide
• Agency vs Freelancer Comparison – When each makes sense

Download the free checklist: 7 Questions Hiring Checklist (PDF) – Print this and bring it to developer interviews.

---

About the Author: I'm a senior web developer with 6+ years of experience and 150+ completed projects. I wrote this guide after seeing too many businesses make expensive hiring mistakes. My goal is to help you hire confidently—whether you choose to work with me or someone else, these questions will help you make the right choice.