WordPress powers a substantial share of the web, and the remote job market around it is large and varied. A "WordPress Developer" ad can mean building custom Gutenberg blocks for a media company, maintaining a WooCommerce store for an e-commerce team, or developing bespoke themes for a digital agency.
Three jobs are hiding in the same keyword
The title is consistent. The actual work is not. Identifying which of the three a listing is describing saves you from applying to roles that don't match your skills or interests.
Theme and Frontend Developer — customises and builds the visual layer of WordPress sites. Primary work: Gutenberg block development, theme architecture, CSS/JavaScript, and making designs match in every browser. Stack: PHP templating + JavaScript (vanilla or React for Gutenberg) + ACF or similar custom fields plugin. Broad frontend scope, moderate PHP depth.
Plugin and Backend Developer — extends WordPress through custom plugin development and server-side logic. Primary work: custom post types, REST API endpoints, hooks and filters, database queries. Stack: PHP + WordPress core APIs + MySQL + caching layers. Narrower scope, deeper PHP and WordPress internals knowledge required.
WooCommerce / E-Commerce Developer — owns the store layer and the integrations that surround it. Primary work: WooCommerce customisation, payment gateway integration, shipping configuration, performance tuning under high load. Stack: PHP + WooCommerce APIs + JavaScript + third-party integrations. E-commerce-specific scope, breadth across the stack.
Four employer types cover most of the market
The employer type shapes the pace, the code quality expectations, and what you'll actually spend your days doing — more than the job title does.
Digital agencies. The largest single segment of the WordPress job market. You'll work across multiple client projects in parallel, meet varied requirements, and spend a lot of time in other people's codebases. Code quality standards vary widely from agency to agency. Good for building breadth quickly; less good if you want to go deep in one area.
Media and publishing companies. Large editorial organisations that run WordPress at scale — millions of page views, dozens of editors, and performance requirements that demand real engineering discipline. The work leans toward architecture, caching, and Gutenberg editor customisation. Slower pace than agencies, but more depth and usually a better engineering culture.
E-commerce businesses. WooCommerce shops that have grown beyond simple plugin configurations and need custom development to handle their business logic. Integration work is heavy here: payment providers, logistics APIs, CRM connections. Performance under load is a real concern.
Product companies with WordPress products. Plugin and theme companies selling commercial WordPress products to thousands of customers. The code has to survive across wildly varied hosting environments, browser combinations, and plugin conflicts. Quality and backward compatibility standards are usually the strictest in the ecosystem.
What the stack actually looks like
Most listings name "WordPress" and leave you to guess the rest. On a serious remote WordPress team, the expected baseline usually includes: PHP (7.4 minimum, 8.x increasingly), Composer for dependency management, a local development environment (Local, DDEV, or Docker), version control with Git, and deployment pipelines rather than FTP uploads. Gutenberg block development means React and JavaScript, which surprises candidates who came to WordPress through PHP alone. Modern WordPress work is a polyglot stack.
Six things worth checking before you apply
These questions cut through listing noise better than any keyword scan.
- Gutenberg or classic editor. These are substantially different development approaches. Gutenberg block development requires JavaScript (often React), while classic editor work is mostly PHP and templating. Listings rarely spell this out — ask during the screen.
- Custom builds or configuration work. Building custom plugins from scratch is a fundamentally different job from configuring and connecting existing plugins. The listing might use "WordPress Developer" for both. Look for phrases like "plugin development," "custom integrations," or "theme development from scratch" as signals of the actual work.
- Hosting environment expectations. Managed WordPress hosting (WP Engine, Kinsta, Pressable) versus self-managed VPS versus AWS with custom configuration means different operational expectations. Check what the team expects you to know about the infrastructure layer.
- Code review and quality standards. Some WordPress shops have rigorous pull request reviews, PHPCS linting, and test suites. Others deploy by FTP and call it done. The listing's language is a reasonable proxy — "engineering" language versus "website" language usually tracks the actual culture.
- Remote maturity. Is async communication documented and practiced, or is the team working remote because they have to? The hiring process itself is often the best signal — a well-structured async application process usually means a well-structured async working environment.
- Scope stability. Agencies will give you shifting priorities and multiple client contexts. In-house product teams will give you depth in one context with more stable scope. Know which one suits how you work best before you apply.
The bottleneck is different at every level
At the junior end, the WordPress market is large and accessible — the barrier to a deployed site is low enough that almost everyone has "built websites in WordPress" on their CV. What separates candidates who get hired from those who don't is evidence of actual engineering discipline: a GitHub repository with real code, a site that's maintained rather than just launched, or a custom plugin that solves a real problem.
At mid and senior levels, what matters is architectural judgement: knowing when to write custom code and when to configure an existing plugin, how to structure a theme for long-term maintainability, and how to diagnose and fix performance problems that go beyond "install a caching plugin." These are harder to demonstrate in a CV and come out in technical interviews and pairing sessions.
What the hiring process usually looks like
Remote WordPress hiring tends to move faster than software engineering at larger tech companies. Most processes run through these stages: (1) Application — CV and portfolio of live work or a link to public code; (2) Screen — 15–30 minute call about background and experience, often with a technical lead; (3) Technical — a take-home project (build a small custom block or plugin feature), or review of existing portfolio; (4) Final conversation — walkthrough of how you approach a real-world problem, team fit; (5) Offer — compensation, hours, timezone expectations.
Red flags and green flags
The WordPress market has a wider quality range than most other tech segments, which makes these signals worth reading carefully.
Red flags — step carefully or pass:
- "Must know page builders" as the primary technical requirement. Elementor and similar tools are configuration work, not development — listings that lead with this are rarely engineering roles.
- No version control mentioned anywhere in the listing or the team description.
- "Self-hosted email" and "FTP access provided" in the infrastructure section.
- A large required plugin list with no mention of any custom development — likely a site administration role mislabelled as development.
Green flags — strong signal of a legitimate engineering role:
- Specific mention of PHP version, Composer, Docker, or a CI/CD pipeline.
- Reference to custom plugin or theme development from scratch, with code examples requested.
- A public GitHub or Bitbucket repository mentioned for the team's work.
- Engineering blog, documented development standards, or a clear code review process.
Gateway to current listings
RemNavi doesn't post jobs. We pull them in from public sources and link straight through to the employer's own listing, so you always apply at the source — no middle layer, no repost.
Frequently asked questions
Do I need to know PHP well, or is JavaScript enough now? Both, increasingly. Classic WordPress development is PHP-heavy, and you still need solid PHP for plugin and theme development. But Gutenberg block development is JavaScript and React. Senior remote roles in the ecosystem expect proficiency in both. "WordPress Developer who only knows JavaScript" or "WordPress Developer who only knows PHP" both have narrower job markets than someone who's comfortable in both.
Is WordPress considered a legitimate engineering discipline, or is it a second-tier market? There's a real range. Large-scale WordPress engineering at media companies or major plugin product companies involves hard problems — performance under load, multi-site architecture, plugin compatibility at scale. Agency WordPress work is more configuration and customisation. The work you'll find at the top end of the market is genuine software engineering. The bottom end is website maintenance. Apply accordingly.
How much of WooCommerce should I know for a general WordPress role? Unless the listing specifically mentions e-commerce or WooCommerce, assume you don't need it. WooCommerce is its own substantial ecosystem — knowing it deeply is valuable for roles that are explicitly store-focused, but it's not a requirement for theme development, plugin development, or editorial WordPress work.
What's the salary ceiling for remote WordPress roles? Lower overall than the broader software engineering market, but with real variation at the top end. Staff-level roles at plugin product companies or WordPress VIP-level agencies can reach strong engineering salaries. Mid-level agency WordPress work pays considerably less. The gap between "WordPress website work" and "WordPress platform engineering" is large and mostly undiscussed in listings.
RemNavi pulls listings from company career pages and a handful of remote job boards, then sends you straight to the employer to apply. We don't host the listings ourselves, and we don't stand between you and the hiring team.
Related resources
- Remote PHP Developer Jobs — PHP is the core language under all WordPress development
- Remote Frontend Developer Jobs — Gutenberg and theme work are frontend engineering
- Remote Fullstack Developer Jobs — Roles spanning PHP backend and JavaScript frontend
- Remote SEO Specialist Jobs — WordPress and SEO often sit in the same job brief
- Remote Backend Developer Jobs — Plugin and integration work has heavy backend overlap