good intern training process, and friendly
Bad documents to start reading.
I was very nervous at first. The interviewer started to introduce what kind of architecture his team is focused on, and then began asking me related questions. Gradually, I relaxed and finished the interview.
Two phone screens. First screen: Architecture OOO questions. Second screen: Scripting, C++, software-based. Onsite: 8 rounds. Mostly tested on Architecture: * Pipelining * Cache coherency * Tomasulo's Algorithm One round on SoC/verification quest
The first round is the phone interview. They asked some basic questions, such as OOP concepts, constraints, FIFO, and SV. The second round is the on-site interview, where they asked more questions about the software aspect.
I was very nervous at first. The interviewer started to introduce what kind of architecture his team is focused on, and then began asking me related questions. Gradually, I relaxed and finished the interview.
Two phone screens. First screen: Architecture OOO questions. Second screen: Scripting, C++, software-based. Onsite: 8 rounds. Mostly tested on Architecture: * Pipelining * Cache coherency * Tomasulo's Algorithm One round on SoC/verification quest
The first round is the phone interview. They asked some basic questions, such as OOP concepts, constraints, FIFO, and SV. The second round is the on-site interview, where they asked more questions about the software aspect.