Real, anonymous reports from people who interviewed for Software Engineer at Dana Incorporated, newest first and distilled into what to expect across the loop.
I had a comparatively simple, culture-and-fit style process with multiple rounds. First came HR, and then I spoke with the manager side, followed by a final round that involved the team directly. Across those conversations, the questions stayed grounded: a bit of personality and how I saw the team working, plus some general background tied back to the role.
My experience was very smooth and low-friction from the start. I began with a recruiter-style conversation where we discussed my CV and the role at a high level. Then I moved into a conversation with plant-side leadership—quality and operations managers—where the discussion centered on quality and production topics, along with my past experience and even broader life/job goals. There wasn’t much pressure around deep technical questioning; it felt more like an alignment check.
The interview process typically follows a structured timeline starting with an HR conversation, followed by discussions with hiring managers and team members, often culminating in a final round that emphasizes fit and communication. Candidates noted that the overall flow felt organized, but experiences varied significantly depending on the individuals involved.
Some candidates experienced a coding exercise or technical questioning early in the process, focusing on fundamental programming concepts rather than advanced algorithms. This portion was seen as the most concrete part of the interviews, though it sometimes lacked opportunities for candidates to explain their thought processes.
Behavioral questions were a significant aspect of the final rounds, focusing on how candidates handle challenges and align with the company's goals. The emphasis on fit and personality often overshadowed technical depth, leading to mixed feelings about the evaluation process.
Candidates reported varying levels of professionalism and communication quality throughout the process, with some interactions feeling uncoordinated or disconnected from the role. This inconsistency impacted candidates' perceptions of the overall experience.
Many candidates expressed frustration with the lack of transparency and feedback regarding final decisions, often feeling that the late-stage outcomes were abrupt or unclear. This left some candidates with a sense of disappointment despite positive earlier interactions.
Candidates appreciated the logistical aspects of the interview process, noting that scheduling and document handling were generally smooth and well-organized. However, some felt that logistical efficiency did not always translate into a positive outcome.