Totally so!
Using PHP in production means:
- The employer organisation is incompetent, or they won't be doing it
- They are also rich, or they'd be bankrupt trying to do it.
Both are good signs if you are looking for a job there.
Using PHP in production means:
- The employer organisation is incompetent, or they won't be doing it
- They are also rich, or they'd be bankrupt trying to do it.
Both are good signs if you are looking for a job there.
IMO the question is not whether you should take a PHP job, it's whether you should take a job building a hosting control panel. Is that type of work something you're interested in? Do you want to become an expert in web hosting? There are lots of companies in the web hosting space, so it could be a solid career domain, but not if it's super boring to you.
I mean if I take up this job my next job would not be in the same domain. I don't have much interest in webdev, but this role also provides the infra exposure so I thought of interviewing.
Also wouldn't using Java or Golang make more sense here if the scale is such?