Work-life balance, work ethics (e.g., no lunch hour meetings or evening meetings) because of multi-geo diaspora.
Management change, frequent organizational change, frequent change at the management level.
Trust your subordinates; do not micromanage.
Interview questions were basic, the sort of things one should know if they have worked on automation testing. The interviewers were polite. The process was chaotic, though. With the exception of the first round of phone interviews, all the F2F inter
They asked about my Verilog projects and labs that I took in my coursework, and what I achieved in that lab coursework. The interview went slow. Then questions were on the digital domain. Questions on Verilog and C/C++: * STA * Verilog project
It was quite smooth. One important piece of information is that Intel is a heavily hardware-based company, so knowledge of C/C++ is a must. Further, your resume should have at least one internship or project based on C/C++.
Interview questions were basic, the sort of things one should know if they have worked on automation testing. The interviewers were polite. The process was chaotic, though. With the exception of the first round of phone interviews, all the F2F inter
They asked about my Verilog projects and labs that I took in my coursework, and what I achieved in that lab coursework. The interview went slow. Then questions were on the digital domain. Questions on Verilog and C/C++: * STA * Verilog project
It was quite smooth. One important piece of information is that Intel is a heavily hardware-based company, so knowledge of C/C++ is a must. Further, your resume should have at least one internship or project based on C/C++.