Hiring a WordPress developer — every question

Define the outcome (new site, rescue, store, speed), shortlist by WordPress-shaped proof — live sites they built, not just themes installed — then vet with references and a small paid test task. WordPress-specific checks matter more than generic ones: ask about their plugin work, their update discipline, their staging process. The general method plus the WordPress specifics: the hiring guide.

WordPress-specific channels, ranked by fit: Codeable (WordPress-only vetted marketplace — see the honest comparison), the official WordPress.org jobs board, independents who publish WordPress work and rates (this desk — start here), general marketplaces for small tasks, and agencies for multi-workstream builds. For WordPress specifically, specialist proof beats general-platform rankings.

Look for the WordPress tells: sites that are still fast a year after launch (check their portfolio on your phone), custom block or theme work rather than everything-in-a-builder, plugin contributions or writing, and a coherent answer on how they handle updates and plugin conflicts. A WordPress developer whose own portfolio sites are slow is showing you their future work.

Hire one accountable generalist on WordPress rather than the cheapest bidder or a big agency: a 5–10 page site with a proven theme approach and a maintenance plan is a $3,000–12,000 engagement from a senior independent. Prioritise handover quality — the office manager must be able to edit content after a 10-minute walkthrough. The ownership terms that protect you: contracts & ownership FAQ.

Demand WooCommerce-shaped proof: live stores with real revenue, checkout customisation work, and platform-migration experience. WooCommerce skills sit on top of WordPress skills — a store is a WordPress site plus catalog logic, payments, shipping and performance under load. Start at the WooCommerce section for what to demand, and the hiring specifics in the platform-developers FAQ.

2026 bands: India independents $20–35/hr, Eastern Europe $45–65, US/UK $75–120. Fixed-price: custom marketing site $3,000–12,000 (senior independent), WooCommerce store $4,000–20,000, rescue or takeover work quoted after a read-only audit. Page-builder builds sit at the bottom of the bands, custom block/theme work at the top. Full rate logic: the rates page.

The honest grid: 5-page business site $2,500–8,000 · 10-page $4,000–12,000 · content-heavy publication $6,000–20,000 · WooCommerce store $4,000–20,000 · membership/LMS site $6,000–25,000 · custom theme (design included) $3,000–15,000. The two variables that move you inside every band: content readiness and how custom the design is. Line-by-line: the cost guide.

Mid-level independent: India $20–30, Eastern Europe $45–60, Latin America $40–60, US $75–110. Senior runs 30–50% above those bands; agencies add 30–60% for the same calibre. WordPress-specific specialists (custom blocks, WooCommerce checkout, performance) price at the top of their local band — and earn it. Compare markets: rates page.

Honest floor: hosting ~$60–120/yr + domain ~$15/yr + a quality theme $50–100 + your labour. That is a real option when the site is an experiment. The professional floor is a scoped one-pager at $500–1,500 from a competent independent. What sits below both — free themes of unknown provenance, nulled premium plugins — is how WordPress sites get hacked; read the maintenance reality first: security checklist.

You are buying judgement about a specific platform's failure modes — plugin conflicts, update cycles, security history, performance decay — plus the standard software liabilities. A WordPress developer's real work is the 80% nobody sees: staging discipline, update strategy, backup verification, clean code that survives the next WordPress version. The visible layout is the cheapest part of a proper WordPress build.

Same geography bands as above — freelancers are the price-setters, agencies price above them. Fixed-price from freelancers: small build $1,500–5,000, mid-size custom $5,000–15,000. The freelancer-versus-agency trade-offs specific to WordPress (maintenance continuity, bus factor) are covered here.

For one WordPress site — the overwhelming majority of cases — a senior freelancer: one accountable name, no markup, direct communication. An agency earns its premium when WordPress is one workstream inside a simultaneous rebrand-plus-campaigns programme, or when procurement needs enterprise rails. The full structural comparison: freelancer vs agency guide.

Dedicated = a developer reserved for your queue monthly, like a team member contracted like a service. Full-time 2026 bands: India $3,000–5,000, Eastern Europe $4,500–7,500, onshore $12,000–18,000+. It fits continuous WordPress work — a growing store, a publishing operation, an evolving membership site — and wastes money on one fixed build. The model mechanics: remote & dedicated FAQ.

Yes — monthly retainers are the standard shape of WordPress care: defined update/fix/edit allowance plus monitoring, $50–300/month from independents for small sites, more for stores. Part-time dedicated slices suit steady improvement work. What a fair retainer includes: the maintenance agreement template shows the clauses.

Reliability tracks process, not letterhead: written scopes, staged payments, update discipline and handover terms. A disciplined freelancer beats a chaotic agency — and WordPress maintenance continuity often favours the freelancer, because the person who built your site keeps maintaining it. Ask both the same question: "show me a project that went wrong." The framework: the comparison guide.

WordPress-shaped proof: live client sites (fast, on your phone), custom work beyond page builders, a staging-and-updates answer, security posture, and clean writing. Then the universal checks — references, a paid test task, code you can have read. The full checklist method: the vetting guide.

The honest stack: PHP (the language WordPress is written in), HTML/CSS/JavaScript, MySQL basics, Git, the WordPress coding and security standards, and — decisive at the senior end — block/editor architecture and performance engineering. Plugin or theme specialisations add depth. A developer who only knows a page builder is a site assembler, not a developer; both can be right for you, but price and risk differ.

The WordPress six: How do you handle plugin conflicts and updates? Show me a site you rescued. How do you keep WordPress fast under real content? What happens if the site is hacked on a Friday? Who owns the theme and plugins you write? What is your staging process? Expected answers and red flags, scripted: the interview template.

A small paid task on a staging copy of your real site beats any quiz: fix a plugin conflict, build one custom block, improve one page's load time. One week of real collaboration predicts a project better than any certificate — and good developers welcome it because it filters their competition. The test-task design: vetting guide.

WordPress-specific reds: everything-in-a-page-builder answers to custom needs, no staging process, nulled-plugin comfort, "admin access only" working habits, no update strategy, and portfolio sites that are slow or dead. Universal reds: full payment upfront, no written scope, vague ownership answers. Any one WordPress red plus one universal red is a pass on the candidate.

Open their client sites on your phone with dev-tools-free honesty: fast? maintained? real businesses? Then check two specifics — do any show custom functionality (not just themes), and are they still standing years later? A portfolio of five live-and-fast WordPress sites beats fifty screenshots. The verification method: the vetting guide.

Mid-level Indian WordPress independents: $20–30/hr; seniors $30–50. Fixed-price: business site $1,500–6,000, WooCommerce store $2,500–10,000, custom plugin or theme work $1,000–8,000. India has the deepest WordPress senior pool in the world — two decades of export-grade platform work. The full market analysis: the India page and the US-vs-India rate math.

The distribution is the same as everywhere — the selection method matters more than the passport. India's specific advantages for WordPress: enormous senior supply, rate arbitrage, and timezone fit for Europe/Asia. Select on live portfolio, written English, and WordPress-specific answers. This desk is an India-based WordPress practice publishing its own rates — judge it like any candidate.

The WordPress-specific protections: scoped access (your hosting, your admin, their user account), a staging environment for all work, staged payments, and a contract with IP assignment — plus backups before anyone touches anything. Remote WordPress work is completely routine; the risks are process-shaped, not geography-shaped. The checklist: remote hiring FAQ.

No single best — overlapping distribution curves by market: India (deepest senior pool, best rates), Eastern Europe (strong engineering culture), Philippines (strong WordPress servicing tradition), US/UK (onshore context, premium rates). For WordPress specifically, India's two decades of platform specialisation make it the volume-quality leader. The honest comparison framework: the rates page covers all markets.

Content edits, menus, plugin settings: do it yourself — WordPress exists so you can. Custom design, performance, security, migrations, anything with a database or a payment: developer territory. The honest self-test: if the site failing would cost money, hire someone accountable; if it would cost an evening, build it yourself. The full decision line: timelines & scope FAQ.

Elementor is excellent for marketing teams building structured pages within a system — and there is a full honest page on Elementor development here. You need a developer when you need speed under real content, custom functionality, integrations, or anything beyond the builder's ceiling. The best WordPress work often combines both: a developer-built component system your team assembles in the builder.

It can draft theme code, snippets and content — a genuine accelerator inside a developer's workflow. It cannot deploy, maintain, secure, take accountability, or fix your production site at 9pm. AI-raised boilerplate still needs a human who can read it, and WordPress's update cycle makes "who maintains this" a permanent question. The honest AI division of labour: the AI FAQ.

Yes — 43% of the web, including a large share of serious business and publishing sites, is not an accident. The honest caveats: unmaintained WordPress is a liability (hence the maintenance checklist), page-builder overload makes sites slow, and simple brochure needs may fit lighter platforms. The platform-versus-platform decisions: WordPress vs Shopify and WordPress vs custom development.