Deep engineering culture emphasizes quality and real-working-stuff over the newest fluff. This leads to a fairly slow response to many fads, but new profitable directions as well.
Unless you have a large amount of experience and scar tissue, prepare to camp for quite a long time before you move up the engineering ladder. However, in the meantime, you will be learning every day from the helpful, old hands.
Limited upside due to a focus on a technical field that is not growing fast anymore. Networking is becoming more and more "plumbing" while the services on top are the highly profitable segment for the moment.
We could benefit from younger blood with skills in newer software development methodologies, albeit obviously they are difficult to attract, preferring the Web 2.0 type of shops.
I got an interview call through an employee referral. It consisted of four 1:1 interviews that went about 45-50 minutes each. Most of the questions were based on pseudo-codes in C and Java. The last interview had a few behavioral questions. There was
Phone interview followed by on-site technical interview.
Phone interview with Manager: Compare TCP/UDP. C programming questions. Hashing. Onsite Interview: Level order traversal. Bit map. Linked list. TCP/UDP. Trace route. Memory management.
I got an interview call through an employee referral. It consisted of four 1:1 interviews that went about 45-50 minutes each. Most of the questions were based on pseudo-codes in C and Java. The last interview had a few behavioral questions. There was
Phone interview followed by on-site technical interview.
Phone interview with Manager: Compare TCP/UDP. C programming questions. Hashing. Onsite Interview: Level order traversal. Bit map. Linked list. TCP/UDP. Trace route. Memory management.