I applied online and the process took 1 week - interviewed at F5 Networks.
Interview Details – a phone interview followed by an onsite interview with programming test. The phone interview was easy. Every 1:1 interview is like going through the resume first, and then asking one white board programming question. The white board questions were easy, but I didn't prepare well. The hiring manager ask me some standard behavior questions.
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
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.
I applied online and the process took 2 weeks - interviewed at F5 Networks in August 2013.
Interview Details – Submitted my application online and got an email the very next day to schedule a phone interview. Their HR group was very fast and my interviewer seemed very friendly and asked me about my background and about F5 Networks. Interview also involved typing into a website for the interviewer to see on the other side.
They asked about differences between a Binary tree vs hash table and the speed of binary tree and hash table. Asked an object oriented programming question, difference between object vs class, write a function that takes in a string and reverse the characters, write a function that matches a string in a binary search tree node.
Interview Question – Object oriented question was a bit tricky Answer Question
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
I applied online and the process took 1+ week - interviewed at F5 Networks in August 2013.
Interview Details – Very sharp (smart) HR, brief phone interview.
Nice, swift hiring manager, half hour phone interview.
Third step, onsite with engineers, architect, upper managerial staff. Way nicer than what I expected reading glass door reviews of other sites. Tech eval was a smart instantiation, look at this code and tell me what you see wrong - plenty to spot that's wrong. Way less nerve-wracking than spontaneous whiteboarding a function that does X.
I applied online and the process took 3 months - interviewed at F5 Networks in July 2013.
Interview Details – Months after sending my resume for a position, a recruiter contacted me for a telephone interview with the hiring manager. It went well, and I was very impressed with the hiring manager, who told me to expect an email from the recruiter about next steps. A couple of months passed, and then I received an email from the hiring manager asking me to come for an in-person interview. I did and thought it went very well. Another month has passed and I've heard nothing. The position is still advertised. I was very excited about this position but subsequently accepted another job. Not sure what's going on at F5.
Interview Question – I don't remember any difficult or unexpected questions. The questions were all very good and focused on my skills and experience, and the company's needs. Answer Question
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
I applied through a recruiter - interviewed at F5 Networks in July 2013.
Interview Details – Was contacted by one of their recruiters who is named after a famous martial arts actor. Dealing with this recruiter was not a positive experience overall, he seemed kind of shady. The company makes good quality products and the people I talked to other than the recruiter were nice and obviously very talented. However the culture was kind of corporate and stiff.
Interview Question – Questions during phone screen: find an element in a binary search tree iteratively and recursively, find the depth of a binary search tree. Explain congestion window and slowstart threshold in TCP. What are the fields in the TCP header? How can the MSS be set in TCP? Find all pairs of numbers that sum to Z in a sorted array. Written test on site: what are the keywords that can be used as modifiers to int in ANSI C. Write a function in C to parse first name and last name out of a string that contains both in quotes. Write a function to print the binary representation of a number, including negative numbers. In person interviews on site: Implement a base64 encoder, what do "extern", "volatile" and "static" mean? can a variable be declared both extern and static? explain how the mpeg2 transport stream works. Write a function to perform run length encoding. What is the difference between char* a = "alice"; and char b = "bob"; ? Implement a stack push function that takes a double pointer to a stack type and a void pointer. What are the important things to consider in web cache design? How does a heap based priority queue work and how can it be improved? Design a malloc and free implementation (no coding). At the end of the on-site the recruiter said he would contact me in a couple of days. A week went by and I never heard from him. He just left me hanging, it seemed like he was purposely avoiding me. I had to call him several times to finally get an answer ... he said it was a tough decision for them but I was not "a good fit", no offer. Answer Question
I applied through a recruiter and the process took a day - interviewed at F5 Networks in May 2010.
Interview Details – Lots of technical interviews (language, data structure, algorithm questions), including a high-level conceptual design interview for a similar kind of product.
Interview Question – For me, trying to remember OO terms that I understood the concepts of tripped me up a little. Answer Question
I applied online and interviewed at F5 Networks.
Interview Details – Found the job listing on the F5 website, and sent my resume via email. The next day I had a message in my inbox from a recruiter who set up an initial screen. She called me the next day and took about 15 minutes of the usual get to know you questions. She emailed me later that day with info on another call with the hiring manager. The HM called me and took about 20 minutes of get to know you and some initial technical questions. He then set me up with a senior technical member of the team for a technical interview. Interview lasted about an hour and was very technical, all over the phone. I later received an email stating that my knowledge wasn't deep enough and would not be going any further.
Interview Question – The most difficult question was asking about access group policies on a ASA firewall. Answer Question
Pros: “Traffic handling code is amongst the most mature and interesting in the business. Lots of latitude to work on what interests you. Smart and hard working dev team, but you're not expected…” “Traffic handling code is amongst the most mature and interesting in the business. Lots of latitude to work on what interests you. Smart and hard working dev team, but you're not expected work yourself to the bone.” – Full Review
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 [?]
Your feedback has been sent to the team and we'll look into it.
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.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –