Senior WordPress developer with AI: what agencies require in 2026

In late September 2026 Blacksmith Agency, a remote US WordPress agency, posted a Senior WordPress Developer role with AI in the workflow, and the post was still circulating on job boards in mid-October. The same agency had advertised an AI Engineer role for agentic workflows. An agency that calls itself AI-first still wants a senior who writes and reviews code. That position pushes out two extremes: teams that boycott agents, and teams that sell “vibe coding” without code review. A seat or nearshore offer outside that hybrid loses at kickoff or on the first security audit.

This opinion rests on one company’s postings, so read it as a signal, not a statistic. The WordPress.org Jobs board in mid-October listed four postings dated 5-13 October (freelance client sites, plugin integrations, a WooCommerce store, a fractional technical lead), none with AI in the title.

Looking for a nearshore partner with the AI + code review hybrid, not a junior with Cursor on production? Describe the project via contact: scope (new site, shop, MCP, blocks), locales, deadline. You compare ownership to a real job post, not a slide that says “we use AI”.

#What Senior WordPress with AI job posts require

The Senior WordPress Developer posting (27 September) and its WordPress Development Lead variant (30 September) ask for:

• a senior, client-facing lead for custom WordPress builds,
• remote work from the US, Canada, Latin America or South Africa, for clients across the US,
• excellent English,
• scope: themes, templates, plugins and blocks,
• “Drive efficiency with AI across the development process” alongside “You still write and review real code”.

Separately, the same agency advertised an AI Engineer role: agentic workflows on LangChain or LangGraph, Anthropic and OpenAI APIs with tool use, WordPress or PHP experience as a bonus.

The pattern: a lead developer who uses agents, plus a person or Automation path that wires production workflows. A “prompt magician” alone does not close the JD.

#WordPress.com Agent, MCP write and developer hiring

On 15 October WordPress.com updated its Agent: generating a site takes less than half the time it used to, and the Agent installs, activates and updates plugins from chat. MCP write tools have been on paid plans since March 2026. The easy win (draft in minutes, save from Cursor) is now visible to the client. The hard win (SLA, plugin whitelist, publish gate) still needs a human. Job ads are the market translation of the same claim we unpack in Agent and MCP write.

When a client sees an Agent demo, they ask: “why do you need a senior?” The posting answers in advance: the senior is there so the Agent does not push three plugins outside the whitelist and an untested checkout to production.

#Senior WordPress with AI in PL and EU nearshore

#Kickoff pricing vs ownership for WordPress AI

Generating a theme in minutes on .com does not remove ERP, HPOS, or multilingual SEO. In the offer, split:

• discovery + first variant package (can be cheaper / shorter),
• ownership package (architecture, review, publish, monitoring).

Clients who buy only the first package come back with “why doesn’t the shop talk to the warehouse”. Better to name the boundary at the start.

#WordPress developer CV: AI tools and code review

In internal hiring:

• require an example: a PR where an agent scaffolded and a human refactored,
• require a gate description: what the agent may do without approve,
• reject portfolios of “I generated 40 pages over the weekend” without tests and without ownership.

In external hiring (client choosing an agency): the same questions work as due diligence.

#Publish gate instead of a “we use AI” slide

One sentence on the discovery call:

The agent writes a draft on staging. A human reviews. Publish is a separate step.

That filters clients who want to “push from chat to production”. Better to lose that lead than to inherit an incident.

#Questions for a Senior WordPress with AI candidate

• Which steps may the agent run without approve?
• What does review of an agent-generated block PR look like?
• Do you have a plugin whitelist for Agent / MCP write?
• Where does the WordPress.com Agent stop and custom self-hosted begin?
• Who is on-call when an agent breaks a Friday deploy?
• How do you measure that AI shortens time (metrics), not only “it feels faster”?

Sensible metrics: time from brief to first draft, plugins outside the whitelist, time from draft to publish, rollbacks after agent changes. Without metrics, “AI in the process” is a slogan.

#WordPress engineer vs AI engineer

The postings split Senior WordPress Developer and AI Engineer. In a small nearshore shop you often merge them in one person. Risk: automation without PHP depth, or PHP without agent discipline.

A model that works at 4-8 people:

• WordPress lead: architecture, review, WooCommerce, blocks,
• mid with AI: scaffold, tests, docs, MCP wiring under supervision,
• content / SEO: Guidelines, drafts, publish queue (not “full MCP access”).

When someone promises the client “one junior with Cursor will do enterprise”, the Blacksmith posting is counter-evidence: an agency that calls itself AI-first still hires a senior who writes and reviews code.

#Senior WordPress developers, Gutenberg 24.2 and React 19

In parallel, Gutenberg 24.2 turns the React 19 experiment on by default in the plugin, unless a theme or plugin with known compatibility issues is active. The senior that posting seeks must be able to test blocks on staging, not only “click a landing together with the Agent”. Detail: Gutenberg 24.2.

The AI + code hybrid also covers editor compatibility. A prompt will not catch a React peerDependency. A staging test will.

#How to talk about WordPress AI with a PL client

The Polish B2B market mixes hard:

• an expectation of “do it like WordPress.com Agent, but with Subiekt”,
• GDPR and logging requirements,
• budgets closer to mid-market than US enterprise.

An answer that matches the claim:

1. Yes, we use agents for drafts and scaffold.
2. No, the Agent does not sign the SLA or wire the warehouse.
3. Publish and integrations sit in engineer ownership.
4. Pricing is individual after scope; we do not sell “unlimited Agent sessions” without a cap.

CMS Conf in Gdynia (November 2026) and local WordCamps are good places to show that hybrid with cases, not a job post copied from a US agency.

#Mistakes in WordPress + AI job posts

• Do not write “AI-first” without a list of tools and gates.
• Do not require “5 years of LangChain” for a role that is 80% PHP and blocks.
• Do not promise the client that junior + Cursor = lead.
• Do not hide that MCP write defaults to drafts: that is a feature, not a shame.

#Senior WordPress with AI hiring interview

Instead of “do you use AI?” (the answer is always yes), run a case:

1. Give the candidate a short landing brief + a whitelist of three plugins.
2. Ask for a plan: what the agent does, what the human does, where publish sits.
3. Ask for review of a deliberately weak PR (generated code with an obvious nonce or escaping hole).
4. Ask for a decision: WordPress.com Agent vs self-hosted for a warehouse integration.

A candidate who cannot name the publish gate fails regardless of how many LLM models they list. A candidate who can, and speaks weakly about LangChain, can still fit Lead WordPress with AI: AI Engineer is a separate path.

#Onboarding a junior WordPress developer with AI agents

A junior with Cursor can generate a block in an hour. Onboarding must teach three things before they get MCP write on client staging:

1. escaping, nonce, capabilities - no exceptions “because the agent wrote it”,
2. reading the diff line by line before merge,
3. when to say “the agent should not do this” (secrets, production, DB migration).

Without that, the junior becomes an error amplifier. With it, the junior becomes a cheaper lead in 18-24 months.

#Due diligence for a WordPress agency with AI (enterprise)

When you pick a WordPress vendor after the Agent / MCP wave:

• ask for a diagram of the path from agent to staging, review and production,
• ask for an example revert after a bad agent change,
• check whether the contract covers ownership of code and logs, not only “license to the effect”,
• ask about Gutenberg / React tests (see 24.2), not only “we know ChatGPT”,
• avoid pricing “unlimited Agent fixes” without a sprint cap.

Enterprise does not buy prompts. It buys incident predictability. The hybrid in that posting answers that requirement.

#AI theater in a WordPress agency: how to avoid it

AI theater: a slide about models, zero metrics, a junior with Cursor on production, the lead busy putting out fires. Symptoms:

• no plugin whitelist,
• MCP write with publish rights for everyone,
• no review of PRs with agent diffs,
• bonuses for “pages generated”, not for absence of incidents.

Treatment:

• metrics from the Agent / MCP article (time from brief to draft, whitelist, time from draft to publish),
• one publish owner per project,
• retrospective after every agent incident (5 Whys, not “blame the model”).

The Blacksmith posting describes the opposite of AI theater. If your agency hires to that kind of job post while the process looks like theater, senior candidates leave during probation.

#Skills for a Senior WordPress developer with AI

Technical minimum (without this, soft skills do not matter):

• PHP 8.x, WP hooks, conscious WP_Query / SQL,
• blocks (edit.js, save / dynamic render),
• React basics in the editor + awareness of the React 19 track (Gutenberg 24.2),
• WooCommerce at the level of debugging checkout and HPOS (“I know where to look”),
• Git, CI, staging, rollback.

AI / agent minimum:

• Cursor / Claude / ChatGPT as tools, not as source of truth,
• ability to describe the publish gate,
• MCP: what it is, where write is dangerous,
• ability to reject model output (code review).

Nice-to-have (separate Automation path):

• LangChain / own orchestration,
• agent evals, not only a happy-path demo,
• integrations beyond WordPress (CRM, ERP) with queues and retry.

Hiring that mixes nice-to-have with the minimum either overpays or hires someone who will not deliver PHP in a crisis.

#Retaining a Senior WordPress developer with AI

Seniors leave when:

• marketing sells “AI will do everything” while they put out fires,
• there is no budget for staging and tests,
• juniors have MCP write on prod “because it is faster”.

Keep them by:

• clear ownership (they decide the publish gate),
• time for Gutenberg / React tests in the retainer,
• metrics that show leadership the value of review, not only draft speed.

That is the same thing an enterprise client wants. Senior retention and client satisfaction share a mechanism: ownership.

#Should you give an AI discount on WordPress pricing

Clients will start asking for a discount “because AI does half the work”. An answer that matches the claim:

• discount scaffold time and the first mockup if it truly fell,
• do not discount ownership, review, security, or on-call,
• write into the contract which phases are AI-accelerated and which are human-gated.

Agencies that give a global “AI discount 30%” on the whole project subsidize someone else’s risk. Agencies that show a phase split match the posting described above: modern and responsible.

On the WPPoland pricing page, market-range rules apply; this article does not quote offer rates. The point is conversation structure, not a number.

#Remote South Africa vs EU nearshore for WordPress AI

A US agency’s remote seat open to South Africa and Latin America describes the same hybrid, but a different cost and legal context. PL/DE/NB nearshore sells:

• a time zone close to DACH and Nordics clients,
• GDPR / local compliance as default,
• shorter latency to on-site workshops.

You do not win against South Africa on prompt price. You win on ownership and local context. In the pitch, repeat the hybrid from the JD, not “we are cheaper because AI”.

#AI and the invisible 80% of a WordPress project

On 6 October WebDevStudios wrote that AI is very good at the 20% of a website you can see and does not ship the 80% you cannot: what gets a site found, keeps it secure and protects visitor data. That complements the posting: the senior owns that 80%. Agent and Cursor accelerate the 20% and the scaffold. Anyone who sells only the 20% gets a ticket Friday at 16:58. Anyone who hires for the hybrid has someone to close that ticket.

#90-day scorecard for Senior WordPress with AI

So the hybrid seat does not stay a slogan:

If after 90 days there are no metrics and no gate, you hired a title, not a competence. The scorecard is also a client conversation tool: “this is how we onboard the person that job post describes”.

#WordPress agency career page for AI roles

Instead of vague “we love WordPress and innovation”:

• list the agent stack and the gates,
• show an example diff with review,
• say plainly that publish is human,
• separate the Engineer path from Automation.

Senior candidates read the career page as due diligence. Board JDs and your page must speak in the same voice. If the board says “real code” and the career page says only “AI-powered digital experiences”, the senior assumes AI theater and does not apply.

#Agency owner checklist: WordPress + AI

• Internal JDs require the hybrid (AI + review), not only one pole
• Junior onboarding covers escaping and diff before MCP write
• Agent metrics sit in the client report
• Retainer has time for editor / React tests
• Nearshore pitch sells EU ownership, not “cheaper prompt”
• Career page = same voice as your job posts

The claim from the first paragraph returns here as an operations list. Without the checklist, you are left with an opinion.

#Answering “why a senior if Agent exists”

Client: “If there is an Agent, why pay for a senior?”

Answer that matches the claim:

1. The Agent shortens time to the first UI variant and content drafts.
2. The senior sets the plugin whitelist, publish gate, and tests (including Gutenberg / React).
3. The senior owns integrations and incidents; the Agent does not take on-call.
4. You pay for risk predictability, not for generation minutes.

If after that script the client still wants only the Agent without ownership, that is a lead to decline or a Phase A with an explicit exit criterion (see the Agent / MCP article). Better to lose the project than to gain production without review.

#How to commission a project if you are not hiring a seat

Not every company needs a Senior WordPress on payroll. Some need a partner with the same JD in practice: Agent and MCP for drafts, a human for the publish gate and integrations.

Ask for a quote when:

• you have a brief and fear “the Agent will do everything” at a competitor,
• you need a WordPress developer with review, not only content ops,
• MCP / AI integration on self-hosted is in scope,
• you want a 90-day scorecard like the section above, but on the agency side.

In the inquiry: business goal, stack, whether WooCommerce is involved, how many locales, whether staging exists. Pricing is individual after scope (pricing page as market context, binding offer after the scope is set).

#Senior WordPress with AI: hybrid seat, not replacing code

The October 2026 signal: hire people who use agents and keep code ownership with a human. The same pattern shows in that job post, in Automattic products (Agent, MCP write), and in the Gutenberg track (React 19 in the plugin).

When you pick a partner and when you build a nearshore team, the filter is shared: boycotting AI and believing the Agent replaces architecture both fail.

Inquiry about delivery or an audit of the AI process in a WordPress project: contact.