Apical

Pros: Some teams genuinely respect a 40-hour work week. Flexible hours mean I can still hit the gym easily. The hybrid model for the San Francisco office helps avoid daily commute stress.
Cons: Other teams, especially during critical development cycles, demand way more. You can easily work 50-60 hours as a Software Engineer. There isn't a consistent company-wide policy for workload management across all engineering teams in this startup environment.
Advice to Management: Standardize workload expectations across all engineering teams. Don't let certain managers burn out their Software Engineers during intense development cycles.

Pros: The hybrid work model is a big plus here. Being able to work remote a couple of days a week really helps manage personal stuff, especially for us Software Engineers in the Austin, TX area. It's a pretty solid setup most of the time.
Cons: But the in-office days can feel a bit strict. There isn't much flexibility if you need to shift your schedule around, which can be a pain. It's not as adaptable as I'd hoped for a big tech company.
Advice to Management: Management should look into offering more true flexibility, especially for technical roles. Trusting employees to manage their time better would improve morale.

Pros: I've worked at Apical as a Software Engineer for a few years. The work-life balance is pretty solid, especially since I'm remote from Austin, TX. You can usually log off after your 8 hours.
Cons: Career growth is the biggest issue. There aren't many clear paths to move up for individual contributors in software engineering. Promotions for senior engineering roles seem to happen slowly.
Advice to Management: Leadership needs to create clearer promotion tracks for engineers. Give us more opportunities to lead projects or mentor junior staff. It'd really help with retention.