PHP powers nearly 80% of the web, which means the job market is huge but fragmented. Remote PHP roles range from high-paying greenfield work in Laravel to steady maintenance gigs on legacy WordPress installs. The market rewards people who can either ship modern PHP or navigate old codebases with grace.
Three jobs are hiding in the same keyword
PHP work splits along the framework and philosophy axis more than most languages.
Laravel product engineer. Building modern web applications with Laravel—clean architecture, testing, database design, shipping features to production. Day to day: Laravel conventions, Eloquent ORM, queues, API design, migrations. The aspiration tier of PHP work, fast-moving, and usually best-paid.
WordPress-agency engineer. Building custom WordPress sites and plugins for clients or internal products—PHP for WordPress, custom post types, plugin development, Elementor or ACF, client relationships. Day to day: Plugins, customization, debugging WordPress quirks, client deadlines. Highest volume of jobs, variable quality, lower pay on average.
Legacy PHP modernization engineer. Maintaining and refactoring older PHP codebases—pre-framework code, custom OOP patterns, upgrading to modern PHP, gradual migration to Laravel or Symfony. Day to day: Debugging legacy code, writing tests for untested systems, incremental refactoring, risk management. Challenging, often well-paid, requires patience.
Four employer types cover most of the market
Modern SaaS and tech companies on Laravel. Startups and growth-stage companies using Laravel as the core platform. Strong engineering culture, fast shipping, competitive pay. Interviews are usually rigorous around architecture and testing.
WordPress hosting and managed services. WP Engine, Kinsta, Pagely, and similar platforms. Steady work, focus on reliability and scaling, good pay. Less emphasis on trend-chasing, more on fundamentals.
Design agencies and web studios. Thousands of agencies building websites and custom systems for clients using PHP and WordPress. Work is project-based, client-driven, sometimes chaotic. Pay varies widely based on agency quality.
Enterprise companies with legacy PHP systems. Established organizations with large PHP codebases, often built years ago. Steady work, good pay, less churn, higher emphasis on stability and regulation.
What the stack actually looks like
Modern PHP: Laravel with Eloquent, database migrations, queues (Redis or database-backed), testing (PHPUnit, Pest), caching strategy. WordPress: PHP with WordPress APIs, plugins, potentially ACF or Elementor, database design around post types. Legacy: heterogeneous—anything from custom OOP patterns to procedural code with no framework.
The floor is PHP 8.0+, though many shops are still on 7.x. Composer for dependency management. MySQL or PostgreSQL for data. Git and code review. Testing ranges from rigorous (modern shops) to nonexistent (many WordPress projects). Deployment varies—some use Heroku or platforms built for PHP, others raw servers or managed hosting.
Six things worth checking before you apply
Whether they're on modern PHP and what that migration looks like. PHP 7.4 and earlier are increasingly outdated. Shops that have upgraded to PHP 8+ usually have better engineering culture. If they're planning a migration, ask about the timeline.
If it's a Laravel shop, which version and how they handle upgrades. Laravel moves fast. Teams on 8.x are carrying technical debt against the current version. Ask how often they upgrade and whether they maintain long-term support versions.
How they test and whether testing is an afterthought or a practice. Modern Laravel shops do TDD or at least ship tested code. WordPress projects often don't. If testing isn't mentioned and you care about it, this is a red flag.
Whether it's a greenfield or legacy system, and how honest they are about it. Greenfield means speed and clean code. Legacy means careful change management and incremental improvement. Neither is bad, but they require different mindsets. Bad listings hide what they actually have.
Who the senior engineer or tech lead is and what they've shipped. PHP's reputation took a hit because of massive amounts of low-quality code. Teams led by someone with taste and experience are different. Look for evidence of that.
How they handle database migrations and schema changes. This is where a lot of PHP projects go wrong. Good teams have a clear process. Teams where "someone" runs migrations manually on production are red flags.
The bottleneck is different at every level
Junior PHP roles are abundant, but many are WordPress agency work or poorly-scoped projects. If you're coming in junior, you need evidence of shipped work—a public Laravel project, contributions to WordPress plugins, or a detailed case study showing debugging and design thinking. WordPress experience is valuable but doesn't transfer as cleanly to modern PHP as you'd hope.
Mid-level is where remote PHP work opens up genuinely. You understand the framework (Laravel or WordPress) deeply, you know when to reach for packages versus building it yourself, and you can review code and mentor others. Remote hiring at mid-level is straightforward—the work is stable and the communication patterns are clear.
Senior roles in PHP often go to people who've led teams through major refactors, who've shipped products with scale problems, or who've built systems that serve millions. Laravel shops pay senior engineers well; WordPress is less common at the senior level because career growth there plateaus.
What the hiring process usually looks like
PHP interviews follow a typical pattern: (1) application — resume with specific framework experience; (2) phone screen — 20-30 minutes, context on the project and basic technical questions; (3) coding task — a take-home building a feature, or live coding in an IDE, usually 2-3 hours; (4) final interview — architecture discussion, code review of the task, sometimes system design; (5) offer.
WordPress shops sometimes skip formal testing if your portfolio speaks for itself. Laravel shops are usually more rigorous. Agencies might ask you to build something closer to a real client project.
Red flags and green flags
Red flags — step carefully or pass:
- Listings that don't specify Laravel or WordPress—could be anything, usually older framework or custom code.
- "PHP and JavaScript required" heavily weighted toward JavaScript—suggests they're trying to backfill a full JavaScript role with PHP.
- No mention of testing or code review in the listing—suggests those practices don't exist.
- Take-homes that ask you to build a full working site in 3 hours—tests speed, not judgment.
- Vague description of the codebase or "legacy system we inherited" without detail—suggests deep problems.
Green flags — strong signal of a healthy team:
- Laravel version specified and a clear upgrade path—"on 10, planning 11 this quarter."
- Named tech lead or senior engineer with public Laravel work, talks, or open-source projects.
- Clear description of the stack and architecture—not just "we use PHP" but "Laravel + Eloquent + PostgreSQL + Redis."
- Explicit mention of testing practices or code review standards.
- Transparent compensation that reflects the difference between legacy and modern work.
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.
Frequently asked questions
Is PHP still worth learning in 2026? Yes. The market is massive, the pay is competitive, and the platform is actively improving. Modern PHP (7.4+) is a genuinely solid language. The reputation damage came from years of low-quality code, but that's not PHP's fault. If you're learning backend, PHP opens more doors than almost anything else.
What's the difference between Laravel and WordPress? Laravel is a framework for building applications from scratch. WordPress is a CMS with PHP as the implementation language. They're different categories of work. Laravel is architecture and design; WordPress is often customization and content management. Both have real jobs and real skills.
Do I need to know WordPress to be a PHP developer? No. You can have a strong career in PHP without ever touching WordPress. That said, WordPress skills are marketable and highly valued in the agency world. The reverse isn't true—WordPress experience doesn't automatically make you a good Laravel engineer.
How much DevOps or server management do I need? It depends on the shop. Modern shops with managed hosting or Heroku abstract all of this away. Shops hosting on raw servers or managing their own infrastructure need more from engineers. Ask during the screen.
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 Backend Developer Jobs — Broader category that includes PHP and other frameworks
- Remote Fullstack Developer Jobs — PHP roles that extend to frontend
- Remote Node.js Developer Jobs — JavaScript alternative in the same space
- Remote DevOps Engineer Jobs — Infrastructure collaborators for PHP teams
- Remote Technical Writer Jobs — Often paired with PHP documentation work