Microsoft

Pros: I got to work a solid hybrid schedule as a Software Engineer. Being able to choose my WFH days was a huge plus for my personal life. The support for the hybrid model really helps manage a busy schedule.
Cons: Some teams are way stricter with in-office attendance, making true work-from-home difficult. It really depends on your specific manager, so flexibility isn't company-wide. It's not ideal if you're seeking a 100% remote software development role.
Advice to Management: Try to standardize remote work policies more across different product groups. It would help a lot if all managers offered similar flexibility for engineering roles.

Pros: As a Software Engineer in the Redmond office, the hybrid work arrangement is pretty solid. It's nice to have two or three WFH days built into the schedule, especially in big tech. This really helps cut down on commute time and gives some control over your day.
Cons: The flexibility can feel a bit inconsistent across different teams, and it sometimes feels like leadership hints at more required onsite days. For true remote work, it's really tough to get approved unless you're in a very specific role. It's not as flexible as smaller companies in the software industry.
Advice to Management: Stick to the advertised hybrid model and don't push for more mandatory onsite days without clear communication. Consider more full-time remote options for experienced engineering roles, especially for those who have proven productivity.

Pros: The hybrid model is a solid step forward for this big tech company. I appreciate not being full-time in the office; it saves on the commute to the Redmond campus. For software development roles, having a flexible schedule helps with deep work.
Cons: True work flexibility often depends heavily on your direct manager, which can be inconsistent. There's pressure to be in the office a few days a week, even when remote work is perfectly fine for many tasks. Sometimes I wish there was a more standardized WFH policy across the board.
Advice to Management: Try to standardize flexibility more across different teams, especially for program manager and software development roles. Trust your employees more regarding when and where they can be most productive. The return to office mandates feel a bit arbitrary sometimes.

Pros: The hybrid setup is a huge plus. We can work remote a couple days a week, which really helps with personal appointments and avoiding that Seattle traffic. For software development roles, this flexibility makes a big difference in daily life.
Cons: While the official policy is flexible, some managers still expect more onsite presence. It can feel like there's an unspoken pressure to be in the Redmond, WA office more often than required. This inconsistency across teams can be pretty frustrating.
Advice to Management: Standardize remote work expectations across all teams. Empower managers to truly embrace the hybrid model, not just pay lip service to it.

Pros: The hybrid model is a solid perk here. As a Software Engineer, I can mostly choose my WFH days, which is great for personal appointments. It makes balancing personal life a lot easier, especially compared to fully onsite roles.
Cons: While the official policy supports flexibility, some managers on the Redmond campus can be a bit old-school about coming into the office. There's pressure to be visible, which kind of defeats the purpose of hybrid work arrangements. It can feel like you're still expected to be in more than two days.
Advice to Management: Really enforce the hybrid work model consistently across all teams and managers. Trust your employees to get the job done remotely or in the office.

Pros: The hybrid work model is generally decent for software development roles; I'm usually in the Redmond campus 2-3 days a week. It allows for important face-to-face collaboration but also gives you time for focused work remotely. I appreciate the ability to sometimes shift my in-office days if needed for personal appointments.
Cons: Work flexibility here isn't always consistent across all teams, which can be frustrating. Some managers are super strict about the hybrid schedule, while others are more relaxed. This lack of standardization for big tech positions can make it tough when you hear about other teams having more freedom.
Advice to Management: Try to standardize the hybrid work policy across all engineering teams to ensure fairness. More true flexibility, not just a fixed hybrid model, would really improve employee satisfaction.

Pros: WFH options are solid here for many engineering roles. I've been able to work from home a couple of days a week from the Redmond, WA office which helps a lot with personal appointments. The hybrid model is generally well-supported.
Cons: Some teams and managers aren't as flexible with remote work or the hybrid schedule. There's pressure to be in the office more often for certain projects, which impacts work-life balance. Not all roles get the same remote flexibility.
Advice to Management: Standardize WFH policies across all engineering teams. Don't leave it all up to individual managers, as it creates inconsistencies and unfairness. More clarity on hybrid expectations would really help employees.

Pros: I really liked the hybrid model and WFH options for a Software Engineer, especially early in the week. It's a big tech company, so the tools for remote collaboration are solid. The Redmond campus is great when you do go in.
Cons: Work flexibility can depend heavily on your specific team and manager; some expect you to be in the office more often than others. You can still feel chained to your desk, even with the hybrid setup. Sometimes, meetings run super late for global teams.
Advice to Management: Push for more consistent work flexibility across all engineering teams. Make sure the hybrid model is enforced fairly, and empower managers to truly support WFH when it makes sense, not just follow a blanket policy.