How to hire a WordPress developer
How to hire a WordPress developer
To hire a WordPress developer in 2026, first decide whether you actually need WordPress (Webflow, Framer, or Astro often beat it for marketing sites), then screen for stack-specific fluency: Gutenberg block development, ACF Pro, WooCommerce, headless via WPGraphQL, and modern PHP 8.2+. Expect to pay $40 to $150 per hour on freelance platforms, $80 to $200 on vetted networks, or roughly $500 to $2,000 per week through booking marketplaces with no hiring loop.
WordPress still powers 43.5% of the web. That's the reason the talent pool is enormous and also the reason the average WordPress hire goes badly: most "WordPress developers" are theme tweakers, not engineers. This guide walks through the honest 2026 screening playbook, what to pay, and when to skip the role entirely.
First, do you actually need a WordPress developer?
Before you write the job post, answer this: what is the site for?
If the answer is "a marketing site with a blog and three landing pages," you probably don't need WordPress in 2026. Webflow ships faster, Framer has better motion primitives, and Astro plus a headless CMS like Sanity gives you a static site that loads in under a second with zero plugin patching. The real cost of WordPress isn't the build, it's the maintenance: 94% of WordPress security vulnerabilities come from poorly coded plugins, and someone has to keep them patched.
WordPress is still the right answer when:
- You run WooCommerce with non-trivial product logic, subscriptions, or B2B pricing rules.
- You have a membership site on MemberPress, Paid Memberships Pro, or Restrict Content Pro.
- You have existing WordPress investment (custom theme, ACF field groups, hundreds of posts) that would cost more to migrate than to maintain.
- You need deep editorial workflows for a content team that already lives in the WP admin.
- You're building a headless front-end (Next.js, Astro, Faust) on top of WP as a content API.
If none of those apply, hire a Webflow developer or a Shopify partner instead. Be honest with yourself before you spend the money.
What to look for in a WordPress developer
A real WordPress engineer in 2026 should clear all of these:
PHP fundamentals on a modern stack. PHP 8.2+ syntax, typed properties, named arguments, enums. They should know why wp_unslash exists and what wpdb->prepare actually protects you from.
Gutenberg block development. Custom blocks built with the @wordpress/scripts toolchain, not just classic shortcodes. They should understand block.json, the InnerBlocks API, and dynamic vs static blocks.
Advanced Custom Fields (ACF Pro). Field groups, flexible content, options pages. ACF is the de facto data layer for custom WordPress, and a developer who avoids it usually defaults to bloated builders.
WooCommerce internals. Hooks (woocommerce_checkout_process), custom payment gateways, Action Scheduler, the new HPOS (High-Performance Order Storage). If they can't explain HPOS, they haven't shipped Woo since 2024.
Modern dev practices. Composer for dependencies, Bedrock for the WP folder structure, Sage 11 for themes, WP-CLI for everything they'd otherwise click. A developer who FTPs into the live server is a 2014 developer.
Headless WP literacy. WPGraphQL plus Faust.js or a custom Next.js front-end, REST API caching, ISR. Not every project needs this, but if you're hiring senior, they should have shipped at least one.
AI-native workflow. Cursor or Claude Code in their daily loop. PHP gets less love than TypeScript in model training data, so the engineers who use AI well on WP have explicit prompts for sanitization, escaping, and nonces. Ask them to walk you through their last block they shipped: what did they prompt vs write themselves?
Performance and security. Object caching with Redis, page caching with the host's stack (Kinsta, WP Engine, Pressable), Critical CSS, Core Web Vitals targets. Security: prepared statements, capability checks, nonces, sanitize-on-input plus escape-on-output.
If the candidate can't speak to half of those, they're a site-builder, not a developer. Site-builders are fine for $300 Elementor jobs. Don't pay them developer rates.
Where to find WordPress developers in 2026
Every channel has a real trade-off. Here's the honest take.
| Channel | Vetting | Typical Rate | Best for |
|---|---|---|---|
| Codeable | 2% acceptance, WP-only | $80-$120/hr | Custom plugin work, ACF builds |
| Toptal | Top 3%, generalist | $100-$200/hr | Headless, complex integrations |
| Upwork | Self-reported, ratings | $20-$80/hr | Small theme tweaks, defined scope |
| Fiverr | None | $10-$50/job | One-off fixes only |
| WordPress.org Jobs Board | None, community | $50-$150/hr | Niche WP specialists |
| WPhired / Smashing Jobs | None | $60-$120/hr | Full-time and long-term contract |
| LinkedIn / direct outreach | Yours | Negotiated | Senior engineers, fractional CTO |
| Cadence | Voice interview + AI-native vetting | $500-$2k/wk | 2-12 week scopes, no hiring loop |
A few notes the SERPs won't tell you:
Codeable is the only WP-specific vetted network worth using. Their 2% acceptance is real, and their dispute mediation is functional. The downside: minimum project size and you pay a premium.
Toptal isn't WP-focused. Their WP roster is thinner than their React or Python rosters. Use them when your project is half WordPress, half something else (a headless Next.js front-end, a custom payment integration, a data pipeline).
Upwork works only with tight scope. A "build me a custom WooCommerce checkout" job will burn you. A "fix this specific bug in this specific plugin, here's the repo" job works fine. Read the founder's playbook for hiring on Upwork before you post.
WordPress.org and WordCamp still produce the best senior engineers, but you have to do the sourcing work yourself. The contributors to core, Gutenberg, and major plugins (Yoast, WooCommerce, Elementor) are reachable on Slack and Twitter. Cold-DM the right person and you'll get a response.
How to evaluate skills (interview playbook)
Skip the whiteboard. WordPress is a contextual ecosystem, and synthetic puzzles don't predict who can ship inside it. Run this instead:
1. Portfolio audit, 15 minutes. Ask for three live URLs they built. Run each through PageSpeed Insights and Wave (accessibility). If their own portfolio site scores under 60 on mobile, that's your answer.
2. Code review on their last PR. Have them screen-share their last real WordPress pull request and walk you through the diff. You're not looking for clever code, you're looking for whether they can explain their choices.
3. Live build, 30 minutes, paid. Pay them $100 to $200 to build a custom Gutenberg block in front of you using their actual setup (Cursor, Local by Flywheel, their preferred plugins). Watch how they prompt the AI, where they verify, how they handle the inevitable error. This single hour tells you more than five interviews.
4. AI-native questions. Ask "Walk me through your last WP feature using Cursor or Claude. Where did the model help? Where did you override it?" The wrong answer is "I don't really use AI." The wrong answer is also "AI writes everything for me." The right answer involves explicit verification and a clear sense of where the model is unreliable (sanitization, capability checks, nonce handling).
5. References that matter. Don't ask "was X good to work with?" Ask "describe the last bug X shipped to production. How did you find out about it, and how did they handle it?" Engineers who can name the bug are honest. Engineers who say "they never ship bugs" haven't shipped.
The same evaluation logic applies whether you're hiring a Shopify developer or a Python developer remotely: screen for stack-specific fluency, not a generic algorithms quiz.
What to expect to pay
Here's the 2026 rate map, normalized across engagement types:
| Engagement | Junior | Mid | Senior | Lead |
|---|---|---|---|---|
| Freelance hourly (US) | $40-$60 | $60-$100 | $100-$150 | $150-$250 |
| Freelance hourly (EU/LatAm) | $25-$45 | $45-$80 | $80-$130 | $130-$200 |
| Full-time salary (US) | $65-85k | $85-115k | $115-160k | $160-220k |
| Agency rate | $100-$150 | $150-$200 | $200-$300 | $300+ |
| Cadence weekly booking | $500/wk | $1,000/wk | $1,500/wk | $2,000/wk |
A few sanity checks. A senior WP engineer in the US who quotes you $40 per hour is either lying about their seniority or desperate. A junior who quotes $200 per hour is repackaging an agency rate as a freelance one. If you're hiring offshore, the offshore developer hiring guide and the Bangalore-specific playbook cover the regional nuances.
The Cadence weekly numbers convert to roughly $12 to $50 per hour at 40 hours, which looks cheap on paper. The honest framing: that's the engineer's pay-out at 80% of the weekly rate, not a discounted hourly. The trade-off is that you commit weekly, not hourly, and you replace any week without notice instead of negotiating an exit.
If you're staring at this table and not sure whether to hire full-time or go contract, a quick read on hiring a fractional CTO reframes the calculus for early-stage founders.
The alternative: skip the hiring loop entirely
A traditional WordPress hire takes 30 to 60 days from job post to first commit. You write the spec, post it on three boards, screen 40 applications, schedule 8 interviews, run 3 paid tests, negotiate, onboard. By the time the engineer ships their first PR, the scope has usually shifted.
For 2 to 12 week scopes, that loop doesn't make sense. Cadence is a booking marketplace where founders book vetted engineers by the week. Every engineer is AI-native by default, vetted on Cursor and Claude Code fluency in a founder-led voice interview before they unlock the platform. The pool is 12,800 engineers across stacks, with a 27-hour median time to first commit.
If you've identified a clear WordPress scope (a Gutenberg block library, a WooCommerce subscription migration, a headless Faust front-end), see how Cadence's hiring flow works and skip the recruiter loop. You get a 48-hour free trial, you replace any week, and you only pay weekly. Long-term placements are still a better fit when you've validated the role and you want to build culture across 6 plus months. For everything shorter, booking wins.
Try Cadence's 48-hour free trial. Pick the tier (junior $500, mid $1k, senior $1.5k, lead $2k weekly), describe the scope, and we shortlist four engineers in two minutes. Replace any week, no notice.
FAQ
How long does it take to hire a WordPress developer in 2026?
Through traditional channels, 30 to 60 days from job post to first commit. Through vetted networks like Codeable or Toptal, 5 to 10 days. Through booking marketplaces like Cadence, under 48 hours.
What's a fair hourly rate for a senior WordPress developer in 2026?
In the US, $100 to $150 per hour for freelance, $115k to $160k full-time. In EU and LatAm, $80 to $130 per hour freelance. Add 30 to 50% for headless WP work (WPGraphQL, Faust, Next.js).
Should I hire a freelancer or an agency for my WordPress build?
Freelancer if the scope is clear and you can manage the project. Agency if you need design, dev, and ongoing maintenance bundled and you're willing to pay 2 to 3 times the freelance rate for the operational layer. For 2 to 12 week scopes, a weekly booking sits in between.
How do I evaluate a WordPress developer if I'm not technical?
Run a 30-minute paid live build and watch how they work, even if you don't follow every keystroke. Ask them to explain a past bug in plain English. If they can't make their work legible to you in person, they won't make it legible in a Slack update either.
Do I even need WordPress in 2026?
For most marketing sites, no. Webflow, Framer, or Astro plus a headless CMS will be faster, cheaper, and safer. WordPress is still the right call for WooCommerce, membership sites, deep editorial workflows, and existing investments too costly to migrate.