Smith

Pros: I really liked their remote work policy. As a Software Engineer, I could mostly set my own hours, which was great for personal appointments. It's a big plus for work-life balance compared to fully onsite jobs.
Cons: The 'core hours' policy felt a bit restrictive sometimes. While remote work is an option, there wasn't much flexibility if you needed to shift your schedule significantly. It also felt like some team leads didn't really follow the official WFH guidelines.
Advice to Management: Managers need to consistently apply the remote work guidelines. Empower teams to truly embrace work flexibility without micromanaging 'core hours.'

Pros: It's a pretty good place to start out as a Junior Software Engineer. You learn a lot if you're proactive. The hybrid work setup in the Austin, TX office is decent, giving you some flexibility.
Cons: Career growth here is super slow after the initial learning curve. There aren't many clear paths to move up in software development. You really have to fight for new opportunities and promotions don't happen often.
Advice to Management: Create clear paths for career progression in software development for employees. Implement structured mentorship programs to support growth beyond entry-level.

Pros: I do like the hybrid model they offer for work arrangement, it's pretty flexible. My direct team in the Austin office is solid and supportive. You get decent exposure to different tech projects.
Cons: The company culture can feel really cliquey, which makes it tough to integrate as a new engineer. There's not much in terms of formal mentorship or consistent team-building. It feels like you're on your own a lot to figure things out.
Advice to Management: Seriously invest in better onboarding and a real mentorship program for new hires. Encourage more company-wide social events, not just team-specific ones, to help break down silos and improve the overall company culture.

Pros: Some of the direct managers are solid, really support their teams. You get decent autonomy in your daily tasks, which is good for Project Manager roles. The hybrid model allows some work flexibility.
Cons: Senior leadership can be a real struggle. There's a lot of flip-flopping on priorities for software development initiatives, which makes planning difficult. Communication from the top down isn't great, and this really impacts morale for us in the San Francisco office.
Advice to Management: Focus on clearer communication and consistent strategic direction. Senior leaders need to engage more with teams, especially those in Project Manager roles, to understand ground-level challenges in software development.

Pros: The hybrid model is a plus; I only had to be in the San Francisco office three days a week. For a Junior Software Engineer, the core hours are generally solid, so you usually know when you're working. It's decent for fitting in personal appointments.
Cons: Deadlines for software development projects can be brutal sometimes, forcing longer hours to finish things up. There isn't much flexibility outside of the hybrid schedule, so last-minute changes are tough. You can feel like you're always on call.
Advice to Management: Try to plan project timelines more realistically to avoid constant crunch mode. Give teams more autonomy for some flexible hours when possible.