A supportive environment overall, though you will get worked very hard.
Poor pay compared to competitors. Lack of stimulating work.
Consider deep down whether some teams should be making substantially more than others. Support teams often need to fill in knowledge gaps for other teams and will work incredibly long hours.
There is more attractive and better paying work for support teams, even with an oncoming recession. Be wary of the potential for some support teams to collapse and the resulting crippling of a program.
45-minute phone interview. First round: Simple coding questions to check your knowledge of algorithms. One coding question to add big integers in C++. Easily doable. Smooth interview process with a good team.
Onsite interview with 7 rounds from different teams, including a lunch interview. Questions were based on school projects, research work, algorithms, and embedded C. Computer architecture questions covered cache, pipelining, Verilog projects, TLB,
First, I had a phone screen. Then, they flew me down to San Diego for an on-site interview, which had about five technical rounds. After a week, they called to say I received the offer.
45-minute phone interview. First round: Simple coding questions to check your knowledge of algorithms. One coding question to add big integers in C++. Easily doable. Smooth interview process with a good team.
Onsite interview with 7 rounds from different teams, including a lunch interview. Questions were based on school projects, research work, algorithms, and embedded C. Computer architecture questions covered cache, pipelining, Verilog projects, TLB,
First, I had a phone screen. Then, they flew me down to San Diego for an on-site interview, which had about five technical rounds. After a week, they called to say I received the offer.