F5 Networks
3.9 of 5 124 reviews
www.f5.com Seattle, WA 1000 to 5000 Employees

F5 Networks Interview Questions & Reviews

Updated Apr 9, 2014
All Interviews Received Offers

Getting the Interview 

68%
18%
9%

Interview Experience 

75%
12%
12%

Interview Difficulty 

35 candidate interviews Back to all interview questions
Relevance Date Difficulty
in

Accepted Offer

Neutral Experience

Programmer/Analyst Interview

Anonymous Employee

Interviewed at F5 Networks

Interview Details – Typical interview loop. Met with stakeholders, business owners, and managers.

Interview Question – How do you communicate detailed projects to large groups   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Average Interview

Technical Intern Interview

Anonymous Employee

I applied through college or university and interviewed at F5 Networks.

Interview Details – campus interview, phone calls with HR and hiring manager, onsite interview with engineers and manager

Interview Question – basic algorithmic questions, nothing complicated   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Declined Offer

Neutral Experience

Software Engineer II Interview

Software Engineer II

I applied online and the process took 6 weeks - interviewed at F5 Networks.

Interview Details – very good hiring process

Interview Question – parse tcpdump output using peerl   Answer Question

Reason for Declining – another job offer

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Easy Interview

Software Engineering Internship Interview

Anonymous Employee

I applied online and the process took 4+ weeks - interviewed at F5 Networks in January 2013.

Interview Details – I applied online and had a phone interview scheduled within one week.
I spoke with the hiring manager for a half hour or so. She wanted to see whether or not my resume was accurate and mostly asked questions about prior projects, languages I knew, and how I go about solving a problem.
After one week, I heard back from my recruiter who wanted to bring me on site for an interview. I had five interviews with four people and it took 3-4 hours. I was asked about many things including behavioral questions, past projects, classes I was taking. Some interviewers went through my resume and asked me about the things on it. They would drill deeper to see if I really had a good understanding of CS concepts.
Basic software engineering experience and knowledge of software design practices are important. Knowing multiple languages helps.

Good problem solving skills are critical for interviewing at F5. It's okay if you don't know something, but you need to demonstrate you could solve a problem you know nothing about.

Overall, interview process was good and the people were quite friendly and supportive. I got a tour of the facility and met many of the people I would later end up working with. There were no trick questions or really difficult problems. I don't think I was asked a single question I didn't know the answer to. If you're a good fit for the job, you shouldn't have problems here.

Interview Question – I didn't get any tricky technical questions, but I was surprised when I was asked for my favorite data structure.   Answer Question

Negotiation Details – Rate was good, did not negotiate.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Average Interview

Software Engineer Interview

Anonymous Employee

I applied online and the process took 2 weeks - interviewed at F5 Networks.

Interview Details – I've applied online and heard back within 2 weeks telling me that they would like to schedule a 45 minutes phone interview with the hiring manager. After that, I've been invited to onsite and had two onsite rounds and one written coding test. I can't tell the questions because of NDA but I could say overall they've tried to touch every area that you might know.

It seemed like they were interested in what you know and how you think. They never say enough, as soon as you keep talking and solving the problem, trying to figure out how much you know. I've had two proper coding questions on board and one data structure design question for a given problem and two open ended problem solving and past experience related questions. There were also behavioral questions.

At the end of the second round, the recruiter came and said they wanted to move on and give an offer on the spot. I was caught off guard but was happy that the process was faster. The whole process (two rounds and offer, excluding the time between phone and on sites) took a week.

Interview Question – I can't because of NDA   Answer Question

Negotiation Details – I was able to negotiate as I had several other offers but the package offered was good and competitive. It had a slight edge.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Difficult Interview

Product Management Engineer II Interview

Product Management Engineer II

I applied online and the process took 2+ weeks - interviewed at F5 Networks in December 2010.

Interview Details – A very detailed interview that tests not only what you know, but how you problem solve. Collaboration is key to working successfully. White boarding skills and how you share ideas and information is important to demonstrate.

Interview Question – Detail a multi tier eCommerce site and how you would trouble shoot an order processing problem?   Answer Question

Negotiation Details – Very straight forward

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Software Engineer I Interview

Software Engineer I
Seattle, WA

I applied online and the process took 2 weeks - interviewed at F5 Networks.

Interview Details – A 1 hour phone screen with coding challenge and C language questions. A week later was called in for an in-person screen. Was given a written programming challenge, followed by interviews with 4 different people. In-person interviews were all coding on white board.

Interview Question – Unexpected question: What do you know about our product.   View Answer

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

1 person found this helpful

Declined Offer

Negative Experience

Average Interview

Instructional Designer Interview

Anonymous Interview Candidate
Seattle, WA

I applied online and the process took 1+ week - interviewed at F5 Networks in May 2012.

Interview Details – Linked in page review, phone interview, in-person interview

Interview Questions

  • Describe what happens when you send an email to me. How many places does it go before delivery and what are they called?   View Answer
  • What kind of phone do you have?   View Answers (2)

Reason for Declining – I asked for and reviewed some of their technical training online and thought it was grim. The interviewer told me what great work they did. There was a disconnect between my standards and their output.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

2 people found this helpful

Accepted Offer

Positive Experience

Average Interview

Intern - Technical Interview

Anonymous Employee
Seattle, WA

I applied through a recruiter and the process took 3 days - interviewed at F5 Networks in August 2013.

Interview Details – I directly contacted a recruiter via email. I had made contact with the recruiter previously based on a tip from a friend who had interviewed with them, so this may have helped my chances of getting a response considerably. I expressed my interest in an intern / entry-level job and gave them my resume. They got back to me on the same day, and we scheduled an interview two days from then.

They emailed a schedule of the interview, including times and people I'd be interviewing with. My interview loop had a short written coding test, two one-on-one interviews with non-senior software developers, and a two-on-one interview with team managers.

The coding test contained three problems: two very simple, and one somewhat tricky. I didn't actually solve the tricky one, but did explain how I would go about solving it. Not being able to solve it did not harm me too much. It seemed to be more about demonstrating some basic knowledge.

Both of the one-on-one interviewers asked some questions about things on my resume. Fairly general questions, but I did need to recall details of past work to answer them. Both interviews also contained a white-boarding question. The questions were not extremely difficult, yet I still didn't solve the question asked by the first interviewer. I did solve the second question, however. What seemed to be important to them is showing how you work through the problem, how you verify correctness (at least informally), and how you communicate with them about the problem and solution. It's helpful to ask for clarification. In retrospect, I could have easily solved the first white-boarding question if I had asked the right question, assuming they also gave me the answer that would have decreased the apparent difficulty of the problem.

The two-on-one interview was an off-site talk over coffee. They asked some questions about algorithms. One prompt was to just talk about a certain basic algorithm. Another question was the sort of exercise you might find in an introduction to algorithms text. They were looking for a basic approach to solving the problem. It was a dialogue, too, as they were willing to give hints. There was general chatting about the interviews so far, prior experience, why I was interested in the job, the work they do there, etc.

In each interview, it paid to be prepared to ask questions. It was also important to show interest in working there. I felt that each interview was as much a technical test as it was a personality test.

The total interview process took about three and a half hours.

Interview Question – I can't give an exact answer, but do review basic algorithms and data structures, and know the basics of the string and I/O libraries of your chosen language, just so that you are able to code without documentation.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Neutral Experience

Average Interview

Software Engineer I Interview

Anonymous Employee
Seattle, WA

I applied through an employee referral and the process took 5 days - interviewed at F5 Networks in November 2009.

Interview Details – The process was streamlined and well-conducted, though long. I spoke with 8 people back-to-back. Expect to code on the whiteboard.

Interview Question – What does our product do, and how would you improve it.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response
RSS Feed Embed
Interviews for Top Jobs at F5 Networks

Worked for F5 Networks? Contribute to the Community!

F5 Networks Videos

Loading...

F5 Networks – Why Work for Us?

​​​​Aligning business strategy and the IT infrastructure The IT infrastructure is key to the success of virtually any major business initiative, from quickly integrating a strategic acquisition to bringing products to… Full Overview

Provided by employer [?]

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.

Glassdoor is your free inside look at F5 Networks interview questions and advice. All 35 interview reviews posted anonymously by F5 Networks employees and interview candidates.