WordPress developer is a title that covers an enormous range of actual capability — from someone who installs Elementor, selects a theme, and configures WooCommerce, to an engineer who writes object-oriented PHP plugins from scratch, develops custom Gutenberg blocks in React, builds REST API integrations, and architects headless WordPress setups for high-traffic sites. The hiring manager distinguishing between these two profiles reads the CV for one thing: evidence of custom development versus configuration. "WordPress development, theme customization, plugin installation, and site management" describes the configurator. "Built a custom WordPress plugin in PHP 8 OOP to replace a £12,000/year SaaS subscription — REST API endpoints for mobile app integration, WP-CLI bulk import command, and ACF-backed custom admin interface" describes the engineer. Most WordPress developer CVs use the configurator's language even when the candidate is the engineer. This guide covers the custom development signals, performance optimization outcomes, and technical vocabulary that move a WordPress developer CV into the right shortlist.

What WordPress Developer Job Descriptions Require in 2026

WordPress developer JDs in 2026 have bifurcated clearly:

Agency WordPress developer: The most common role profile. Responsible for building custom themes (usually from a starter theme like Sage, Underscores, or custom from scratch), developing bespoke plugins for client requirements, WooCommerce customization (custom payment flows, product variations, order management), and site performance optimization. JDs at professional agencies consistently require: PHP proficiency (OOP PHP, WordPress hooks and filters system, custom post types, REST API), Git-based workflow (staging environments, child themes not core edits), and JavaScript capability for block development or JavaScript-driven interactions. Page builder expertise (Elementor, Bricks) is mentioned as "nice to have" at professional agencies but is sometimes a disqualifier at those that build custom.

In-house WordPress developer (media and content companies): Focus shifts toward performance at scale (caching strategies, database query optimization, CDN configuration, Core Web Vitals), multisite network administration, and integration with third-party editorial tools, analytics platforms, and ad technology. High-traffic WordPress sites (1M+ monthly pageviews) require different skills from typical agency WordPress work — object cache implementation, transient API usage, deferred loading patterns, and CRON management.

WordPress plugin/product developer: Building commercial or open-source WordPress plugins. Requires: deep OOP PHP, WordPress coding standards compliance, PHPUnit testing, readme.txt/GPL licensing familiarity, Freemius or Easy Digital Downloads integration for commercial licensing, and often internationalization (i18n) and translation file management.

Headless WordPress developer: Growing segment where WordPress is used as a CMS (content management, ACF-driven data structures, REST API or WPGraphQL for data delivery) with a decoupled frontend — usually Next.js or Gatsby. Requires: WPGraphQL or WP REST API fluency, JavaScript/TypeScript/React at frontend level, understanding of static site generation vs. server-side rendering, and deployment to Vercel, Netlify, or similar.

Core requirements across most WordPress JDs: PHP (working knowledge minimum; OOP PHP for senior roles), WordPress action and filter hooks (the fundamental extension mechanism), Git, staging/production workflow, responsive CSS, and some JavaScript capability. WooCommerce is listed as required in the majority of UK agency JDs.

WordPress developer salaries in 2026: £32K–£55K UK for agency roles; £45K–£75K for senior in-house or headless WordPress specialists. Freelance: £350–£650/day.

ATS Keywords for a WordPress Developer Resume

WordPress ATS filtering uses specific development terminology rather than generic web development terms. "WordPress experience" is weaker than "custom plugin development", "Gutenberg block development", "WooCommerce customization", and "WordPress REST API."

Essential ATS terms for a WordPress developer resume:

  • Title variants: WordPress Developer, WP Developer, WordPress Engineer, WordPress Plugin Developer, WooCommerce Developer, Full Stack WordPress Developer, Headless WordPress Developer
  • Core WordPress: WordPress, custom theme development, custom plugin development, WordPress hooks, actions and filters, WordPress REST API, WP-CLI, custom post types, taxonomies, WordPress Multisite, child theme
  • Languages: PHP, PHP 8, OOP PHP, JavaScript, jQuery, React (Gutenberg blocks), TypeScript, HTML5, CSS3, SASS, SCSS, Tailwind CSS, Bootstrap
  • Content and fields: ACF, Advanced Custom Fields, Pods, Carbon Fields, Metabox, CPT UI, custom fields
  • Block development: Gutenberg, block editor, custom blocks, Full Site Editing, FSE, block patterns, block variations, @wordpress/scripts
  • WooCommerce: WooCommerce, WooCommerce customization, WooCommerce hooks, payment gateway integration, WooCommerce REST API, WooCommerce Subscriptions, WooCommerce bookings
  • Performance: Core Web Vitals, LCP, CLS, FID, FCP, PageSpeed Insights, caching, WP Rocket, Redis, Memcached, W3 Total Cache, Cloudflare, CDN, WebP, image optimization, lazy loading
  • Headless: headless WordPress, headless CMS, WPGraphQL, GraphQL, Next.js, Gatsby, Vercel, Netlify
  • Security: Wordfence, security hardening, SSL, WAF, two-factor authentication, WordPress updates, malware scanning
  • Development workflow: Git, GitHub, GitLab, Bitbucket, staging, deployment, Composer, npm, Webpack, Vite, Local by Flywheel, DDEV
  • Hosting: WP Engine, Kinsta, Cloudways, Flywheel, SiteGround, Pantheon, managed WordPress hosting
  • Long-tail phrases: WordPress developer resume, how to write a WordPress developer resume, WooCommerce developer cv, WordPress plugin developer resume, headless WordPress developer resume, PHP WordPress developer resume

Placement: "WordPress Developer" with your primary specialization (WooCommerce / headless / plugin) in the headline. PHP and OOP PHP explicitly named — these are the signals that distinguish professional development from page builder work. Core Web Vitals score improvements (e.g., PageSpeed from 34 to 87) in your experience bullets wherever they exist — these are concise, verifiable, and client-valued.

WordPress Developer CV Structure and Bullets That Show Custom Development Depth

Section order:

  1. Headline — "WordPress Developer | PHP 8 · WooCommerce · Gutenberg Blocks · Headless CMS · Core Web Vitals"
  2. Skills — PHP & WordPress / Block Development / WooCommerce / Performance / JavaScript / DevOps & Hosting
  3. Experience — 4–5 bullets per role; custom development evidence, performance outcomes, and client/project scale per bullet
  4. Projects — open-source plugins (link to WordPress.org plugin page or GitHub), notable portfolio sites, headless WordPress repos

One to two pages. Agency developers with large client volumes: keep project descriptions brief and focus on the most technically complex. In-house developers: include traffic scale and performance metric baselines.

Three elements make a WordPress developer bullet convincing: the custom development scope (what was built from scratch, not installed), the technical approach (OOP PHP, React blocks, REST API, headless architecture), and the measurable outcome (PageSpeed score, conversion rate, cost saving, traffic handled). Three examples:

  • Developed a custom WordPress plugin to replace a client's £12,000/year SaaS property listing subscription — PHP 8 OOP architecture with a custom post type, ACF field groups for property attributes, REST API endpoints for mobile app integration, and a WP-CLI command for bulk import from the client's legacy database; 82% annual cost reduction with equivalent functionality retained
  • Migrated a WooCommerce store with 38,000 SKUs and £2.4M annual revenue from Shopify to a headless WooCommerce setup with Next.js frontend — reduced average page load time from 6.2 seconds to 1.4 seconds, Core Web Vitals passed on all metrics; client reported a 14% conversion rate improvement in the 90-day period following launch
  • Optimised performance for a media WordPress site averaging 1.2M monthly pageviews — implemented Redis full-page object caching, lazy loading for all below-the-fold images, WebP conversion for 18,000 existing media assets, and Cloudflare CDN with edge caching; mobile PageSpeed Insights score improved from 34 to 87 and bounce rate fell by 8% over the following 60 days

WordPress developer interviews often include a code review (find the issue in this plugin code), a live PHP exercise (write a custom hook for this requirement), or a technical discussion (how would you structure a WooCommerce customisation for this use case). Your CV's custom development language determines whether the interview focuses on your PHP depth or on which plugins you prefer.

Three WordPress Developer CV Mistakes That Signal a Site Builder, Not an Engineer

"WordPress" as the primary skill without custom development evidence. Adding WordPress to a skills section signals familiarity, not engineering capability. The relevant question for a WordPress developer role — particularly at a professional agency or for a senior in-house position — is whether the candidate builds custom functionality from scratch or configures existing plugins. The distinction is clear in the vocabulary: "custom post type", "custom plugin", "WordPress REST API endpoint", "Gutenberg block development with @wordpress/scripts", "WordPress hooks and filters" signal engineering; "theme customization", "plugin installation", "WooCommerce setup", "Elementor" signal configuration. Both have value in different contexts, but the vocabulary on your CV signals which category you belong to. Use the engineering vocabulary if you are an engineer.

No site performance metrics. Core Web Vitals (LCP, CLS, FID/INP) became a Google ranking factor and are now part of almost every serious client brief for WordPress projects. PageSpeed Insights scores are objectively measurable, publicly visible, and directly tied to client outcomes (search ranking, bounce rate, conversion). A WordPress developer who has improved a site's mobile PageSpeed score from 34 to 87 has a concrete, verifiable achievement that most clients and hiring managers understand immediately. Pull the before-and-after scores from your projects — they are available for free via Google PageSpeed Insights for any public site — and include them in your bullets. Even one performance win per role adds more credibility than a skills section listing five caching plugins.

Absence of Git and staging workflow evidence. Professional WordPress development is done with Git, a version control workflow that includes staging environments, and a deployment process that never involves editing files directly on the live server. The absence of Git, staging, and deployment tooling from a WordPress developer CV suggests the candidate works in the way that most non-technical site owners manage WordPress: directly editing production, downloading plugins as-needed, and hoping nothing breaks during an update. Name your Git workflow explicitly if you use one: "Git workflow with staging environment, theme and plugin development via composer, deployment via SSH or WP Engine's DeployHQ integration" is the professional signal that distinguishes you from the configurator.

If you are applying to WordPress developer or WooCommerce specialist roles and want your CV rebuilt around the specific PHP, plugin development, and performance optimization requirements in a target job description, Resumegpt generates your WordPress developer CV from your work history in under 60 seconds — custom development depth evidenced, performance wins measured, ATS-optimised, and exported as a PDF ready to submit.