Pros
People lower down the chain of management are nice, fun and understanding that you're in the same awful situation they're in.
Cons
- Employees, both former and current, have told management that the current need for multiple new features every "Third" of the year is not sustainable. This however does not matter to the CEO or the leads. As an example, multiple software development managers handed in their resignations in under a year because the need for change was so desperate but management didn't want to hear it, so they resigned. -The scope and specification of new features is updated on the whim of the CEO or the Product team. There is no clear direction and developers fumble in the dark to cobble together something in a disjointed, old, awfully optimised system that passes the unset expectations of Product or the CEO. Bonuses are tied to this way of doing things so you will find corners cut and shoddy code implemented just to make people happy, readability and usability be damned. -As others have also said, there is no training for this role offered. It is a complicated mess of a system that uses a smorgasboard of technologies the development leads read about and have decided to implement. -Leads are quite happy to say all sorts of awful things about people who previously worked at PP. If you work here and then leave, you can expect management to make fun of you and use you as an example to try and get compliance from current staff. -You will not learn anything new or exciting while here. You will learn the weird quirks and oddities that this system has because there are so many that only the leads know about, meaning you are constantly fumbling to fix issues without all the information you need or would even be able to find. You will not feel like you are learning anything or progressing in any way towards your career.