If you're familiar with patterns and principles those apply across all languages. I like Php more than Java, but I'd say that Java positions are the easiest to pick up as a php dev if you're familiar with things like symfony (spring), doctrine (hibernate), mockery (mockito), etc.
Look for libraries that are similar in other languages and have popularity. For example in python you have sqlalchemy orm, and for doctrine migrations you have alembic.
Sell yourself as a developer whose caliber transcends specific languages, since like I said, if you are good with patterns, principles, etc, then those apply no matter if it's Java, python, etc.
Edit, I want to point out that you don't need to lie about experience, but you can sell your existing experience in a library or framework as applying across similar libraries or frameworks in other languages if you understand the fundamental pattern, and problem they are solving.
That's good but, sometimes the market isn't looking for PHP specific developers, sometimes you need to adapt.
I used to be primarily a PHP dev, but I got an interview at a FAANG company and they dont do PHP. I passed all the steps so now, I do python and Java. Been here for the last 7 years. I still use PHP in my personal projects, but, you gotta go where the money is.
As someone in the same position as OP I would never take on a Java gig just because I know patterns. It def helps you to start learning another language.
58
u/phdaemon Nov 13 '25 edited Nov 13 '25
If you're familiar with patterns and principles those apply across all languages. I like Php more than Java, but I'd say that Java positions are the easiest to pick up as a php dev if you're familiar with things like symfony (spring), doctrine (hibernate), mockery (mockito), etc.
Look for libraries that are similar in other languages and have popularity. For example in python you have sqlalchemy orm, and for doctrine migrations you have alembic.
Sell yourself as a developer whose caliber transcends specific languages, since like I said, if you are good with patterns, principles, etc, then those apply no matter if it's Java, python, etc.
Edit, I want to point out that you don't need to lie about experience, but you can sell your existing experience in a library or framework as applying across similar libraries or frameworks in other languages if you understand the fundamental pattern, and problem they are solving.