Real, anonymous reports from people who interviewed for Software Engineer at AMD Construction Group, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer opportunity on campus with an overall average difficulty, moving through résumé-based shortlisting into a technical round and then an HR closeout.
I went to a face-to-face interview that felt blocked by internal mismatch, and it ended without useful feedback even after I had prepared.
Most candidates experienced an initial recruiter screen that focused on resume alignment and role fit, often leading to technical interviews if successful. This stage typically involved basic questions about background and expectations.
Technical rounds varied widely, often including coding questions on data structures, algorithms, and sometimes hardware-specific topics like Verilog or digital design. Candidates reported a mix of LeetCode-style problems and domain-specific questions, emphasizing practical problem-solving skills.
Several interviews included a deep dive into candidates' past projects, where they were expected to discuss their work in detail and demonstrate their understanding of relevant technologies. This often involved situational questions and assessments of their problem-solving approaches.
Behavioral interviews were common, focusing on leadership experiences, conflict resolution, and alignment with company values. Candidates were encouraged to use frameworks like STAR to structure their responses.
Candidates noted varying levels of interviewer engagement and professionalism, with some reporting a supportive atmosphere while others experienced disinterest or lack of feedback. This dynamic significantly impacted their overall impression of the interview process.
Most candidates did not receive offers, with many expressing a desire for clearer feedback on their performance. The outcome often felt tied to the alignment of their skills with the specific needs of the role and the overall interview experience.