Recruiter called to set up a phone call with the hiring manager. Several days of silence, then suddenly a date was fixed and the hiring manager called for an initial phone screening. Pretty simple stuff like C++ templates, iterators, SSL, and the difference between active and passive FTP.
Since I already had an offer from another company and had to make a decision, I pinged the recruiter, and she quickly set up an onsite interview. It was a lengthy onsite process in which you ended up talking to 5-6 engineers and the hiring manager as well.
C++ exception handling, copy constructors, and many questions on C++ templates. Most of the interviewers were obsessed with templates and wanted to dig into them.
Templatized linked list.
One of the senior guys came and started with a "warm-up" question on network latency, and from there on, a barrage of questions...
The hiring manager asked questions on iterators and a whiteboard coding exercise on converting a byte stream into a hex string.
The following metrics were computed from 1 interview experience for the F5 Software Engineer III role in San Jose, California.
F5's interview process for their Software Engineer III roles in San Jose, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for F5's Software Engineer III interview process in San Jose, California.