Real, anonymous reports from people who interviewed for Software Engineer at AUTO1 Group, newest first and distilled into what to expect across the loop.
After a recruiter call, the process moved fairly quickly into multiple technical touchpoints. The first screen felt like a guided set of questions in the Java ecosystem—enough to see whether my background matched what they were building. Then I sat through a deeper technical session that leaned heavily on language and framework fundamentals; the emphasis felt less about memorized syntax and more about how I approached problems. The interviewers stayed focused on my mindset for working through issues, not just whether I could recite details.
I didn’t make it past an early stage, but the first interview itself was pleasant enough. They asked mostly basic background questions to get a picture of my experience, and after the call they told me the interview went well and they would schedule the next step.
The interview process is generally structured with multiple stages, starting with an HR screening followed by technical interviews that may include live coding and system design discussions. However, candidates reported inconsistencies in pacing and follow-up, leading to feelings of disorganization.
Technical interviews often emphasize language and framework fundamentals, with a mix of theoretical questions and practical problem-solving tasks. Candidates experienced a range of difficulty levels, with some finding the questions shallow while others faced more challenging live coding scenarios.
Initial HR interactions vary from thorough discussions about the role and company context to more robotic and checklist-like conversations, impacting candidates' perceptions of the company's professionalism. Some candidates noted a lack of clarity and engagement during these early stages.
Candidates frequently reported issues with communication throughout the process, including delays in feedback and unclear next steps after interviews. Many expressed disappointment over not receiving constructive feedback or closure after their interviews.
The interview environment can be stressful, particularly during live coding sessions where candidates feel pressured to perform under tight time constraints. This aspect significantly influenced candidates' experiences and outcomes, with some struggling to demonstrate their skills effectively.
Overall, many candidates left the process without offers, often feeling that the outcome was less about their performance and more about the interview process itself. Reflections commonly included a desire for clearer communication and a more coherent structure throughout the interviews.