Real, anonymous reports from people who interviewed for Software Engineer at Oceaneering International, newest first and distilled into what to expect across the loop.
My process started with a general screening session. After a quick round of introductions, the conversation went into my background and previous projects, with follow-ups about my skills and how well my profile matched the role. The vibe was straightforward, and it felt like they were trying to understand both technical alignment and motivation.
I reached out over email and ended up on a video call with three engineers. The atmosphere was relaxed, and the conversation was largely driven by me—most of the time, I asked questions about their roles and about the company itself. It felt more like a discussion than a formal grilling.
The interview process typically includes a phone screen with the hiring manager, followed by multiple rounds involving engineers and HR, often taking around four weeks from initial contact to offer. Candidates noted a structured approach with clear checkpoints throughout the process.
Candidates experienced a variety of technical assessments, including coding questions focused on C and embedded C, as well as discussions on software fundamentals like OOP and networking. The emphasis was on core concepts rather than specific frameworks.
Interviews often included behavioral questions and discussions about candidates' backgrounds, focusing on fit within the team and the company culture. Candidates were encouraged to share narratives about their experiences and motivations.
The overall tone of interviews was described as relaxed and conversational, with many candidates feeling more like they were having discussions rather than being formally interrogated. This helped ease nerves and foster open communication.
Several candidates expressed frustration over a lack of clear communication regarding interview outcomes, with some not receiving timely feedback or closure after the process. Following up was often necessary to confirm results.
Candidates noted the importance of being well-prepared for technical depth, particularly in core areas like operating systems and troubleshooting, as interviewers sought concrete examples of past experiences rather than theoretical knowledge.
