You've probably heard "PHP is dying" for most of your career, and kept shipping anyway. Payment gateways, admin panels, Laravel APIs, the one cron job everyone was afraid to touch. A layoff doesn't erase any of it.
This page is laid out as a calm timeline. You don't need to do it fast. You only need to start at Week 1.
For context: "php developer jobs" gets about 1,600 searches a month in India and 320 in the US. India is where most of the PHP search interest is, which makes local and Indian-SMB work a realistic starting point.
Your realistic 90 days
You wrote PHP for a living — Laravel or CodeIgniter apps, custom CRMs, payment integrations, maybe a legacy monolith nobody else would touch. Those apps are still running, and they increasingly need connecting to AI services and messaging. This plan has you test three routes against your own code before you pick one.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Wrote cron jobs that emailed CSV reports | Replace them with a monitored n8n or Make workflow the business can see |
| Built Laravel controllers that called payment and SMS APIs | Call an AI API from the same kind of controller, with logging and limits |
| Debugged legacy PHP nobody documented | Debug AI-generated apps founders can't fix |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | List 5 PHP projects you shipped: what they connected to, what broke most, who owned them | 5 rows in a Sheet |
| 2 | From your own GitHub, pick one repo you can show (or rebuild a small slice of a private one without client code) | Repo link saved |
| 3 | Automation test: move one cron-style task into n8n or Make | It runs on a schedule |
| 4 | Chatbot test: write a 40-line Laravel route that sends a question to an AI API and logs the answer | A logged response in storage/logs |
| 5 | Rescue test: deploy a v0 or Lovable app and fix one deliberate bug | Fix committed with a note |
| 6 | Score each test 1–5 on 'enjoyed it' and 'saw paying demand in postings' | 3 scores written |
| 7 | Save 10 postings for the top-scoring route on LinkedIn or Naukri | 10 links with the tools they name |
Days 1–30: One route, one proof built from your PHP past
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Build the first proof for your chosen route using a pattern from your old PHP work (cron → workflow, controller → AI call, legacy fix → app rescue) | about 12 hours over 3 weeks | it runs and you've recorded a 2-minute walkthrough | A half-size version with no recording. | Commit what exists and stop. |
| Message 5 ex-colleagues or old managers with the recording and ask who's hiring for this | about 2 hours | 5 messages sent, replies logged | 2 people. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: A recruiter or ex-colleague has responded to your new headline, and you have one recording of working proof.
Days 31–60: Second proof and real applications
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Build a second, different proof for the same route | about 10 hours | both proofs linked from one GitHub README | Improve the first proof instead. | Leave the README as-is. |
| Apply to 10 roles that list both PHP and your new route's tools | about 5 hours | 10 applications logged | 5 applications. | Pause applications in interview weeks. |
Signal by day 60: At least one screening call or a client conversation about the route you chose.
Days 61–90: Narrow down and follow up
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Follow up every application older than 2 weeks with one new detail from your proof | about 3 hours | every open application has had one follow-up | Follow up on the top 3. | Skip follow-ups this month. |
| Write a short case study: 'what I'd do with your legacy PHP app and AI' | about 5 hours | case study is a page you can link | A LinkedIn post instead. | Keep it as a draft. |
Signal by day 90: A second-round interview, a paid trial, or a referral from an ex-colleague. Any one counts.
Job-hunt moves that matter for this route
- Many Indian product companies and agencies still run Laravel. Search 'Laravel + AI', 'PHP + n8n' and 'PHP integration' on Naukri and LinkedIn.
- Ex-colleagues and old clients refer faster than job boards. Ask them for a name, not a job.
- Your proof should look like your old work: a repo, a README, a recording.
Where the openings are, and what to type
Also worth a weekly look: Instahyre, Cutshort, Wellfound, and iimjobs or hirist for senior roles. Upwork and Contra if you want freelance work.
Services firms maintaining Laravel and CodeIgniter apps, agencies, and SMEs. Naukri carries most PHP roles; LinkedIn and Upwork add automation and rescue work.
- LinkedIn search string:
(PHP OR Laravel) AND (API OR automation OR "AI integration") - Naukri / foundit keywords: PHP developer, Laravel developer, PHP API (application programming interface) integration
Worries people bring to this route
- PHP and 40+ feels like a double minus. Huge numbers of business apps still run on PHP. People who know them are needed to connect them to AI tools.
- Months out of work. Add one AI step to an old Laravel project and date the commit.
- No degree. PHP hiring is skills-tested more than degree-filtered.
- English. A clean README with screenshots is enough for most clients.
- Family says learn Java instead. Your PHP skills transfer straight into automation and integration work; no restart needed.
- Money. Maintenance work on legacy PHP apps can bridge the gap.
Try it
Letter from Future Self
Fill in a few blanks — the route you're exploring, one skill you're proud of, one thing you'd like to be doing on Day 90 — and the page writes a short letter from you, ninety days from now, back to today's you. It's warm, it's specific to your answers, and it never mentions money or promises. Download it as a text file and open it on Day 90. (Nothing is uploaded; it stays on your device.)
Letter from Future Self
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
What carries over, at a glance
| PHP experience | Where it goes |
|---|---|
| Guzzle / cURL API calls | HTTP Request nodes, bot integrations |
| Laravel scheduler / cron | Schedule triggers |
| Sessions, auth, CSRF | Securing bots and rescued apps |
| MySQL design | Supabase/Postgres, data mapping |
| Legacy code patience | Rescue work, gently |
About PHP itself
PHP isn't going anywhere soon for many businesses. The official policy gives each branch two years of active support and two more years of security fixes, which also means older apps need upgrading regularly — another kind of rescue work. Staying a PHP developer while adding one route is a perfectly valid plan.
Rewriting the PHP headline
Before: "PHP Developer · Laravel, CodeIgniter, MySQL" After: "PHP/Laravel developer → AI automation · integrations, scheduled workflows, n8n"
Scams that target developers
Joining-fee "jobs", placement-guarantee courses, "test tasks" that are full projects, and requests for OTPs or UPI PINs. Official domains only; avoid VPN-based job schemes. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Common PHP-developer questions
Should I switch to Node or Python? Not required for these routes. A little JavaScript helps everywhere. Is Laravel still worth listing? Yes. Keep it; add the new direction beside it. Can I do this part-time? Yes. The quests are sized for that.
Take the quiz · Related: WordPress · Web developer · Backend · Full-stack
We haven't verified pay data for this route.
Newer step-by-step plan: PHP Developer → API Integration Engineer, each with one proof project and a 90-day schedule.
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked between 23 Oct 2026 and 25 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| Laravel scheduling | laravel.com |
| n8n / Make / Botpress / Supabase plans | see verification-log-2026-10-23.md |
| PHP support policy | php.net |
| openai-php/client | github.com |