Candidates describe Unisys software engineer interviews as fundamentals-heavy: an online test, technical rounds on Java, OOP, DSA or SQL, then HR and manager conversations. Reports span entry-level and experienced roles.
$80K
Avg. Base Comp
$90K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Unisys reports for software-oriented roles lean toward fundamentals and project explanation rather than hard algorithm puzzles. The accounts cover different titles, including Junior Java Developer, Associate Software Engineer and an Angular-focused Associate Engineer role, so the process shifts with the role and hiring channel.
Early screens varied. A Junior Java candidate described an online coding test on arrays, trees, hash maps and string handling, plus Java concept questions on JDK, JRE and JVM and on final versus finally versus finalize(). An Associate Software Engineer candidate took a broad test covering data structures, algorithms, networks, OOP and operating systems. A campus candidate mostly saw aptitude MCQs. Another Associate Software Engineer candidate took an aptitude test followed by a group discussion.
Technical rounds rewarded clear explanations. Candidates were asked about exception handling, OOP pillars and operator overloading, linked lists and sorting, and SQL normalization and transactions. One Angular-focused candidate discussed token management, routing and lazy loading. Another candidate was asked about design patterns used in past projects. Several people were asked to walk through their own projects and the choices behind them.
HR and manager conversations were generally described as conversational, covering background, motivation and team fit. One candidate reported slow communication after a positive screen. Most reported outcomes were rejections, so solid fundamentals and a polite follow-up both matter.
Synthesized from 8 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 Unisys process.
I started with an online test covering computer fundamentals — data structures, algorithms, computer networks, object-oriented programming, and operating systems. It felt like a broad sweep to filter candidates on basics rather than depth. After clearing that, I moved into a technical round where the interviewer asked about exception handling, specifically when a finally block gets called and the edge cases where it doesn't. The questions were straightforward, nothing that required obscure knowledge, but they were testing whether I understood the language fundamentals solidly.
Next came the HR interview, which was more conversational. They asked about my experience with tools like ServiceNow and wanted to understand my background. The energy was social and approachable — the HR person and manager both seemed genuinely interested in getting to know me as a person, not just quizzing me on facts. We talked about the team structure, the Hub Dynamic initiative, and found some common ground on interests outside of work.
Then came the managerial round, where the focus shifted to culture fit and how I'd work within their team. By that point in the process, the vibe felt collaborative rather than adversarial. If you make it through, they conduct a background check before extending an offer letter. The whole process took several weeks from initial call to final decision, so patience is key. Be solid on your fundamentals going in — they're testing breadth of CS knowledge, not trying to trick you. And don't underestimate the relationship-building rounds; they genuinely care about team fit.
Prep tip from this candidate
Brush up on exception handling specifics (finally block behavior, when it doesn't execute) and be prepared to explain computer fundamentals across DSA, networks, OOP, and OS clearly. The technical questions are straightforward, so focus on confidence and clarity in your explanations rather than memorizing edge cases.
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 Unisys
Describing a data project and its challenges
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Prime to N | |
| Monthly Customer Report | |
| Largest Salary by Department | |
| Top 3 Users | |
| String Shift | |
| Comments Histogram | |
| Random SQL Sample | |
| Find the Missing Number | |
| Size of Joins | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Upsell Transactions | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Rectangle Overlap | |
| Minimum Change | |
| Flight Records | |
| The Brackets Problem | |
| Project Pairs | |
| Retailer Data Warehouse | |
| Raining in Seattle | |
| Scrambled Tickets | |
| Find Duplicate Numbers in a List |
Synthesized from candidate reports. Individual experiences may vary.
A Junior Java candidate described a resume screen that looked for Java experience, internships, academic projects, OOP and databases, followed by a short HR call about interest and availability. A separate campus candidate reported a 70% academic cutoff before taking part. Entry routes appear to differ by role.
Several candidates began with an online test, but the content differed. Reports include a Java coding test, a broad test on data structures, networks, OOP and operating systems, and aptitude tests for campus and Associate Software Engineer candidates. One Associate Software Engineer candidate also reported a group discussion.
Technical rounds favored clear explanations over difficult puzzles. Reported questions covered Java concepts, exception handling, OOP, arrays and strings, linked lists and trees, SQL normalization and transactions, and detailed project walkthroughs. An Angular-focused candidate was asked about token management and routing, and another candidate about design patterns used in past projects.
One Associate Software Engineer candidate described a managerial round focused on culture fit and how they would work within the team. Another described a second technical interview covering current work, bug handling and client requirements.
HR conversations covered background, motivation and culture fit, and one HR round ran over an hour. An Associate Software Engineer candidate noted a background check before an offer. An Angular-focused candidate described slow replies after the screen.
