Real, anonymous reports from people who interviewed for Software Engineer at Sandisk, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role with an overall easy, low-stress feel, moving through three rounds quickly.
I interviewed for a senior device R&D Engineer role and found the process straightforward, with about four rounds over roughly two weeks.
The interview process typically consists of multiple rounds, often starting with an HR screen followed by technical discussions, and can span from two weeks to a month. Candidates should expect a mix of technical and HR rounds, with some experiences highlighting a more extensive onsite loop.
Technical interviews primarily cover fundamental concepts related to memory architecture, CMOS, NAND, and digital logic, with an emphasis on basic programming and systems knowledge. Candidates should prepare for questions that align closely with their background and resume.
HR rounds often focus on fit and motivation, with candidates discussing their backgrounds and experiences in a friendly manner. These discussions are generally low-pressure and aim to assess alignment with the company's culture and values.
Overall, candidates report a manageable difficulty level throughout the interview process, with many describing the questions as straightforward and approachable. However, some candidates have experienced mismatched questions that did not align with their expertise, leading to frustration.
Onsite interviews can involve multiple back-to-back technical and managerial discussions, often requiring candidates to demonstrate their knowledge in a high-pressure environment. Candidates should be prepared for a thorough evaluation of both technical skills and interpersonal fit.
Many candidates express a desire to better align their preparation with the specific technical areas relevant to the role, as well as to clarify expectations regarding the interview process. Some recommend practicing core concepts and being ready for a variety of technical discussions.