Quick answer: When you hire a WordPress developer, check real WordPress experience (themes, plugins, security, performance), ask for sites they built and still maintain, confirm how they handle updates and staging, and insist that you own hosting, domain and code. Prefer someone who writes maintainable work over someone who only demos page-builder speed. A clear brief, milestones and written scope protect both sides.
Decide what you actually need
“WordPress developer” covers several roles:
- Builder: comfortable with themes, page builders and common plugins
- Developer: writes custom themes or plugins in PHP, understands hooks and the database
- Full-stack or agency team: design, development, content and ongoing care
A brochure site with a premium theme needs different skills from a membership site, WooCommerce store or intranet. Write the outcome first: number of templates, integrations, content migration, training and support window. A vague “make us a WordPress site” brief invites mismatched quotes.
Also decide whether you need a one-off build, a redesign on an existing install, or a partner for continuous improvement. Hiring for the wrong shape of work is a common reason projects stall after launch.
Skills worth verifying
Ask for evidence, not slogans.
Core WordPress
- Custom themes or disciplined use of a child theme
- Plugin evaluation: what they install and what they refuse
- Content structure: custom post types and fields when needed
- User roles and editorial workflow
- Comfort with the block editor and classic editor where your content team still needs it
Technical hygiene
- Staging and deployment habits
- Git or another version history (even for smaller projects)
- PHP and MySQL comfort at the level your project needs
- Security basics: updates, least privilege, hardened admin
- Ability to diagnose white screens, plugin conflicts and mail delivery issues
Performance and SEO foundations
- Caching and image handling
- Clean markup and sensible heading structure
- Sitemap, redirects and metadata cooperation with your SEO plugin
- Awareness of mobile performance and third-party script weight
Communication
- Can they explain trade-offs to a non-developer?
- Do they document logins and how the site was built?
- Do they ask about business goals, or only about colours and plugins?
Website documentation should be part of delivery, not an optional extra.
Portfolio questions that reveal quality
Anyone can list famous brands. Better questions:
- Which sites did you personally build, and which did you only edit?
- Can I speak to a client whose site you still maintain?
- What broke on a past project, and how did you fix it?
- How do you handle plugin conflicts after WordPress core updates?
- Show me the admin of a site you are proud of (with permission).
- How do you estimate work you have not done before?
Look for tidy admin areas, restrained plugin lists and clear naming. Messy backends often mean expensive future maintenance. Our notes on website maintenance cost show why that matters for budget planning.
Freelancer, agency or in-house?
Freelancer: flexible and often cheaper for defined builds. Risk: holidays, illness and single points of failure. Ask about backup contacts for emergencies.
Agency: broader skills, process and cover. Cost is higher. Confirm who does the work day to day, not only who sells it.
In-house: best when WordPress is core to operations and change is constant. Still budget for specialist help on security and complex features.
For business-critical sites, prefer a provider who offers WordPress maintenance after launch so updates do not stall. A beautiful build that nobody patches becomes a liability.
Red flags
- Guarantees of “page one in 30 days” bundled into a build quote
- No staging site
- Building as admin directly on production from day one
- Unwillingness to use a child theme or version control
- Keeping exclusive ownership of the theme code or host account
- Huge plugin stacks with overlapping jobs
- No written scope or change process
- Samples that are slow on mobile or full of stock layout clutter
- Pressure to decide on a sales call without a scoped proposal
If someone cannot explain how they will hand the site over, do not hire them for a business site.
What to put in the brief
Share before you ask for price:
- Goals and primary conversions (leads, sales, bookings)
- Must-have pages and integrations (CRM, payments, booking)
- Content: who writes it, who migrates it
- Design references as direction, not as an instruction to copy a competitor
- Timeline and launch constraints
- Who hosts today and where you want to host
- Accessibility or compliance needs if any
- Who will edit pages after launch and how technical they are
A solid brief cuts rework. Pair it with a requirements style document when the project is complex; our software requirements document guide adapts well to larger WordPress builds. Include examples of pages you like and pages you hate, with reasons.
Interview and trial ideas
Useful practical checks:
- Walk through how they would approach your top three features
- Ask them to review your current site and list risks
- For custom work, a small paid trial (a template or plugin spike) beats a long theoretical interview
- Confirm timezone overlap and response times
- Ask how they test: browsers, phones, forms, roles
“It looked fine on my laptop” is not a test plan. Listen for how they talk about edge cases: forms failing, payment webhooks, multilingual URLs, membership renewals.
Contract and ownership essentials
Before work starts, agree in writing:
- You own the domain, hosting account, CMS and code
- Deliverables and milestones with acceptance criteria
- What “done” means for each phase
- Hourly rate or fixed fee, and how change requests are priced
- Third-party licence costs (plugins, stock, fonts)
- Warranty window for bugs after launch
- Confidentiality and data handling
- Exit: how credentials and files are returned
- Whether the developer may showcase the work publicly
Never leave the only admin user as the developer. Create your own owner account on day one. Store licence keys for premium plugins in your company vault.
Budget ranges in plain terms
Prices vary by country and complexity. Mentally separate:
- Design and build
- Content and migration
- Integrations
- Training
- Ongoing care
The cheapest quote often omits staging, redirects, training or post-launch support. Compare like for like. A slightly higher build that is maintainable is usually cheaper over two years than a fragile bargain. Ask what happens in month four when WordPress and plugins need updates; if the answer is silence, add maintenance to the budget now.
Onboarding the person you hire
Once you choose someone:
- Share brand assets, analytics access and existing tech inventory
- Agree communication channel and weekly update format
- Set milestone demos on staging, not surprise big reveals
- Plan content freeze and launch checklist early
- Book training while the build is fresh, not months later
Good hiring continues after the contract is signed. The relationship works when both sides treat the site as a product that will keep changing.
FAQ
Do I need a developer if I use a page builder?
For a simple site you might not. Once you need custom integrations, membership, complex WooCommerce or performance work, a developer saves money by avoiding plugin piles.
Should the developer also do SEO?
Technical SEO foundations yes. Ongoing content and link strategy is often a different skill. Clarify who owns which part.
Is a website builder safer than hiring someone?
Hosted builders reduce technical risk and also limit flexibility. Hire a developer when you need ownership, custom behaviour or deeper integrations.
How do I compare two similar quotes?
Compare assumptions: number of templates, revisions, migrations, integrations, training hours and warranty. The spreadsheet column that only shows a total fee hides the real difference.
Hire for maintainability
The right WordPress hire builds something your team can edit, your host can support and another developer can take over later. Check skills, process, ownership and scope before you compare day rates. If you want a WordPress build or rebuild done with clear handover, see how we help businesses turn visitors into customers.
