Real, anonymous reports from people who interviewed for Software Engineer at OpenText, newest first and distilled into what to expect across the loop.
I had a fairly average, engineering-heavy journey with multiple rounds focusing on DSA plus back-end fundamentals, and I didn’t reach an offer.
I went through an unusually difficult and discouraging process for the Software Engineer role, and I didn’t move forward.
The initial screening often involves a conversation about your background and fit for the role, but experiences vary significantly in professionalism and tone, impacting candidates' impressions early on.
Candidates can expect a mix of coding challenges focused on data structures and algorithms, with some also covering core programming concepts like OOP, SQL, and system design, often through multiple rounds.
Interviews may include behavioral questions and managerial discussions about handling pressure and decision-making, with varying levels of emphasis across different experiences.
The depth of technical questioning can vary, with some candidates facing challenging, in-depth questions on specific technologies like Java and Spring, while others may experience a mismatch between expected and actual topics.
Candidates frequently report a lack of follow-up or clarity regarding their application status, with some experiencing ghosting after interviews, which can lead to frustration regardless of performance.
The interview process is generally structured but can feel disorganized or mismatched in expectations, impacting candidates' perceptions of the company culture and fit.