OpenText Interview Questions
& Process

So the interview process was pretty well put together and managed professionally. It kicked off with a quick screening call, then a chat with a director to see if my background matched what they needed. After that, I had a panel interview with six people who really dug into my knowledge of Kubernetes, Terraform, Python projects, and how I handle on-call duties and ITIL. That lasted about an hour. They also had a practical, hands-on technical part for about an hour where I had to debug a live EKS cluster, focusing on Kubernetes and Terraform problems, which felt really relevant. I liked that they got back to me with feedback quickly. All in all, it was a really organized, thorough, and efficient process.

So, the interview started with an HR call, then there were two really tough in-person technical interviews. The questions were super hard and needed a lot of skill. The salary they offered was pretty low, like $60k a year, which is way less than usual for this kind of tech job, especially in Canada. It was weird because my resume showed 3 years of experience, and they still interviewed me, but then they brought up not having 5+ years. It was frustrating. I wouldn't suggest applying here. The company had huge layoffs in 2025, cutting about 1,600 jobs because of changes, which makes me wonder about job security. Also, the stock (OTEX) hasn't been doing well, down about 26% this year and over 50% in the last 5 years, which seems like bigger problems and adds to the uncertainty about where the company is headed.

So at OpenText, the interview usually starts with a design exercise where they give you a problem on a sheet of paper. It takes about an hour, and you gotta figure out the problem, who the users are, their goals, make user flows and IA, sketch out some wireframes, and talk about your assumptions and why you made certain choices. They don't care about how pretty it looks, just your thinking and problem-solving skills. Then, there's a panel interview where they'll ask about your approach, dig into your wireframes and IA, see how you made decisions and what trade-offs you made. They'll also want to chat about your past projects, challenges, and how your designs made a difference. Basically, they're checking if you can think like a designer, explain yourself clearly, and have good experience.

So, I had this interview, and it was pretty good. First, there was an HR chat, then a technical part where they hit me with some scenario questions about the job. The person interviewing was cool, made it easy to explain stuff. I liked how they focused on solving problems and talking things through, plus I got to ask about the team and how things work around here. It was a good chance to show what I can do and also get a feel for the company and what they care about.