How to Hire a WordPress Developer: What to Look For

Finding the right WordPress developer is harder than it looks. The platform powers over 43% of all websites on the internet, which means the pool of people calling themselves “WordPress developers” is enormous and wildly inconsistent in quality. Some are self-taught freelancers who learned from YouTube videos last year. Others have been writing PHP since WordPress 2.0 and could rebuild a theme from scratch without documentation. Knowing how to hire a WordPress developer who actually fits your project requires knowing what questions to ask and what red flags to watch for.

We’ve reviewed hundreds of codebases over 15+ years of WordPress work at Weboption. The number of sites built by undertrained developers that come through our door is, honestly, depressing. Broken hooks, hardcoded credentials, zero version control, plugin soup. The good news: the filtering process is simpler than most people think if you know what to look for.

Understand what type of WordPress developer you actually need

WordPress development is not a single skill. There are at least three distinct types of practitioners, and mixing them up is one of the most common and expensive mistakes clients make.

Theme developers specialize in front-end work. They build custom themes, translate Figma or Sketch mockups into working templates, and handle CSS, JavaScript, and the WordPress template hierarchy. If your project is primarily about how the site looks and feels, this is the person you want.

Plugin developers work deeper in the stack. They write PHP classes, hook into WordPress core actions and filters, build REST API endpoints, and sometimes deal with database queries directly. If you need custom functionality that does not exist in any off-the-shelf plugin, you need someone with solid plugin development experience.

Full-stack WordPress developers handle both layers. They are more expensive and harder to find, but for complex projects involving custom post types, Gutenberg block development, WooCommerce extensions, or headless WordPress setups, you need someone who can work across the whole codebase. No shortcuts here.

Be honest about your project before you start interviewing. A site refresh on an existing theme is a very different job from building a membership platform with custom user roles and payment integration. Scope clarity saves everyone time.

What to look for in a portfolio

Anyone can build a nice-looking portfolio page. What you want is evidence of real technical depth, not just pretty screenshots.

Ask for GitHub or GitLab profiles. A developer who writes clean, documented code and commits regularly is showing you their actual working habits. Look at the commit history on their repositories. Are commits frequent and descriptive, or are there just two commits labeled “initial” and “final”? That tells you everything.

Ask about specific projects and listen for concrete details. A developer who built a WooCommerce store should be able to tell you which payment gateways they integrated, what version of WooCommerce they worked with (the current stable release is 9.x), and what custom hooks they wrote. Vague answers about “building e-commerce sites” are a warning sign. Push back. If they can’t go specific, they probably weren’t the one doing the real work.

Look for experience with modern WordPress development practices. The block editor (Gutenberg) has been the default since WordPress 5.0, released in 2018. A developer who still builds everything in the classic editor or who has no experience with React-based block development is behind the curve. For simpler projects that might not matter much. For anything you plan to maintain and grow over the next three years, it matters a lot.

The misconception about WordPress being easy to develop for

There is a widespread belief that WordPress is simple, so WordPress development must be simple too. This belief leads to a lot of bad hiring decisions and expensive site rebuilds.

The WordPress admin interface is relatively accessible. Installing plugins and changing themes does not require a developer at all. But actual development work on WordPress involves understanding a hook system with over 2,000 documented action and filter hooks, PHP namespacing, the WP_Query class and its performance implications, how WordPress handles database abstraction through WPDB, REST API authentication, block.json schema definitions for Gutenberg blocks, and security considerations around nonce verification, data sanitization, and capability checks.

A developer who does not know what wp_enqueue_scripts does, or who cannot explain the difference between sanitize_text_field() and esc_html(), has gaps in their knowledge that cause real problems. Sites built by undertrained developers frequently have SQL injection vulnerabilities, XSS attack surfaces, or performance issues that only appear under real traffic. After auditing over 200 WordPress installs, the most common issue we find is unsanitized input from custom forms going straight into database queries. Not acceptable.

When you hire a WordPress developer, expect to pay for real expertise. Experienced freelancers in the US typically charge between $75 and $150 per hour. Experienced agencies in Brazil, like Weboption, offer competitive rates without sacrificing quality because of the difference in operating costs. Paying $15 per hour for WordPress development is almost always a path to expensive rewrites six months later.

Interview questions that actually reveal skill level

Generic interview questions do not work well for technical hires. Here are specific questions worth asking when you hire a WordPress developer.

Ask them to explain how they would add custom functionality without modifying core WordPress files. The right answer involves creating a child theme or a custom plugin, using hooks, and never touching files in the /wp-includes/ or /wp-admin/ directories. Any answer that involves editing core files directly should end the conversation immediately.

Ask how they handle WordPress performance optimization. A good developer will mention object caching (Redis or Memcached), proper use of transients for expensive database queries, image optimization through tools like Imagify or ShortPixel, and leveraging a CDN. They should also know what Query Monitor reveals about slow database calls. Honestly, if they’ve never used Query Monitor, that’s a red flag.

Ask about their deployment workflow. Do they use local development environments like LocalWP or Lando? Do they use version control? How do they push changes from staging to production without overwriting the database? Developers without a clear answer here will cause production incidents. We’ve cleaned up the aftermath of these incidents too many times to count.

Ask about security practices. They should mention keeping WordPress core, themes, and plugins updated, using tools like Wordfence or Solid Security for monitoring, setting correct file permissions (644 for files, 755 for directories), and disabling the XML-RPC endpoint if not in use.

Freelancer vs. agency: which makes more sense?

Both options have legitimate use cases. A single experienced freelancer is often the right choice for a small project with a clear scope and a short timeline. The communication overhead is lower, and if you find someone good, the relationship can work well for years.

Agencies make more sense for larger projects, especially ones that involve multiple specialists working in parallel, ongoing maintenance contracts, or projects where you need accountability beyond one person’s availability. A freelancer getting sick or landing a bigger client mid-project is a real risk. An agency absorbs that risk internally.

What agencies also bring is accumulated experience. A team that has built dozens of WordPress sites has seen the same problems repeat and knows how to avoid them. They have established processes for QA, staging deployments, and performance testing. That experience is worth paying for on complex builds.

One practical middle ground: hire a senior freelancer or small agency for the build, and negotiate a monthly retainer for maintenance. WordPress sites are not static objects. Plugins release updates every few weeks, security patches need to be applied promptly, and performance needs monitoring. Ongoing support is not optional for a serious web presence.

Checking references and setting up the engagement correctly

References matter more in development than in most fields because bad code is invisible until it fails. Ask to speak with two or three previous clients. Ask specifically whether the project was delivered on time, whether the developer communicated clearly about problems when they came up, and whether there were any post-launch issues that required fixes.

Before signing any contract, make sure the scope of work is written down with enough detail that both parties agree on what “done” means. Vague scopes lead to disputes. The contract should specify who owns the code after delivery, what hosting environment is expected, whether SEO setup is included, and what the handoff process looks like.

Get access to the staging environment during development, not just at the end. Reviewing work incrementally catches problems early, when they are cheap to fix. We require this on every project we run. It protects the client and keeps our team accountable.

Frequently asked questions

How much does it cost to hire a WordPress developer?

Experienced WordPress developers in the US charge between $75 and $150 per hour for freelance work. Agencies in Brazil with equivalent experience often charge less due to lower operating costs, without the quality drop. Rates under $25/hour almost always reflect junior skill levels, which cost more in rewrites and fixes down the road.

What is the difference between a WordPress developer and a WordPress designer?

A WordPress designer focuses on visual layout, color, typography, and user experience. A WordPress developer writes the code that makes things function: custom post types, plugin integrations, REST API endpoints, and Gutenberg blocks. Many projects need both, and some developers have strong design skills, but they are different disciplines with different hiring criteria.

Should I hire a freelancer or an agency for my WordPress project?

For small, well-scoped projects, a skilled freelancer works well and usually costs less. For larger builds, projects with multiple moving parts, or anything requiring ongoing maintenance and accountability, an agency is the safer choice. The key risk with freelancers is availability: one illness or competing project can stall your build for weeks.

How do I know if a WordPress developer is actually skilled?

Ask for their GitHub profile and look at real commit history. Ask specific questions: how they would handle performance optimization, what their deployment workflow is, and how they manage security. A skilled developer gives specific, technical answers immediately. Vague answers about “extensive experience” without concrete details are a reliable indicator of limited depth.

What questions should I ask before hiring a WordPress developer?

Ask how they add custom functionality without editing core files. Ask what tools they use for local development and deployment. Ask how they approach performance and security. Ask for two or three client references and actually call them. These five areas cover the most common failure points we see when clients bring broken projects to us after hiring the wrong person.

Ready to find the right developer for your WordPress project?

Hiring a WordPress developer who genuinely knows the platform takes more diligence than most people expect. The right questions and a clear-eyed look at portfolios filter out most of the bad fits quickly.

At Weboption, we’ve been building and maintaining WordPress sites for clients across multiple industries for over 15 years. If you want to talk through your project and get a realistic assessment of what it will take to build it right, reach out at weboption.com.br/contato. We give you a straight answer about scope, timeline, and cost before you commit to anything.