DevCru wordt geladen…
DevCru — Web & App Development Agency
guide
4 min read

How to choose a freelance web developer in the Netherlands

Practical questions, red flags and what to put in the agreement when you hire a freelance web developer. Checklist, interview questions and guidance on performance, security and maintenance.

Share:

A good freelance web developer saves time and prevents costly mistakes. But how do you spot someone who combines engineering, UX and maintainability well? This guide gives practical interview questions, red flags, and the items to put in your contract.

You’ll get a checklist, suggested contract clauses and simple tests you can ask for. Also consider performance (Core Web Vitals), responsive behavior and security early on — fixing those later is often more expensive.

We link to pragmatic sources and show indicative rates and timelines — always noting these vary per project.

Start with the objective

Before you call candidates: write a short brief. A brochure site, a small webshop or a custom web app require different skills.

  • Functional goal: lead site, e-commerce, internal tool.
  • Expected traffic and peaks: 1,000 uniques/month vs. 100,000 — affects hosting and caching.
  • Integrations: CRM, payment providers, headless CMS.

A freelancer with proven experience in similar projects is usually faster and more predictable.

Questions to ask (interview)

  • What exact role will you take? (front-end, back-end, fullstack, devops)
  • Which tech stack do you propose and why? (e.g., React, Next.js, WordPress)
  • Can you sketch a simple architecture in 10–15 minutes?
  • How do you measure performance? Name metrics like LCP and CLS.
  • How do you handle security and which risks do you see for this project?
  • How do you ensure accessibility and responsive behavior?
  • How do you handle backups and deployments?
  • What’s your weekly availability and response time for bugs?
  • What deliverables will you provide (README, deployment steps, env vars)?

Ask for concrete examples. If a candidate can’t show relevant work, that’s a red flag.

Red flags: what to watch for

  • No portfolio or weak examples.
  • Vague answers without concrete metrics (load time, uptime, tests).
  • No mention of security or no reference to known risks such as the OWASP Top 10: https://owasp.org/www-project-top-ten/.
  • Overcommitment to a single tool without justification.
  • Unrealistic delivery times or very low prices without defined scope.
  • Refusal to sign written agreements.

A developer who explains how they test performance and security is more valuable than one who only lists features.

Technical checks you can request

  • A short take-home task: build a responsive landing page with a form and basic validation.
  • Ask which Core Web Vitals they monitor and how: https://web.dev/articles/vitals.
  • Ask how they test responsive design (tools, device testing), see best practices on MDN: https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Responsive_Design.

A compact test of a few hours gives insights faster than long interviews.

What to record in the agreement (contract and scope)

  • Scope: exactly what will be delivered (pages, flows, APIs).
  • Acceptance criteria: functional and non-functional (e.g., target LCP, CLS if relevant).
  • Delivery dates and milestones.
  • Revision rounds: how many are included and what counts as out-of-scope.
  • Support and maintenance: hours per month, hourly rate for extra work.
  • Ownership and licenses: who owns code and assets.
  • Backups and rollback procedures.
  • Security responsibilities: who applies patches, monitors, and handles incidents.
  • Payment terms and termination.
  • NDA or privacy clause if personal data is involved (note GDPR considerations: https://www.autoriteitpersoonsgegevens.nl/themas/basis-avg/avg-algemeen).

Indicative rates (hourly) — for reference only, projects vary:

  • Junior: €35–€60/hour.
  • Medior: €60–€95/hour.
  • Senior: €95–€150+/hour.

A small site (5–10 pages) often takes 1–3 weeks. A webshop or custom web app can take several months.

Checklist before signing

  • You’ve seen relevant work samples.
  • Tech stack and hosting are clear.
  • Performance and security requirements are specified.
  • Price, payment and milestones are written down.
  • Post-launch support is agreed.
  • Ownership and backups are arranged.

Comparison table: what to expect

Independent delivery

Junior
Low
Medior
Medium
Senior
High

Architecture

Junior
Basic
Medior
Good
Senior
Strong

Tests & CI

Junior
Limited
Medior
Standard
Senior
Robust

Security awareness

Junior
Basic
Medior
Good
Senior
Proactive (incl. OWASP)

Communication

Junior
Varies
Medior
Reliable
Senior
Strategic

Maintenance and scaling

Plan for monitoring and updates from the start. Performance and security are ongoing efforts. Schedule a technical review after 1–3 months and budget to pay down technical debt.

If you want a technical assessment or second opinion, DevCru is a senior-led bureau that also does audits and ongoing support. Read about us on the about page or get in touch via contact.

For a short quote or practical advice, request a quote.

Sources

Every figure and guideline in this article can be checked in the sources below.

Got a project in mind?

Tell us briefly what you want to build. You get an honest read on scope, price and timeline within one business day.

Request a quote

Related services

Continue on the page that matches this topic.

Keep reading

Other articles that pair well with this one.