A website developer builds and maintains the technical side of a site: the code, the server it runs on, the systems it connects to, and the reasons it stops working at 2am. That is the short definition. The useful answer is longer, because “website developer” gets used for three different jobs, and knowing which one you need changes what you should pay.
The three jobs people mean
| Title | Builds | Typical work |
|---|---|---|
| Web designer | How it looks | Layouts, type, colour, brand, prototypes in Figma |
| Website developer | How it works | Themes, templates, code, integrations, performance |
| Full-stack developer | Both ends | Front-end plus server, APIs, database, deployment |
In a small studio one person does all three. In a larger team they are separate people who hand work to each other, and the handoff is where projects quietly lose a week. If you are hiring, ask which of the three the person actually does rather than trusting the job title.
What a website developer actually does
Day to day, the work splits into four buckets:
- Building. Turning a design into templates and components — HTML, CSS, JavaScript, a WordPress theme, or an application running on a framework.
- Integrating. Connecting the site to payment providers, CRMs, email systems, booking tools and analytics. This is usually more of the timeline than the visible design is.
- Making it survive. Caching, image compression, database hygiene, backups, staging environments. The unglamorous part that determines whether the site still loads in a year.
- Diagnosing. Reading error logs, reproducing bugs, tracing why a form stopped sending. Roughly a third of a working developer’s week, on a site that has been live for a while.
Notice how little of that is “putting a page together”. Modern tools make the assembly fast; the judgement is in the integration, the performance work and the diagnosis.
Skills that separate a developer from a builder user
| Skill | Why it matters to you |
|---|---|
| HTML, CSS, JavaScript | Can fix what a page builder cannot express |
| Server-side language (PHP, Python, Node) | Custom features without a stack of plugins |
| Database basics | Understands why the site got slow, not just that it did |
| Git | Changes are reversible; work is not lost in a single live file |
| Hosting, DNS, SSL | Can move or launch a site without a support ticket chain |
| Performance and accessibility | Pages that work for real users and pass audits |
| Security fundamentals | Knows why updates, least privilege and backups are not optional |
A page-builder specialist is genuinely faster for a five-page brochure site. A developer earns their rate on the site with a booking system, a membership area, a migration, or a performance problem that no plugin solved.
WordPress developer is a specialism, not a lesser one
WordPress runs 58% of the sites whose CMS is known — about 40% of all websites — and the work has its own depth: the hook system, custom post types, REST endpoints, block themes and theme.json, WP-CLI for anything repetitive, and the discipline of not editing a live theme file at midnight. Someone fluent in that stack delivers a WordPress build in days where a generalist spends those days learning it.
If your site runs WordPress, ask for WordPress work specifically — plugin conflicts and update breakage are their own skill, and they are the problems you will actually call about.
Do you need to hire one?
Three honest cases:
- No: a brochure site with five pages, a template theme and text you have written. Learn the block editor, budget a week, and spend the money on content instead.
- Yes, briefly: the site exists but a form, a redirect, a checkout or a Core Web Vitals score refuses to behave. A few hours of a developer is cheaper than a month of you guessing.
- Yes, properly: custom functionality, a migration with live traffic, an integration with a business system, or a multi-user site. This is where DIY quietly costs more than the quote you avoided.
What you are buying is not typing speed. It is the ability to look at a broken site and know which of forty possible causes is the real one — the same skill that stops a small problem from becoming an outage.
How to judge one in a short conversation
- Ask what they would do with your current site before quoting. A developer who opens with a diagnosis is worth more than one who opens with a package price.
- Ask what happens when an update breaks the site. The answer should mention a staging copy and a restore point, not “we fix it quickly”.
- Ask for one example of a performance or security problem they solved, with numbers. Vague answers here are the norm; specific ones are the signal.
- Ask who owns the code and the hosting account afterwards. If the answer is not “you”, walk away.
FAQ
Is a website developer the same as a web designer?
No. Designers decide how the site looks and how it should feel to use; developers make that real and keep it running. Many people do both, but the skills are different and so are the rates.
Do I need a developer for a WordPress site?
Not for a simple brochure site built on a good theme. You do for custom features, integrations, migrations, or when performance and security problems outgrow plugins.
What does a website developer cost?
Rates vary widely by region and specialism. What drives the number is scope and integration work, not page count — our guide to website development costs breaks down the ranges and what moves them.
Can a developer fix a site someone else built?
Yes, and it is most of the work available. Expect the first hour to be paid diagnosis: reading the theme, the plugin list and the error log before any change is promised.