Amazon

Pros: I appreciate the hybrid model for Software Development Engineer roles. You get some days remote, which helps avoid the Seattle traffic. There's decent flexibility with daily start/end times if your team allows.
Cons: The return-to-office mandate can feel pretty rigid. It's not truly remote work, and we're expected onsite 3 days a week. It can be tough to schedule personal appointments around those fixed office days.
Advice to Management: Listen to feedback on remote work policies. More trust in teams to decide their own onsite schedules would really improve morale and productivity.

Pros: For Software Development Engineers, the hybrid model in the Seattle office is pretty solid. You get a few WFH days each week, which helps avoid that crazy traffic. It's nice to have that option for personal appointments too, it's not super strict.
Cons: The main issue is the sheer number of meetings, especially in a big tech company like this. Even with hybrid work, your calendar fills up super fast. It can be really tough to get deep work done during office hours with constant interruptions.
Advice to Management: Maybe look into reducing meeting loads or designate some 'no meeting' focus blocks. It would really help productivity for engineering teams and improve the sense of flexibility.

Pros: As a Software Development Engineer, I did appreciate the option for hybrid work. It's nice to have a couple of remote days each week for sure. This is pretty standard for big tech now, so it's good they offer it.
Cons: The three days onsite requirement in the Seattle office really limits true flexibility. It makes planning tough, especially with personal appointments. For e-commerce roles, sometimes it feels like they could offer more WFH.
Advice to Management: Seriously reconsider the strict three-day onsite policy. More trust in employees for remote productivity would help work-life balance a lot.

Pros: I liked the hybrid model allowing some remote work; it definitely helped with the commute to the Seattle office a few days a week. There's some freedom to arrange your daily schedule around core team hours, which is good for personal appointments.
Cons: Despite the supposed flexibility, as a Software Development Engineer, you're expected to deliver a lot. This often means working well over 40 hours, making the 'flexibility' feel more like just spreading long hours out. It's tough to truly disconnect in this big tech environment.
Advice to Management: Encourage teams to truly embrace work-life balance, not just flexibility. Managers need to set clear boundaries on expected working hours to avoid burnout among Software Development Engineers.

Pros: For a big tech company, the hybrid work arrangement is decent. I get to work remotely a few days a week, which helps with my commute into the Seattle office. There's some flexibility around daily start times too.
Cons: There's still a big push for on-site presence, which feels less flexible than ideal. Meetings often stretch late, impacting work-life balance even with a hybrid setup. It's tough to truly disconnect as a Software Development Engineer.
Advice to Management: Consider reducing mandatory in-office days and encouraging managers to respect after-hours time. Focus on meeting efficiency.

Pros: I like seeing my team in person some days. The Seattle office has good facilities. It helps with project collaboration on cloud computing initiatives.
Cons: True work flexibility isn't really an option for SDEs. We're expected in the office three days a week. It makes personal planning tricky, especially for big tech roles.
Advice to Management: Give teams more autonomy on remote versus office days. A one-size-fits-all hybrid policy isn't ideal for all roles.

Pros: For a big tech company, they're decent about WFH a couple days a week. It's helpful if you need to run errands or manage personal stuff from the Seattle office. You usually can adjust your start time a bit.
Cons: True flexibility isn't really there, especially for Software Development Engineer roles. There's often pressure to be available, even on evenings for on-call. It's tough to really disconnect in this fast-paced tech industry environment.
Advice to Management: Management should try to genuinely promote work-life balance and respect boundaries for employees. Reducing on-call frequency and fostering a culture where people aren't expected to be 'always on' would help a lot.

Pros: You do get some flexibility with your in-office days if your manager is cool. For Software Development Engineer roles, the current hybrid policy means you're not fully remote, but it's better than 5 days in office. Some teams in big tech might offer more, but this is decent.
Cons: The mandated 3 days in the Seattle office can be tough for work-life balance, especially with the commute. It's not true work flexibility when you're tracked on badge swipes. Full remote options are super rare, even if your specific role could do it.
Advice to Management: Consider more flexible remote options for SDEs whose work doesn't truly require onsite presence. Trust your teams to get the work done.

Pros: Some SDE roles, especially in big tech, do offer decent flexibility. The hybrid model lets you work remote from Seattle a few days. It's nice not to be in the office daily.
Cons: True work-from-home options are rare for Software Development Engineers. It really depends on your manager and team. The ecommerce industry pace means you're often expected to be available, hurting real flexibility.
Advice to Management: Encourage consistent flexibility policies across all engineering teams. Empower managers to trust employees with remote work, especially for experienced Software Development Engineers. It would improve retention.

Pros: You might get decent WFH options on certain teams, especially for some Software Development Engineer roles. There's a solid hybrid model in a few Seattle offices.
Cons: Many teams are super strict about core hours, so you can't always just pick your own schedule. On-call duties can really mess with your work-life balance and any WFH plans.
Advice to Management: Give managers more autonomy to offer flexible work arrangements. Standardize WFH policies across the company, not just team by team.