Real, anonymous reports from people who interviewed for Software Engineer at Applied Materials, newest first and distilled into what to expect across the loop.
I went through an HR-to-technical flow with a short timeline and a couple of coding questions, feeling generally average in difficulty.
I experienced a two-round path where the first round blended behavioral and light tech, and the second round was significantly deeper—overall difficulty felt average-to-difficult.
The interview process typically includes an HR screen followed by one or two technical rounds, often blending behavioral and technical questions. Candidates should expect a mix of formats, including video calls and in-person interviews, with varying levels of depth in technical discussions.
Technical interviews often emphasize coding skills with LeetCode-style problems, as well as domain-specific knowledge such as cloud architecture, FinOps, and QA/testing. Candidates should prepare for both hands-on technical assessments and theoretical discussions related to their field.
Behavioral interviews are a significant component, focusing on teamwork, collaboration, and personal experiences. Candidates should be ready to discuss their background and how it aligns with the company culture and team dynamics.
Overall difficulty varies from average to difficult, with some candidates reporting a pressured environment during technical assessments. It's important to be well-prepared for both the content and the interview style, as this can significantly impact performance.
Candidates often report a lack of clear feedback after interviews, regardless of the outcome. It's advisable to seek constructive feedback proactively and to reflect on the experience to improve future interviews.
Candidates should focus on specific technical topics relevant to their role, such as DSA, system design, and domain knowledge related to their expertise. Tailoring preparation to the job description and expected technical skills is crucial.
