Good Company, but hard to succeed
Good Company, but hard to succeed
Good benefits. Great work-life balance. Pay is decent.
Slow moving. A few engineering department heads don't talk to each other. Highly engineering-driven company. This manifests in products that don't stick in customer environments. It doesn't understand usability. Very little collaboration between engineering and product teams.
Hire smart guys. Clean up the mess. Let go of some of your engineering VP(s) who don't collaborate.
Was this helpful?
F5 Interview Experiences
Senior Software Engineer
Recruiter contacted me via LinkedIn. 1 phone interview with Architect. Mostly involved multiple programming questions and improving the solution as much as possible. Got a response after 2 days for an onsite. Onsite was 5 interviews with an archit
Senior Software Engineer
I had a phone screening, and was immediately invited to an onsite interview. The onsite interview was a 1:1 with the recruiter (though I never saw him, only his assistant) and two engineers. They asked mostly networking protocol-related questions,
Senior Software Engineer
A phone interview followed by an onsite interview with a programming test. The phone interview was easy. Every 1:1 interview is like going through the resume first and then asking one whiteboard programming question. The whiteboard questions were
Senior Software Engineer
San Jose, California, United StatesJanuary 1, 2015Recruiter contacted me via LinkedIn. 1 phone interview with Architect. Mostly involved multiple programming questions and improving the solution as much as possible. Got a response after 2 days for an onsite. Onsite was 5 interviews with an archit
Senior Software Engineer
San Jose, California, United StatesNovember 1, 2013I had a phone screening, and was immediately invited to an onsite interview. The onsite interview was a 1:1 with the recruiter (though I never saw him, only his assistant) and two engineers. They asked mostly networking protocol-related questions,
Senior Software Engineer
San Jose, California, United StatesOctober 20, 2013A phone interview followed by an onsite interview with a programming test. The phone interview was easy. Every 1:1 interview is like going through the resume first and then asking one whiteboard programming question. The whiteboard questions were
