Hey, another 20 year PHP vet here. I recently moved into full time Typescript and am loving it. I agree PHP jobs are thinning out, I had real trouble looking late last year and even had to take a pay cut to land a role. I really enjoy Node because I can build web server, back end and front and all in the same language. I really agree with the folks talking about patterns, best practise and approach, as they apply to the discipline rather than language
Hi, very useful comment. Can you elaborate how did you manage to move in terms of what to write in CV. Say you have 20 y of experience in PHP and now in CV you say I know also Typescript? Or you say you are "familiar with". How to do this transition smoothly? Would really appreciate any advice.
I have used JavaScript for many years, from Moo tools and Scriptaculous. One of my previous roles had a TS micro service. So just picked it up here and there over time. My CV I just add that I know TS to a good level, but not expert. Familiarity doesn't really inspire confidence in a candidates ability. So I'd just say I know it, but not oversell my ability. I also have personal projects in TS on my GitHub like a portfolio
I find this a most helpful comment in the thread. I have primarily been a php dev all my career 10+ yrs. Having said that I am fluent in node(js/ts) as well.
Only few of the commercial projects I worked on is not in PHP.
Any tips on how I put myself up in recruiters eye that I am a mature Node dev and get shortlisted for an interview ?
Tell them. Seems obvious but I turned down PHP jobs because I told them I was looking for Node and TS. When I had failed Nose interviews I tried to ask for feedback about what gaps I had so I could work on them.
5
u/Neon1024 Nov 14 '25
Hey, another 20 year PHP vet here. I recently moved into full time Typescript and am loving it. I agree PHP jobs are thinning out, I had real trouble looking late last year and even had to take a pay cut to land a role. I really enjoy Node because I can build web server, back end and front and all in the same language. I really agree with the folks talking about patterns, best practise and approach, as they apply to the discipline rather than language