Taro Logo

Software Engineer III Interview Experience - Seattle, Washington

May 1, 2012
Negative ExperienceNo Offer

Process

I applied online and got a phone interview. After the interview, there was no response for more than a week. Then I got a call from a different team at F5 for another phone interview. I was then selected to go onsite, where they decided to interview me for two different teams. Overall, I was very confused as to what position they really wanted to interview me for.

Onsite interview process consisted of a coding test and then a 1:1 with members from different teams. Interview questions were standard, pretty much the same as the ones posted here. A few other questions included: print the binary representation of a number, and how would you delete a node from a binary tree. One interviewer asked me questions in networking, and he wasn't sure of the answers himself. He was clearly not a networking person and rambled on about TCP header and datalink layer header fields. Even after I tried to explain the actual field values to him, he wouldn't listen to me. They should make sure the interviewers ask only questions related to their domain.

Questions

What is virtual memory? How would you explain virtualization in layman terms?

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the F5 Software Engineer III role in Seattle, Washington.

Success Rate

40%
Pass Rate

F5's interview process for their Software Engineer III roles in Seattle, Washington is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive20%
Neutral0%
Negative80%

Candidates reported having very negative feelings for F5's Software Engineer III interview process in Seattle, Washington.

F5 Work Experiences