Philips Senior Software Developer reviews

The leadership of Philips believes that making software is similar to manufacturing devices. Whenever something goes wrong in the software group (or even if it doesn't) the predictable answers are to 1) fire someone 2) hire someone or 3) add a new "process" Although I happen to have met many software quality engineers at Philips, I think management was poor at rewarding them, listening to them, and hiring them. The worst and most troubling condition is that the leadership is not good at its essential task, which is product vision. They haven't envisioned an industry-leading product in any of the segments they're targeting. Every product is "me, too" and Philips as company is coasting on the basis of its market position as one of the few manufacturers of large hospital modalities, which long ago locked in many hospitals to its radiology information system. When the "me-too" strategy fails to enflame Philip's customers' imaginations, development is blamed. In fact, whatever the issue, development is blamed. Development is low man on the totem pole at Philips. I wasn't going to write this review, but they did something petty and annoying after I quit. Since I quit within the first year of hire, I had to pay back my signing bonus. Which I had no problem doing. I left my mailing address and contact information with them, and was promised to receive a letter with payment instructions. But instead of sending me a normal invoice, they put me directly into collection! This impacted my FICO score. It's such a petty malice (or gross incompetence) that I've changed my mind and I'm telling the truth. Don't work for this company if you can find better!

Bureaucracy. Bureaucracy everywhere. From asking for a new mouse to buying a server, you'll face many obstacles along the way, and it'll always take looong time until you get what you need (if it ever happens). Terrible internal processes and tools for tasks and time tracking. Trello? Jira? Not in here! You don't get to work creating native code, but using only internal components of in-house frameworks. It's ok in the beginning of you career, but in the long run you won't actually learn anything new.