DevHub

Pros: As a Software Engineer, the work-life balance is pretty good most weeks. I appreciate the hybrid work model; being in the Seattle office two days helps collaboration without burning you out. We usually stick to 40-hour weeks.
Cons: Sometimes project deadlines get super tight, and you'll put in extra hours. It's not constant, but during release cycles, the expectation is definitely there. Can be tough on personal plans then.
Advice to Management: Try to buffer project timelines more effectively. It would really help prevent crunch periods for engineering teams.

Pros: As a Software Engineer, the remote work option was a huge plus for me. I could adjust my schedule pretty easily for personal appointments. It's really WFH friendly, which is great.
Cons: Even with WFH, there are so many meetings. Sometimes my calendar was just booked solid and it's tough to get deep work done. For a tech company, I thought there'd be more asynchronous work.
Advice to Management: Try to cut down on unnecessary meetings. Trust your remote developers more with asynchronous work and focus on clear communication channels instead of constant calls.

Pros: I've enjoyed the work-from-home policy; it's great being remote from Seattle and setting my own schedule most days. For software development roles, the day-to-day is pretty flexible, which helps a lot with personal appointments.
Cons: Sometimes the "flexibility" means unclear expectations, especially for a growing startup. It can be tough to coordinate with teams across different time zones when there aren't core hours, which impacts productivity.
Advice to Management: Try to set some clearer core collaboration hours, even for remote teams. It would help for sprint planning and just general team syncs.