Real, anonymous reports from people who interviewed for Software Engineer at ASM, newest first and distilled into what to expect across the loop.
I had an overall average-difficulty, recruiter-led process for an entry-level software engineer/FSE-style role, with about a week or two between first contact and the first technical conversations.
My interview attempt was difficult mainly due to poor logistics and communication, during a single Teams session where the audio and coordination issues made it hard to even follow the questions.
The initial stage typically involves a 30-60 minute conversation with HR or a recruiter, focusing on your background, motivation, and role expectations. This step is crucial for setting the tone and expectations for the subsequent technical rounds.
Candidates can expect multiple technical interviews that assess coding skills, system design, and problem-solving abilities, often with a focus on CS fundamentals and practical applications. The format may include both virtual and in-person sessions, with a mix of direct coding tasks and discussions about past projects.
Some interviews may require candidates to present their past projects or technical knowledge, often using slides, followed by a Q&A session. This aspect emphasizes the ability to communicate complex ideas clearly and effectively.
Behavioral interviews are common, focusing on communication, teamwork, and how candidates handle pressure and challenges. These questions help assess cultural fit and interpersonal skills within the team environment.
Several candidates reported challenges with scheduling, coordination, and communication throughout the interview process, which can affect the overall experience and perception of the company. Timeliness and professionalism in communication are critical.
Candidates often experienced delays in receiving feedback or decisions after interviews, which can lead to frustration. While many did not receive offers, they noted the importance of clear communication regarding the outcome.
