DayOne

Pros: As a Software Engineer, the hybrid model here is actually pretty good. We only need to be in the San Francisco office three days a week. That's decent for a growth-stage tech startup.
Cons: But sometimes those in-office days feel mandatory, even when there's no real reason to be there. It's tough to adjust schedules if something comes up, which kind of defeats the purpose of 'flexibility'. You can't really change which days you come in without a fuss.
Advice to Management: Leadership should revisit the hybrid work policy. It'd be great if we had more control over which days we come into the office, making actual work flexibility better for Software Engineer roles.

Pros: I appreciate the flexible start times, it really helps with my morning commute. The hybrid model is pretty solid, letting me do remote work a couple days a week. It's good for a Software Engineer who needs quiet time to focus.
Cons: The required office days feel a bit rigid. Sometimes I'm just in the office because I have to be, not for collaboration. As a growing tech company, they're still figuring things out, so policies can shift.
Advice to Management: Think about making the in-office days more optional or based on team needs. More flexibility for engineering roles would really help productivity and morale.

Pros: I've worked as a Software Engineer remotely from Austin, TX, which is a huge plus. The WFH policy is solid; you can usually set your own hours if you get the work done. It's great for personal appointments and avoiding a commute.
Cons: Sometimes, though, there's pressure for team syncs that don't always consider different time zones for our global teams. They're trying to push for more in-office days if you're local, which affects that good remote feel. It can feel less flexible than it should for a tech startup.
Advice to Management: Keep supporting the remote work model fully. Be mindful of global team time zones for crucial meetings. Don't force local folks back into the office too much.