Imajin

Pros: As a Junior Software Engineer in the Austin office, the hybrid work model is a big help. You get 2 days remote, which is nice for personal appointments. The core development team usually respects 40-hour weeks.
Cons: Sometimes agile sprints push things late, especially right before a big release. It's tough when project managers don't fully account for actual engineering development time. Your personal life can definitely take a hit then.
Advice to Management: Project managers need to improve planning for engineering roles to avoid last-minute crunch periods. Please support better time management for your dev teams.

Pros: The hybrid work model is pretty good for most engineering roles, letting you split time between home and the Seattle office. It's nice to have some remote options and avoid the full commute daily. There's decent flexibility to shift your in-office days if something comes up.
Cons: It can feel forced to come in on specific days, even if your team isn't all there. True work-from-home isn't really an option long-term, which is tough for some. The policy isn't super consistent across all dev teams either in this corporate environment.
Advice to Management: Consider more consistent hybrid policies across all engineering departments. Allow for more flexible remote days instead of mandatory fixed ones to improve work-life balance.