Real, anonymous reports from people who interviewed for Software Engineer at Wood, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role and the process felt average in difficulty, with a strong focus on safety/operations knowledge over pure coding, across a short, continuous sequence.
I interviewed for Software Engineer with an overall average difficulty, and it followed a straightforward recruiter/HR plus manager flow (typically one or two stages), with limited or no formal technical testing.
The interview process typically consists of a recruiter screen followed by a discussion with the hiring manager, often without formal technical testing. Some candidates experienced additional stages, such as group activities or technical presentations, but the overall flow remains straightforward.
Candidates reported varying levels of technical questioning, with some focusing on domain-specific knowledge related to safety, operations, or engineering principles. The emphasis on practical application and real-world scenarios was common, with less focus on algorithmic coding challenges.
Behavioral questions and discussions about past projects were central to many interviews, with interviewers looking for clear communication about experiences, challenges faced, and problem-solving approaches. Candidates were encouraged to articulate their motivations and fit for the role.
Some candidates experienced assessment centers that included group exercises and technical evaluations, focusing on collaboration and communication skills alongside technical knowledge. The performance in these activities was critical for evaluation.
The difficulty level of the interviews varied, with some candidates finding the process easy to average, while others faced rigorous technical questioning. Overall, candidates noted that preparation for both technical and behavioral aspects was essential.
Candidates frequently did not receive offers, often citing the importance of aligning their experience with the role's requirements and demonstrating clear communication. Feedback was sometimes provided, highlighting areas for improvement.
