SPD

Pros: I've met some really good folks here as a Software Engineer. The teams are generally supportive, and it's a decent place for entry-level tech talent to get started. The hybrid work model in the Seattle, WA office is pretty solid.
Cons: There's a lot of corporate bureaucracy, which slows things down. Sometimes, the company culture feels a bit stale compared to other big tech firms. Decision-making isn't always transparent for individual contributors.
Advice to Management: Try to empower individual contributors more. Streamline approval processes to foster a more agile environment and update that corporate culture.

Pros: Some senior leaders in the Seattle office are great. They genuinely care about their people. Our project leads often provide solid direction for software development, which is good.
Cons: Middle management can be a real struggle here. There's not enough consistent training for new managers. It leads to poor communication and some frustrating Agile sprints, especially for new Software Engineers.
Advice to Management: Invest more in management training, especially for new team leads. Make sure communication is consistent across all levels. This would really help morale and project delivery.

Pros: There are solid engineering teams here, and as a Software Engineer, I've worked on some really interesting software development projects. The hybrid work model in the Austin office is a definite plus for flexibility.
Cons: The company culture can feel a bit old-school and cliquey sometimes. It's tough when there isn't consistent communication from leadership about big company shifts. This definitely impacts overall morale and a sense of belonging for many.
Advice to Management: Leadership needs to bridge the gap between different teams. Foster a more inclusive environment and be more transparent with company direction. It would help a lot with overall morale.

Pros: For most Software Developer roles, the hybrid model helps a lot with personal time. Most weeks are solid 40-hour weeks, which is good for scheduling outside of work. It's a decent setup for the tech industry.
Cons: Sometimes deadlines get really tight, especially during the last week of a sprint cycle. It can feel like management expects more than 40 hours then. Remote work can also blur lines if you don't actively set boundaries for yourself.
Advice to Management: Try to set more realistic sprint goals to avoid last-minute crunch periods. Better communication about project scope changes would help a lot with workload planning for Software Developers. Respecting the 40-hour work week consistently would improve morale.