Real, anonymous reports from people who interviewed for Software Engineer at PACCAR, newest first and distilled into what to expect across the loop.
I started with a recruiter touchpoint and then, about a week later, I joined a panel with four engineers. The first thirty minutes were basically a mix of technical and past experience questions, but it didn’t feel like a hard-core technical grilling like I expected. It came across more like a fluid conversation where the goal seemed to be understanding how I’d work with the team and whether my background fit their day-to-day.
My process felt pretty structured: I had a recruiter phone call first, then a video interview with the manager, and finally a last round with the whole team. Across those conversations, the final step stood out because it included both technical questions and broader concepts, not just one or the other.
The interview process typically follows a structured sequence: an initial HR phone screening, followed by a video or onsite interview with the hiring manager, and often a final round with the team. The timeline for scheduling interviews can vary, but candidates noted a clear progression through the stages.
Interviews often blend behavioral and technical questions, with a notable emphasis on fit and communication rather than rigorous technical assessments. Candidates reported a conversational tone, focusing on past experiences and how they align with team needs.
Candidates encountered a mix of straightforward behavioral questions and light technical inquiries, often centered on previous projects and experiences rather than abstract coding problems. This approach aimed to gauge practical reasoning and alignment with the role.
The overall atmosphere of the interviews was described as friendly and low-pressure, allowing candidates to feel comfortable discussing their backgrounds without the stress of aggressive questioning. This contributed to a positive candidate experience despite some not receiving offers.
Candidates expressed that they could have better prepared for the interviews by focusing on aligning their experiences with the specific role requirements, as some felt their technical knowledge was underutilized during the discussions.
While many candidates did not receive offers, they appreciated the clarity and structure of the interview process. Feedback often highlighted the importance of fit over technical prowess, which shaped their overall impression of the company.