Real, anonymous reports from people who interviewed for Software Engineer at OpenText, newest first and distilled into what to expect across the loop.
My first step was an online assessment, and it came with a pretty clear structure. I sat for a timed test that started with multiple-choice questions and then moved into DSA-style coding. The coding portion had a couple of problems, including something similar to the Longest Common Prefix idea, and the overall difficulty was manageable.
My interviews leaned heavily into difficulty and behavioral focus, and the intensity showed up early. I started with an HR screening and then went into multiple face-to-face technical rounds that demanded deep expertise. The questions were extremely challenging, and it felt like they expected me to operate at a high level right away.
Candidates typically start with an online assessment that includes multiple-choice questions and DSA-style coding problems, focusing on core CS concepts and problem-solving skills. The assessment is time-bound and can feel tight, with questions often leaning towards strings and arrays.
The technical interviews often consist of coding challenges and system design discussions, with a mix of low-level design questions. Candidates report a focus on practical engineering skills and the ability to communicate their thought processes clearly during coding tasks.
Behavioral interviews emphasize cultural fit and how candidates handle pressure, with questions designed to assess interpersonal skills and team collaboration. The tone is generally conversational, aiming to gauge how well candidates would integrate into the team.
Candidates experience varying levels of difficulty, with some reporting high expectations for technical depth and others finding the process manageable. Mismatched expectations regarding the role and the interview content can lead to frustration.
Feedback timelines can be inconsistent, with some candidates experiencing quick responses while others face prolonged silence or lack of closure. This can contribute to a feeling of uncertainty and dissatisfaction with the overall process.
Interviews often cover a broad range of technical topics, including OOP, data structures, and system design, requiring candidates to demonstrate both depth and breadth of knowledge. This can include specific technologies relevant to the role, such as Java or C++.