How to Hire a WordPress Developer: What to Ask, What to Pay, and What to Avoid

Hiring a WordPress developer is not like hiring for most other services. The barrier to calling yourself a WordPress developer is low — page builders and templates mean someone with six months of self-teaching can produce a site that looks professional but is built on a foundation that will cost you in maintenance, performance, and security within a year. Evaluating the right signals filters that out before you sign a contract.

Step Zero: Define What You Actually Need

WordPress development covers a wide range. A developer who is excellent at building custom plugins from scratch may have no interest in setting up a template-based brochure site. A designer-developer who builds beautiful marketing sites may have no experience with WooCommerce payment gateway integrations. Being specific about your project type narrows the field and makes evaluation faster.

The main categories:

Theme development: Custom visual design and front-end code, built as a WordPress theme
Plugin development: Custom functionality added to WordPress through a plugin
WooCommerce development: Online store setup, custom product types, payment and shipping integration
Site builds using existing themes: Configuring and customizing a premium theme (Avada, Divi, GeneratePress) to fit your brand
Migrations: Moving a site from another platform to WordPress, or between WordPress hosts
Maintenance and support: Ongoing updates, security monitoring, and bug fixes

Know which of these you need before approaching developers. "Build me a WordPress website" is too vague to get a useful quote and too vague to evaluate whether a developer is the right fit.

Where to Find WordPress Developers

Freelance platforms

Upwork and Toptal both have large pools of WordPress developers. Upwork ranges enormously in quality and price — filtering by job success score above 90% and at least 50 hours logged narrows it to developers with a track record. Toptal pre-vets developers and charges a significant premium for that vetting. Neither platform's filtering replaces your own evaluation process.

WordPress-specific communities

The WordPress Job Board at jobs.wordpress.net is maintained by the WordPress.org community and is free to post on. Developers who seek work there tend to be WordPress-focused rather than generalist freelancers. The advanced WordPress Facebook group and Post Status Slack community are also places where serious WordPress developers spend time.

Agencies

A WordPress development agency brings a team — typically a project manager, a developer, and often a designer — which reduces your coordination burden. Agencies cost more than individual freelancers for equivalent work but offer more reliability: if a single developer gets sick or quits mid-project, an agency absorbs that risk. For projects above $10,000 or with hard deadlines, the agency premium is often worth it.

Referrals

A referral from a business you trust that had a good experience with a specific developer is worth more than any marketplace profile. The person referring can speak to what the working relationship was actually like, not just what the finished product looks like.

Evaluating Portfolios

A portfolio is a marketing document, not an audit. Every site in it is the developer's best work under favorable conditions. The evaluation goal is to find signal beyond the surface.

Look at live sites, not screenshots

Visit the actual sites in the portfolio. Run them through Google PageSpeed Insights. A developer who claims WordPress expertise but whose portfolio sites score below 70 on mobile performance either did not care about performance or did not know how to optimize it. Neither is a good sign for your project.

Ask about their role

A portfolio site may have been a team effort. Ask specifically: "On this site, what did you build versus what was done by someone else?" A developer who can describe precisely what they contributed — and what they did not do — is being honest. One who claims full credit for everything is a yellow flag.

Look for custom code versus assembled templates

There is nothing wrong with building on premium themes or page builders — it is efficient for many projects. But a developer should be able to tell you which sites in their portfolio involved custom PHP, custom CSS beyond theme defaults, or custom plugin code. If every site is "I set up Elementor and configured the theme," their skill ceiling is lower than someone who has written custom post types, hooks, and shortcodes.

Questions to Ask Before Hiring

Ask these before you discuss price. The answers tell you more than a rate sheet.

"Walk me through how you'd build [your specific project type]." A competent developer can describe their approach without being vague. If the answer is "it depends on a lot of things" without any elaboration, probe deeper. They should be able to give you a general technical approach for a project of your type even without a full spec.
"What version of PHP do you write against and how do you keep up with deprecations?" WordPress officially recommends PHP 8.1+. A developer still writing code that requires PHP 7.4 is behind on the language.
"How do you handle local development and staging?" A developer doing all their work on a live server is a problem. The answer should describe a local development environment (LocalWP, Docker, MAMP) and a staging workflow before pushing to production.
"What happens if something breaks after launch?" You want a clear answer: a warranty period for bugs in their code, a support retainer option, and clear boundaries on what is covered. "We'll figure it out" is not an answer.
"Who will own the code and assets when the project is done?" The correct answer is: you own everything your money paid for. Developers sometimes try to retain license rights to custom code or theme child files. This matters if you ever need to switch developers.

Rates and Budgets

WordPress developer rates vary widely based on location, skill level, and project type. Broad ranges based on current market rates:

Developer Type	Hourly Rate (US)	Typical Project Price
Freelancer (offshore, general)	$15–$40/hr	$500–$3,000
Freelancer (US/Canada, mid-level)	$75–$125/hr	$3,000–$10,000
Freelancer (US, senior/specialist)	$125–$200/hr	$8,000–$25,000
Agency (small)	$100–$150/hr	$5,000–$30,000
Agency (mid-size)	$150–$250/hr	$15,000–$100,000+

The relationship between rate and quality is real but not linear. A $200/hr senior WordPress specialist will produce better custom plugin code than a $20/hr generalist freelancer. But a $150/hr agency building a template-based brochure site is almost certainly overkill. Match the resource to the actual complexity of the work.

Fixed-price contracts beat hourly billing for most clients. They transfer the risk of scope creep to the developer and give you a defined deliverable. Hourly contracts are appropriate when the scope is genuinely uncertain — ongoing maintenance, exploratory development, or large platform builds where requirements evolve.

Red Flags to Watch For

No contract or vague contract: A professional developer works from a written agreement that specifies deliverables, timeline, payment schedule, revision limits, and ownership terms. "We'll do it on a handshake" is a red flag at any price point.
Asking for full payment upfront: A standard payment structure for a fixed-price project is 50% at contract signing and 50% at launch. Developers who ask for 100% upfront before work begins have no incentive to finish.
No questions about your business: A developer who quotes you without asking what your site needs to accomplish, who your audience is, or what success looks like is selling a generic product, not solving your problem.
Portfolio that only shows design, never functionality: Screenshots prove a site looks good. They do not prove it loads quickly, is accessible, passes Core Web Vitals, or was built with maintainable code. Ask for PageSpeed scores and whether sites are still live and maintained.
"I'll handle the hosting too" with no specifics: Developers who bundle hosting without disclosing the underlying provider, the plan specs, or whether you will have independent access to your account create a lock-in situation. You should always have direct access to your own hosting account.

What the Contract Should Cover

Whether you use a template or a custom agreement, the contract should address:

Deliverables: specific pages, features, and integrations included in scope
Timeline: milestone dates and what triggers each payment
Revision rounds: how many rounds of feedback are included before additional charges apply
Ownership: all code, design assets, and content belong to you at project completion
Confidentiality: the developer will not disclose your business information
Warranty: a defined period (typically 30–90 days) during which the developer fixes bugs in their own code at no charge
Termination: what happens if either party ends the agreement early, and what work-in-progress is delivered and paid for

The Alternative: An Agency Relationship

For businesses where the website is a serious revenue channel, the freelancer-hiring process is worth the effort. For businesses that need a well-built site but do not have the bandwidth to manage a developer relationship themselves, an ongoing agency relationship often makes more sense.

At Vortex Media, we handle the full lifecycle: design, development, hosting, maintenance, and security monitoring. If you would rather have a team that knows your site inside out and fixes problems before you notice them, book a free call and we will scope what that looks like for your specific situation.