A well-written WordPress developer job post is a good diagnostic. Strip the perks and the tone, and what’s left is a list of what a serious agency believes it can no longer hire around. A recent one from Blacksmith Agency is a clean example: custom PHP/WordPress builds (not page-builder assembly), senior-level client ownership, translating business goals into technical scope — and, stated as plainly as the rest, “real fluency using AI to drive efficiency.”
Three of those four requirements haven’t changed in a decade. The fourth is new enough that most developers, and most job posts, still describe it vaguely. Worth being precise about what it actually means.
Layer 1 — the craft requirement didn’t move
Custom code, not assembled blocks. Understanding hooks — actions and filters — well enough to extend core and plugin behavior without forking it. Architecture that survives a second developer joining the project: separation of concerns, dependency inversion, interfaces you can swap without rewriting callers. We’ve written about how SOLID maps onto real WordPress plugin code, because “SOLID for WordPress” isn’t an academic exercise here — it’s the difference between a plugin catalog that scales and a functions.php that doesn’t.
This requirement is actually pricier now, not cheaper. An AI agent will execute a bad architectural decision faster and at greater scale than a human would have. Judgment about what to build doesn’t get automated away by a tool that’s very good at how.
Layer 2 — ownership, not just output
“Own client relationships,” “translate business objectives into technical scope,” “scope your own work” — this is the senior layer, and it’s the one AI tooling doesn’t touch at all. A model can generate a function. It can’t sit in a discovery call and figure out which of the client’s three stated problems is the real one. This is also the layer that separates a developer from an agency’s actual bottleneck: not code output, but the judgment about what code to write and why.
Layer 3 — “AI fluency,” and the two things people mean by it
This is where most articles on this topic get vague, because “use AI” now covers two genuinely different skills.
3a. AI as a productivity tool for the developer. This is what most job posts mean, including Blacksmith’s: Claude Code, Cursor, Copilot, an agent that writes and reviews your diffs. Table stakes now, the same way a linter was table stakes five years ago. Worth naming plainly rather than gesturing at.
3b. AI as a capability the developer ships inside WordPress itself. This is a different skill, and it’s rare. It means understanding Abilities API, MCP, and Connectors well enough to register what an AI agent is allowed to do on a client’s site — not to write code faster, but to build the thing a site owner’s own agent will call. Noel Tock’s “5 Levels of Agentic WordPress” (Autocomplete → Creation → Delegation → Automation → Evolution) is a useful map of where a given project actually sits on this axis.
Most developers who list “AI fluency” mean 3a. The senior-plus tier a post like Blacksmith’s is really describing means both — using AI well, and knowing how to build AI capability into a WordPress site safely (permission-checked abilities, not raw database access handed to a model).
Self-check
A rough version of what a 2026 senior WordPress developer interview probably tests, one question per layer:
- Can you explain a hook chain (which filter fires before which action, and why it matters) without looking it up?
- Have you scoped a project directly with a client, and said no to part of it?
- Can you name what your AI coding tool got wrong on a recent task, not just what it sped up?
- Do you know the difference between an AI agent editing your code and an AI agent calling your plugin’s API at runtime?
If the fourth question is unfamiliar, that’s not a gap in a resume — it’s a gap in the market right now, which is exactly why it’s worth closing.
Where this is documented
- SOLID principles mapped to WordPress plugin architecture
- Domain-Driven Design for WordPress
- Abilities API, Connectors, and MCP for WordPress
- Agentic Engineering services
Related
- Blacksmith Agency’s WordPress developer listing (source for this piece): https://apply.blacksmith.agency/wpdev/apply
- AI Workflow Automation in WordPress (4WP.dev) — companion piece on the 3b layer in practice
