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.
After a recruiter call, I moved into a structured technical loop that lasted a few weeks. The recruiter asked about my background and then explained the rough process, and about a week later I was already in the first technical screen. Across the next rounds with engineers and the hiring manager, the conversation mostly revolved around my past projects—especially my experience with Linux systems and embedded-style software development.
My process started with an HR-style pre-screen: a phone call where I went through background and got basic logistics before moving on. Then the interview experience turned very technical. I had a manager-style round where I walked through my résumé and projects, and that naturally led into a coding portion with a couple of medium-leetcode problems—mostly strings and arrays—where edge cases mattered.
The interview process typically begins with a recruiter screening, followed by a series of technical interviews that can span several weeks. Candidates noted a generally organized and efficient timeline, with feedback provided relatively quickly after interviews.
Technical interviews emphasize a mix of coding challenges, hardware design fundamentals, and problem-solving scenarios, often involving data structures, algorithms, and specific hardware-related concepts like Verilog and digital logic. Candidates should prepare for both practical coding and theoretical questions related to their past projects.
Candidates often engage in discussions about their past projects and experiences, with interviewers probing for depth in technical understanding and practical application. This behavioral aspect is crucial, as it helps assess cultural fit and alignment with the team's work.
The interview atmosphere can vary significantly, with some candidates reporting a friendly and supportive environment, while others experienced a more adversarial or disorganized dynamic. Candidates should be prepared for varying levels of engagement from interviewers.
Candidates should expect a rigorous assessment of their technical knowledge, particularly in areas related to hardware and embedded systems. Interviewers are looking for clarity in reasoning and the ability to connect theoretical concepts to practical applications.
Many candidates reflected on the importance of receiving constructive feedback, regardless of the outcome. Some noted that they wished they had prepared differently, particularly in areas where they felt less confident or had not practiced recently.