Was this sample helpful? Rate it!
Average: 4.6 (14 votes)
Contents
Key Takeaways for a PHP Developer Resume
What This Resume Gets Right
How to Write a PHP Developer Resume
Key Sections for a PHP Developer Resume
PHP Developer Resume Summary Examples
PHP Developer Work Experience Examples
Top PHP Developer Skills
PHP Developer Certifications
Common PHP Developer Resume Mistakes
PHP Developer Resume FAQs
Summary
PHP developer with eight years building web applications and back-ends with PHP and Laravel for agencies and product companies in Amman. Builds the server side that powers websites and platforms — designing APIs and database-driven applications, integrating payments and third-party services, and keeping code clean, secure and fast as products grow. Rebuilt a slow legacy application into a modern Laravel platform and built an API used by multiple front-ends. Develops PHP and Laravel applications and APIs, designs and queries databases, integrates services, writes tested code, and ships and maintains web platforms. Pragmatic, solid and security-aware. Looking for a senior PHP-developer or backend role with a company building web products that have to be reliable and maintainable.
Work Experience
PHP Developer
Amman Web Solutions, Amman, Jordan
Jan 2019 – Present
- Build the server side that powers websites and platforms, keeping code clean, secure and fast as products grow.
- Rebuilt a slow legacy application into a modern Laravel platform and built an API used by multiple front-ends.
- Develop PHP and Laravel applications and APIs, turning requirements into reliable, maintainable back-ends.
- Design and query databases efficiently, keeping data correct and fast even as tables and traffic grow.
- Integrate payments and third-party services, connecting applications cleanly to the tools businesses depend on.
- Write tested code and review others', keeping the codebase healthy and secure as features keep being added.
Junior PHP Developer
Jordan Software House, Amman, Jordan
Feb 2017 – Dec 2018
- Built web application features in PHP under senior developers, learning professional development hands-on.
- Wrote code and fixed bugs across applications, building PHP and database skills over time.
- Learned PHP, Laravel and database design on the job across nearly two years.
- Gained the certification and experience that led into a full PHP-developer role of my own.
Education
BSc in Computer Science, Computer Science
University of Jordan
Sep 2012 – Jun 2016
- Degree in computer science covering web development, databases, algorithms and software engineering, with projects. The programme built the technical foundation professional web development requires. It led directly into PHP development.
Laravel & Web Security Certification, Web Development
Online Developer Academy
Aug 2016 – Jan 2017
- Certification in Laravel development and web application security to a recognised standard. It deepened the framework and security toolkit. It supported building modern, secure, maintainable PHP applications.
Certifications
Laravel & Web Security Certification
Online Developer Academy
Jan 2017 – Present
- Certification in Laravel development and web application security to a recognised standard, which deepened the framework and security toolkit and supports building modern, secure, maintainable PHP applications.
Highlights
Rebuilt a legacy app
- Rebuilt a slow, fragile legacy application into a modern Laravel platform. Replacing aging code with a clean, maintainable system improves performance, security and how easily the product can grow for years to come.
Built a shared API
- Built an API now used by multiple front-end applications. A well-designed shared API lets many apps draw on the same reliable back-end, so building one cleanly multiplies its value across the whole product.
Platform Rebuild
Legacy-to-Laravel Rebuild
Jan 2021 – Sep 2021
- Led the rebuild of a slow legacy web application into a modern Laravel platform with a clean API, which improved performance and security and let multiple front-end applications share one reliable, maintainable back-end.
Languages
- Arabic — Native or Bilingual Proficiency
- English (UK) — Full Professional Proficiency
Technical Skills
- PHP
- Laravel
- API Development
- MySQL & Databases
- Web Security
- Third-Party Integration
- Testing
- Performance Optimisation
- Git & CI/CD
- Clean Code
Personal Skills
- Problem Solving
- Pragmatism
- Security Awareness
- Reliability
- Collaboration
Activities & Interests
- Badminton
- Drinking
- Travelling
- Ski
- Gymnastic
Key Takeaways for a PHP Developer Resume
Before the detail, here is what separates a PHP resume that gets a callback from one that gets filtered:
- Name your PHP version. "PHP 8.2" reads as a modern developer; an unversioned "PHP" reads as someone who may still be maintaining PHP 5.6 procedural code.
- Framework first, language second. Laravel and Symfony are what recruiters search for, so put the framework and the version in your skills line before anything else.
- Legacy modernisation is a selling point, not an embarrassment. Version upgrades, Rector runs and rewriting raw queries as parameter-bound code are highly employable skills.
- Show database competence explicitly. MySQL indexing, Eloquent N+1 fixes and query counts per page request are the difference between a PHP developer and a template editor.
- Say something about security. SQL injection, CSRF, XSS and how you handled them is expected on the web tier and quietly missing from most PHP resumes.
- Be honest about WordPress and Magento. Naming them helps for CMS and e-commerce roles and hurts for product engineering roles, so tailor which one is visible.
What This Resume Gets Right
The sample belongs to a PHP developer with eight years across agency and product work in Amman. The choices worth copying are structural:
- The summary names the framework early and pairs it with a business outcome rather than a feature list, so a reader knows the specialism inside the first line.
- A legacy rebuild is used as the headline achievement, which is smart because rescuing a slow, fragile application is the work most PHP employers are actually hiring for.
- The shared API is described by how many front-ends consume it, which turns an ordinary integration task into evidence of interface design judgement.
- Security sits in both the skills block and the personal profile, unusual on a PHP resume and immediately reassuring to anyone who has inherited an injectable codebase.
- The junior role is written as a progression story with a duration attached, so the jump to a full developer title is explained instead of asserted.
- The technical skills list stays at ten focused entries, which keeps the framework and database keywords prominent instead of drowning them in library names.
Extra tips
PHP employers rarely hire for greenfield work; most are looking for someone to modernise an application that already earns money.
One bullet quantifying a legacy rescue, such as query counts before and after, outperforms three describing new features.
How to Write a PHP Developer Resume
PHP hiring is unusually varied, spanning agencies, CMS shops and product engineering teams. These five moves work across all of them:
How do you signal that you write modern PHP?
Version numbers and tooling do it faster than prose. "PHP 8.2, typed properties, enums, PHPStan level 6, PSR-12" tells a reviewer in one line that you are not writing 2013-era code. If you led an upgrade, say so: "migrated 90,000 lines from PHP 7.4 to 8.2 with Rector" is one of the strongest bullets available to a PHP developer.
Which framework details should go on the resume?
Name the framework, the version and the parts you used in anger. "Laravel 10: queues with Horizon, Sanctum authentication, policies, custom Artisan commands" is far more useful than "Laravel". Symfony developers should do the same with bundles, Doctrine and the Messenger component.
What numbers make a PHP bullet convincing?
Queries per page request, response time in milliseconds, traffic, catalogue or record counts, and test coverage. "Cut the admin dashboard from 312 queries to 9 by adding eager loading" is the kind of line a technical reviewer stops on, because it shows you profiled rather than guessed.
Should you mention WordPress or Magento?
Only when the target role wants it. For an agency or e-commerce job, WooCommerce and Magento experience is a direct match and should be prominent. For a Laravel product team, heavy CMS emphasis can read as theme work rather than application engineering, so keep it to one line.
How do you show security awareness without sounding vague?
Attach it to something you fixed. "Replaced 240 raw SQL queries with parameter-bound Eloquent, closing every injection finding in the annual penetration test" beats the word "security" sitting alone in a skills list. Mention OWASP categories only if you can discuss them properly in interview.
Key Sections for a PHP Developer Resume
A PHP resume carries a slightly different load to other backend roles, because the hiring manager needs to place you on the spectrum from CMS work to application engineering:
A skills block ordered framework, language version, database, then tooling: Laravel, PHP 8.2, MySQL, Composer, PHPUnit, Git, Docker.
The deployment story. Whether you shipped via Deployer, Envoyer, GitHub Actions or manual FTP tells a reviewer a great deal about the engineering culture you come from.
One line naming the traffic or scale of the applications you maintained, since PHP work ranges from brochure sites to platforms serving millions of requests.
Integrations you own end to end, especially payments. Stripe or PayPal with webhook handling and idempotency is a concrete, checkable specialism.
A projects or highlights block for a legacy rescue or a platform rebuild, which is the highest-signal work a PHP developer can show.
Testing evidence. PHPUnit or Pest with a coverage figure separates you from the large share of PHP applicants who have never written a test.
PHP Developer Resume Summary Examples
Three summaries at different stages, each pronoun-free and each pointing at a different slice of PHP work than the sample above:
Entry-level resume summary example
PHP developer with two years building Laravel applications on a small product team, working across controllers, Eloquent models, Blade views and queued jobs in a PHP 8.2 codebase. Shipped a customer billing module covering invoices, refunds and proration, backed by 180 Pest tests and validated end to end against Stripe webhooks in a sandbox environment. Cut a slow admin dashboard from 312 database queries to 9 by adding eager loading after profiling with Laravel Debugbar, taking page render from 4 seconds to under half a second. Follows PSR-12, keeps Composer dependencies current, and treats prepared statements and CSRF tokens as engineering rather than framework magic. Looking for a team that reviews code properly and releases often.
Mid-level resume summary example
PHP developer with six years building and maintaining Laravel and Symfony applications for e-commerce and SaaS products, comfortable owning a feature from schema design through to deployment. Rebuilt a PHP 5.6 order module as a Laravel service, replacing 240 raw queries with parameter-bound Eloquent code and closing every injection finding raised in the annual penetration test. Moved invoice generation, bulk email and CSV exports onto Redis-backed queues with Horizon, taking median checkout response from 2.4 seconds to 380 milliseconds. Handles the unglamorous work well: version upgrades with Rector and PHPStan, MySQL index tuning, and zero-downtime deploys. Seeking a senior backend role on a product with real traffic and a codebase worth maintaining.
Senior-level resume summary example
Senior PHP developer with ten years leading backend work on high-traffic Laravel and Symfony platforms, including a marketplace serving 60,000 monthly active users across web and mobile clients. Designed the versioned REST API and Sanctum authentication layer consumed by a Vue application, a React Native client and two partner integrations, with no breaking change shipped in three years. Led a 90,000-line upgrade from PHP 7.4 to 8.2 using Rector and PHPStan at level 6, clearing deprecations ahead of the end-of-life date and gaining a measurable OPcache improvement. Sets code standards across nine repositories, chairs architecture review and mentors four developers. Wants a lead or principal backend role where security, performance and maintainability are budgeted for rather than bolted on.
PHP Developer Work Experience Examples
Three sets covering the routes most PHP careers actually take. Borrow the shape, then replace the numbers with yours:
Mid-level PHP developer, Laravel product team
- Rebuilt a legacy PHP 5.6 order module as a Laravel 10 service, moving 240 raw SQL queries onto parameter-bound Eloquent and closing every injection finding raised in the annual penetration test.
- Moved 18 synchronous jobs including invoice PDFs and bulk email onto Redis-backed Laravel queues with Horizon, cutting median checkout response time from 2.4 seconds to 380 milliseconds at peak.
- Fixed N+1 loading across the customer dashboard using eager loading and query logging, taking a single page from 312 database queries down to 9 and dropping primary MySQL CPU by roughly a third.
- Wrote 420 PHPUnit and Pest tests covering billing, refunds and tax rules, moving the module from no coverage to 81 percent and making quarterly pricing changes safe to release on a Friday.
- Upgraded a 90,000-line codebase from PHP 7.4 to PHP 8.2 using Rector and PHPStan level 6, clearing 1,100 deprecations before the end-of-life date and gaining a measurable OPcache improvement.
Senior PHP developer, agency and multi-client platforms
- Designed a Sanctum-authenticated REST API consumed by a Vue web app, a React Native client and two partner integrations, versioning it so 60,000 monthly users saw no breaking change in three years.
- Integrated Stripe payments with webhook signature verification, idempotency keys and a nightly reconciliation job, ending the duplicate-charge tickets that had been costing support hours every week.
- Set PSR-12 and a shared Composer package standard across nine client codebases, adding Laravel Pint and PHPStan to CI so style and static-analysis arguments stopped landing in code review at all.
- Migrated a WooCommerce store carrying 42,000 products onto a headless Laravel back-end, holding order throughput steady through cutover weekend and improving catalogue load from 3.1 to 0.9 seconds.
- Introduced zero-downtime deploys with Deployer and atomic symlink releases across 14 client sites, replacing a manual FTP process that had caused four production incidents in the preceding year.
PHP developer focused on performance and reliability
- Profiled the checkout path with Blackfire and Xdebug, replacing three chatty internal API calls with one cached aggregate and trimming server time per request from 1,900 milliseconds to 240 at peak.
- Tuned php-fpm pool sizing, OPcache memory allocation and nginx buffering across four production servers, absorbing a traffic spike of triple normal volume without adding hardware or shedding requests.
- Added Redis caching with tagged invalidation to the product catalogue and pricing rules, cutting MySQL read load by 62 percent and holding response times flat while the catalogue tripled in size.
- Replaced a nightly cron export with a chunked Laravel job streaming to S3, bringing a task that regularly exhausted the 512 MB memory limit down to a steady 90 MB and a quarter of the runtime.
- Instrumented the application with structured logging and Sentry release tracking, cutting mean time to identify a production error from around two hours to under ten minutes across the whole team.
Top PHP Developer Skills
Order these by what the target job actually runs on. A Laravel product team and a Magento agency will scan for very different things:
Hard skills
- PHP 8.2 and 8.3
- Laravel
- Symfony
- Composer dependency management
- Eloquent and Doctrine ORM
- MySQL and MariaDB
- Database indexing and query optimisation
- REST API design and versioning
- Redis caching and queues
- PHPUnit and Pest
- PHPStan and Rector
- PSR-12 and PSR standards
- Web security: SQL injection, XSS, CSRF
- Payment integrations such as Stripe
- nginx, php-fpm and OPcache
- Git and pull-request workflow
- CI/CD and zero-downtime deployment
- Docker and local environment tooling
- WordPress, WooCommerce and Magento
- Blackfire and Xdebug profiling
Soft skills:
- Client communication
- Estimating realistically
- Code review
- Debugging inherited code
- Documentation habits
- Working to fixed launch dates
PHP Developer Certifications
PHP is a field where shipped work beats paper, so treat these as supporting evidence rather than a route in:
-
Zend Certified PHP Engineer
— Zend by Perforce The closest thing PHP has to a vendor-neutral language credential. Most useful for consultants and contractors who need a signal clients recognise.
-
Laravel Certification
— Laravel Optional. Worth holding if your Laravel work has been on internal or client systems nobody outside the company can inspect.
-
Symfony Certification
— SensioLabs Carries more weight than the Laravel equivalent in European enterprise shops, where Symfony is often the house framework.
-
MySQL Database Developer
— Oracle Useful if you are positioning on data-layer depth, since most PHP applicants cannot evidence query tuning beyond adding an index.
-
AWS Certified Developer: Associate
— Amazon Web Services Relevant when the role involves queues, S3 and containerised deployment rather than shared hosting.
Common PHP Developer Resume Mistakes
These come up constantly in PHP applications and each one is quietly costing candidates interviews:
Most of them take an afternoon to fix once you can see them. If you want a layout that keeps framework detail visible without collapsing into a wall of text, start from our online resume builder and paste your bullets straight in.
- Listing PHP with no version. Reviewers assume the worst, and "PHP" alone reads as a developer who may still be maintaining procedural PHP 5 code.
- Framework soup. Claiming Laravel, Symfony, CodeIgniter, CakePHP, Yii and Zend at once signals shallow exposure rather than range; pick the two you would defend in a technical interview.
- Hiding the legacy work. Version upgrades, refactoring raw queries and killing global state are exactly what employers need done, so put them in bullets rather than apologising for them.
- Describing CMS work as development without saying what you built. "WordPress" could mean plugin architecture or installing a theme, and a hiring manager will assume the latter.
- No mention of the database. PHP roles are database roles; a resume with no index, query-count or schema detail reads as someone who only ever called the ORM and hoped.
- Skipping security entirely. On the web tier this is a red flag, especially for anyone who has spent time in agency work where inherited codebases are frequently injectable.
PHP Developer Resume FAQs
The questions PHP candidates search most often before they start writing:
Lead with the framework and PHP version, then MySQL, Composer, REST API design, PHPUnit or Pest, Git and your deployment tooling. Add caching and queue experience with Redis if you have it. Order the list to match the job advert, because Laravel shops and Magento agencies scan for different names.
Not necessary, but it is the most searched PHP keyword by a wide margin. If your background is Symfony, CodeIgniter or a bespoke framework, say so plainly and show transferable depth in routing, ORM work and dependency injection rather than pretending to Laravel exposure you cannot defend.
Yes for agency, CMS and e-commerce roles; keep it to one line for product engineering roles. If you do include it, describe the engineering rather than the platform: custom plugins, REST endpoints, or a headless migration carries far more weight than theme customisation.
One page for up to five years of experience, two pages after that. Agency PHP developers often have long client lists; group them under one employer heading rather than giving every project its own block, or the document sprawls past readability.
No. Hiring is decided on shipped applications, a code sample or a technical test. A Zend or Symfony certification helps mainly for contractors, career changers, and developers whose commercial work sits behind NDAs and cannot be shown.
Put the current version in your skills line and any migration you led in your bullets. "PHP 8.2, upgraded 90,000 lines from 7.4 with Rector and PHPStan" answers the modernity question and demonstrates the exact task many employers are hiring for.
Include them briefly if they are real: Blade or Twig, plus Vue, Livewire or Alpine. Two or three lines is enough. Extending the front-end list too far dilutes the backend signal that a PHP hiring manager is looking for first.
Get Started With Our
Free Resume Creator today!
Free sign-up. No credit card required.
