F5

Pros: Working as a Software Engineer at F5 in Seattle, I appreciate the stable environment of this multi-cloud application security company. My team is very supportive, and there are good opportunities to learn. The work-life balance is genuinely positive, and the hybrid work arrangement offers excellent flexibility.
Cons: Career progression sometimes feels a bit slow; promotions aren't as fast as I'd like. Also, some internal approval processes can be bureaucratic, which can occasionally be frustrating.
Advice to Management: Focus on streamlining promotion paths and internal approval workflows to empower employees more.

Pros: The pay and benefits package is genuinely strong, highly competitive for a Software Engineer in the Seattle tech industry. Medical, dental, and PTO are excellent. I really value the company culture; colleagues are supportive, and I've learned a ton. The hybrid work model significantly aids work-life balance in this stable network security company.
Cons: Career growth can feel a bit slow, especially regarding promotions. Also, internal approval processes can sometimes be bureaucratic, occasionally delaying projects.
Advice to Management: Streamline internal promotion paths and reduce bureaucratic approval steps to help accelerate project delivery and career progression.

Pros: The hybrid model is generally good. I could often work remote a few days a week, which was a huge plus for my commute to the Seattle office. For Software Engineer roles, it's pretty common to have WFH options, which F5 usually supports.
Cons: Some projects require more onsite time than others, especially in network security development. There's no consistent company-wide policy, so work-life balance can feel uneven across departments. Managers really dictate how much freedom you get with your schedule.
Advice to Management: Try to standardize hybrid and WFH policies more across the board. It would help teams feel more fairly treated regarding work flexibility.

Pros: The culture among my immediate team members was really good, and working in the Seattle office was fine when we were onsite. For a while, things felt pretty stable here as a Senior Software Engineer, especially with our focus on application delivery solutions. Decent benefits package too.
Cons: Recently, job security has been a big concern. There have been several rounds of layoffs, which really hit morale for us in engineering roles. It makes you wonder about your future, even in a big tech company like F5. The hybrid model also feels a bit up in the air sometimes.
Advice to Management: Management really needs to communicate more openly about the company's direction and future plans. Transparency around staffing changes would help a lot with employee morale and reduce anxiety about job security.

Pros: The base salary for a Software Engineer here is pretty solid, around $140k for me. It's competitive for a big tech company like F5 in Seattle. Stock options are a nice bonus, though they vest over four years.
Cons: Annual raises don't really keep up with inflation after your initial years. Healthcare benefits are just okay, honestly. Our parental leave policy could use a big boost for new parents.
Advice to Management: Look into increasing annual merit raises to keep pace with the market and cost of living. Also, review the comprehensive benefits package, especially healthcare and parental leave, to stay competitive.

Pros: The work as a Software Engineer is usually interesting and engaging. Benefits are solid, and the pay is competitive for big tech in enterprise networking. I got to work on some cool, impactful products.
Cons: Job security isn't what it used to be here. There's been a lot of restructuring, which makes you nervous. For product development roles, it feels like things can change quickly.
Advice to Management: Address the job security concerns head-on. More transparency about company direction and potential impacts on teams would help. We need a clear vision, especially for product development, to feel stable again.

Pros: You'll find smart folks here. As a Software Engineer, I've learned a ton about network security. There's a push for a decent culture at a big tech company.
Cons: The culture feels a bit behind the times sometimes. It's tough to get new initiatives going, especially in the Seattle office. Leadership often seems hesitant to really change things.
Advice to Management: You guys need to really listen and act faster on employee ideas. Push for more innovation, especially in the network security product teams, and cut down on bureaucracy.

Pros: The teams are generally really supportive, which is great for a Software Engineer. People are smart and willing to help, making the hybrid environment pretty smooth. Benefits are solid, typical for a big tech company.
Cons: Career progression isn't the fastest here; it often feels like you're stuck waiting for a spot. The pace can be slow, especially on legacy systems, which can be frustrating. Decision-making at higher levels sometimes feels disconnected.
Advice to Management: Work on improving career path clarity for individual contributors, especially for those working on established products.

Pros: Work-life balance here is generally okay, especially with the remote work flexibility. For a Software Engineer, I usually stuck to pretty standard 40-hour weeks. The benefits package is solid for a big tech company.
Cons: There are definitely crunch times, especially around release cycles for new application delivery features. Some teams, particularly those with on-call rotations, have tougher schedules. Project planning can sometimes lead to unexpected late nights.
Advice to Management: Recognize burnout, especially in critical engineering teams. Improve project planning to avoid last-minute crunch periods.

Pros: I liked the hybrid model, giving me some WFH days each week. As a Software Engineer, I generally stuck to 40-hour weeks. The Seattle office is pretty nice too.
Cons: Sometimes projects in network security or application delivery can have tight deadlines, pushing hours. There's pressure to deliver, especially closer to release cycles.
Advice to Management: Try to smooth out project timelines more. It would help prevent last-minute crunch times for engineers.