We track WordPress developer job postings daily — not to republish them, but to dissect them. Every listing that comes in gets broken down into skills, requirements, and the real signal buried under recruiter boilerplate. Here’s what a live read of current postings shows.
What the Data Shows
Across the WordPress developer roles currently open, a clear pattern already stands out:
- Roughly 1 in 6 postings (about 16%) explicitly frame the role as Full-Stack — not “WordPress developer” alone.
- Nearly a quarter of open roles (about 23%) target Senior-level candidates specifically; entry-level WordPress-only postings are shrinking.
- AI-assisted or AI-driven workflow is now a named requirement in roughly 1 in 15 postings (~7%) — and rising. A year ago this line barely existed.
- React/Next.js is named directly alongside WordPress in a growing share of full-stack listings — WordPress is no longer being hired as a standalone skill.
None of this is guesswork — it’s pulled directly from live postings we monitor and re-analyze continuously.
The Baseline Is Moving
“WordPress developer” used to mean theme edits and a plugin or two. That baseline has moved. FSE (Full Site Editing), custom post types, the REST API, and hook-based architecture aren’t advanced topics anymore — they’re the entry price. Companies increasingly assume architectural literacy, not just PHP syntax.
Stack Convergence: Front + Back in One Hire
The market is stepping away from hiring “just a backend WordPress dev” or “just a Gutenberg frontend dev.” Increasingly, one hire is expected to move across both: PHP/WP core on one side, React/Gutenberg block development on the other. Employers are consolidating what used to be two roles into one job description — and one salary line.
The AI Engineering Shift
The newest and fastest-growing signal in the data: AI is no longer a bonus skill, it’s becoming a workflow requirement. Postings increasingly name AI-assisted development, AI-driven ticket handling, or MCP/agent-based tooling as part of the day-to-day — not as an experiment, but as how the work gets done.
For Candidates: What to Actually Prepare
- Stop treating WordPress and “modern stack” as separate tracks — pair them.
- Get fluent in FSE, block development, and the REST API — not as extras, but as baseline.
- Get hands-on with at least one AI-assisted dev workflow before it’s asked for in an interview, not after.
- If you’re targeting Senior roles, expect architecture-level questions, not just code trivia.
For Companies: What a Real Candidate Profile Looks Like
- Define whether you actually need full-stack coverage — don’t bury it in a “WordPress developer” title and expect one skillset to cover two roles’ worth of work.
- If AI-assisted workflow is part of your team’s process, say so explicitly — vague listings attract vague candidates.
- Match seniority language to actual scope. A “Senior” title with junior-level scope is why postings sit unanswered.
This Is a Living Dataset
We update this analysis as new postings come in — this isn’t a one-time snapshot, it’s an ongoing read of where the WordPress developer market is actually heading. Follow along as the picture sharpens.