Real, anonymous reports from people who interviewed for Software Engineer at Aptiv, newest first and distilled into what to expect across the loop.
My recruiter conversation was followed by a manager interview about an hour long. The whole experience was quicker to conclude than I expected because there was a mismatch between what they were seeking and what I was presenting. We ended up agreeing to finish early instead of stretching it out.
I went through a fairly straightforward set of online rounds. There was coding and aptitude early on, and after that I had technical interviews that dug into core CS fundamentals along with networking-related questions. The HR part leaned into company and role context rather than repeating purely technical topics.
The interview process typically follows a structured flow starting with a recruiter screen, followed by technical rounds focused on core engineering concepts, and concluding with a managerial and HR discussion. Most candidates noted that the process felt organized and clear about expectations.
Technical interviews emphasize core computer science fundamentals, including C/C++ programming, embedded systems, and specific domain knowledge related to automotive software. Candidates reported that the questions often required deep understanding rather than surface-level knowledge.
Behavioral interviews assess candidates' past experiences, teamwork, and alignment with company values, often using scenario-based questions. Interviewers focus on how candidates communicate and fit within the team dynamics.
For senior roles, candidates noted that expectations extend beyond technical skills to include leadership, mentoring, and process standardization. This emphasis on role-fit can lead to quicker decisions if candidates do not align with these expectations.
While many candidates appreciated the clarity of the process, some experienced delays and poor communication regarding timelines and feedback. This inconsistency can add stress to the interview experience.
Candidates reflected that they should have prepared more for specific technical topics relevant to the role, such as low-level programming and system behavior reasoning, as well as being ready to discuss their past projects in detail.