Pros
The scrum team works well together, for the most part. Agile process here is better than at some places, at least within the scrum team. Being on a small team means that one person can make an impact...if the business lets you. GraphQL. Great vacation benefits that they actually encourage you to use.
Cons
Business as a whole should respect that Agile does not mean "fast," nor does it mean "do what we're told without question." Major decisions are sometimes announced in quarterly all-staff meetings with the teams relevant to these decisions having no idea. The company has a good mission, but it doesn't always feel that they practice what they preach. From a dev standpoint, the scrum team needs their business analysts to truly be product owners and have the clout that comes with it. There are no designers here, nor much desire for UX/UI/front-end-only engineers whose passion is developing tools that not only work, but that people also enjoy using. A successful software engineer here will be the unicorn who loves database administration, deployments, and design. Some teams (and their leadership!) view the scrum team as a necessary evil, a means to an end (Some New Feature) rather than partners. Engineers and computer scientists are the future we encourage in our kids, so why are the tech teams at PLTW often treated as burdens? There's also a micromanagement problem here. I observed many times where adults were not being treated as adults. Giving us greater flexibility can also encourage greater productivity in the end. Somewhat related, it would be great if the business casual/formal (depending on team) dress code didn't exist. Since most of us weren't meeting with clients, I didn't see a need for that. We can still dress professionally but also wear jeans. I feel that many, or even most, issues here come from the top down (as mentioned in previous reviews by others), and that means negativity can trickle into teams that would otherwise be effective and passionate about their roles at PLTW.