OpenText Software Engineer candidates describe an online assessment, a short HR conversation, and technical discussions covering projects, Java/Spring Boot, cloud tooling, and fundamental coding.
$117K
Avg. Base Comp
$152K
Avg. Total Comp
Not reported
Typical Rounds
7 days
Process Length
For an OpenText Software Engineer interview, prepare to explain your own work with the same care you give coding fundamentals. One Software Engineer candidate reported an online assessment followed by a brief HR-style conversation and later technical discussions. The technical emphasis in that account was practical engineering context alongside basic-to-medium DSA: Java, Spring Boot, Docker, AWS, hashing, two pointers, sliding window, and a question about AWS rate limiting. Be ready to describe a project’s architecture, your exact contribution, and the tradeoffs behind decisions rather than only listing tools.
Other reported software-engineering tracks vary by level and location. A junior candidate described a paper-based technical test before a technical interview, with OOP, SOLID, SQL, binary search, and bubble sort. An internship candidate described live HackerRank-style coding plus core CS questions on DBMS, OS, networking, and OOP. Those reports suggest that fundamentals may be tested broadly, but they do not establish one universal format.
Practice concise walkthroughs of projects, then solve familiar array or string problems aloud while stating the approach and complexity. For Java- and cloud-oriented conversations, connect framework and infrastructure choices to a concrete system you built.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Opentext process.
I went through a fairly straightforward interview process for the Software Engineer role at Opentext. For an internship/campus-style process, it was 2 rounds for me. My first round was a coding round in a Hackerrank-style setup, and I was given two questions that I could solve in any language. The problems were in the easy to medium range and focused on basic DSA, especially strings and arrays. In my case, there was also a live coding element where I had to share my screen and run the code in an IDE, so it wasn’t just about explaining the solution but actually executing it cleanly.
The second round was a technical plus HR round. This one mixed coding follow-up with core computer science fundamentals. I was asked a DSA question around anagram and heap sort, along with basic OOPs, DBMS, and OS questions. The DBMS portion included basics like queries and ACID properties, and networking came up at a basic conceptual level, including troubleshooting. The technical depth was not extreme, but they did expect you to be comfortable with the fundamentals and able to answer quickly without much hand-holding. Compared with a pure algorithm interview, this felt more like a balanced screening of coding ability plus core CS knowledge.
Overall, I’d call the difficulty moderate. The coding questions themselves were not very hard, but the live execution and the breadth of fundamentals meant you needed to be prepared across multiple areas. I ended up receiving an offer. My main advice would be to practice easy and medium string/array problems, review OOPs, DBMS basics, OS, and networking fundamentals, and make sure you’re comfortable coding while sharing your screen and running the solution live.
Prep tip from this candidate
Be ready for a Hackerrank-style coding round with two easy-to-medium questions, often around strings and arrays, and practice running your solution live while sharing your screen. Also review DBMS basics like ACID properties, plus core OOPs, OS, and networking fundamentals, since those came up in the technical round.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Opentext
Write a query to get the largest salary of any employee by department
| Question | |
|---|---|
| Swap Variables | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Minimum Change | |
| Upsell Transactions | |
| Find the Missing Number | |
| Top 3 Users | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Rectangle Overlap | |
| Scrambled Tickets | |
| Flight Records | |
| Bagging vs Boosting | |
| Project Pairs | |
| The Brackets Problem | |
| Maximum Profit |
Synthesized from candidate reports. Individual experiences may vary.
One Software Engineer candidate said the process began with an online assessment. The report does not specify its format or questions, so candidates should treat this as a possible initial screen rather than a fixed assessment blueprint.
The same candidate described a short, relaxed HR-style round focused on behavioral fit, including strengths and weaknesses. Prepare a concise account of your background and project work, while expecting the emphasis to vary by team.
Candidates report technical discussion of Java, Spring Boot, Docker, AWS, and basic-to-medium DSA such as hashing, two pointers, and sliding window. Project ownership was a repeated focus in the Software Engineer account; later rounds may be face to face.
