Established leader in its segment.
Engineering-oriented culture.
As with any large organization, your impressions will vary based on locale and who your boss is.
Decent comp package and benefits.
Established leader in its segment that became complacent. The need to move BIG-IP service offerings into the public cloud environment has been readily apparent for some years now.
They are a classic example of "The Innovator's Dilemma" – a company that is being displaced by underdogs and was too complacent to act on it earlier.
The new CEO is driving change by cutting with a sledgehammer rather than a scalpel.
This will most likely result in underperformance of current cash cows. The hope is that new offerings will create value faster than the damage being inflicted reduces it.
The new CEO and his crew need to "skip a level" and talk to people in the trenches to understand the long-term damage being done to current offerings by the way cost-cutting is being implemented.
The new leadership team, brought in with the new CEO, does not seem to trust the old guard, and this is probably why some of the changes are not wise in the mid-to-long term. As it stands at the moment, F5 is two companies with little trust between them.
1st round: test. 2nd round: C++, Linux basics. Asked if I have any cloud or DevOps skills. A small program. 3rd round: managerial, which was again a C++ program and discussed about my projects in resume. Final round: HR round.
First, a networking domain round, a coding round, and a behavioral round. Merge Sort was asked in the coding round. Questions related to load balancers were asked in the networking round. Networking fundamentals were asked too.
There were three rounds. The first was a coding assessment. If you clear it, the next two technical rounds should be 60 minutes long. They mainly focused on HTTP and networking.
1st round: test. 2nd round: C++, Linux basics. Asked if I have any cloud or DevOps skills. A small program. 3rd round: managerial, which was again a C++ program and discussed about my projects in resume. Final round: HR round.
First, a networking domain round, a coding round, and a behavioral round. Merge Sort was asked in the coding round. Questions related to load balancers were asked in the networking round. Networking fundamentals were asked too.
There were three rounds. The first was a coding assessment. If you clear it, the next two technical rounds should be 60 minutes long. They mainly focused on HTTP and networking.