Pros
- Top management really open up to your feedback (Mainly those in C Level) - Decent compensation package
Cons
- A person who's in charge of implementation of Software development process really is an incompetent , he seem to have vast knowledge on Software development process like SCRUM , AGILE but on the theory level , if something go wrong and need for solution to fix them , he never come up with an executable plan instead what you will always got from him is some quote, Theory from random article or text book that's most of the time didn't actually answer your question , there's no clear step one ,2,3, 4 or actionable solution for an issue that's why most of issue that you have will always there , no matter how long the time pass - They claim to have "Engineer Culture" here but it's simply a disguise of preferential treatment for Developer, here in this company Developer do no wrong , to the point where simply log a bug can be a big issue between QA and Developer , because it will effect with developer OKR and it will make developer look bad, many of the time when QA log a bug which cause by developer miss out requirement or implement with a wrong design can cause uproar within team , they will simply reject by telling that it's not there fault even if it's evidentially that they miss a requirement or design which written down in JIRA card , they can simply push a blame to either other party, sometime they go to the length where they accuse designer that They miss implement some feature or some design because designer change their design after they implement them (which after look at change log, it's not true at all), best part of this circus is that even a person who in charge of Developer department are also onboard with this excuse and give an approval with this kind of behavior!, instead of fix the root cause of this problem instead they will order those who got a stick from Tech team (either Designer, or who ever it's) to "Improve" their work and make sure Developer can understand them and get better at communication so developer will not "miss understand" - to much difference in skill for lead developer in each team , some team have a very good lead dev which are mature and act as a decent lead, while some team have a toxic attitude lead dev which acting like a spoil brat with the power he got , they're difference to the point where working in difference team can make you feel that you're not in the same company - because Developer here got a preferential treatment , they will do whatever they want, they can simply reject not to work on any task because they don't like feature or requirement and they want to change it in the way that they like or change it to make it "easier" and not "waste their effort" to much to implement it, they can simply reject just like that and will not implement on it until you go back to all stake holder to "convince" them again, even if those feature requirement are from agreement from all stake holder which already include representative from developer as well, but if the developer who implement those feature didn't like it, well you have to go thought all meeting again, they simply didn't care about timeline at all , the only thing they care is their ease of work, and if you ask me why all this happen , why even for Junior developer can wield this kind of power, well it's because those who in charge of developer department are encourage this and back them