
TransUnion software engineer candidates report two to four rounds built around coding fundamentals, core CS questions, deep dives into resume projects, and a manager or HR conversation.
$125K
Avg. Base Comp
$137K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
TransUnion software engineer interviews, as candidates describe them, lean on fundamentals and your own resume more than on puzzle-style problems. The reported processes are short. One candidate had two rounds, a technical interview followed by a hiring manager conversation, while others described three or four rounds that included an online test, one or two technical interviews and an HR conversation. One senior-level candidate said three rounds stretched over about a week.
Coding questions tend to be classic. Candidates mention binary search, spiral traversal of an array, finding the maximum element in an array, and implementing a stack with complexity analysis. A candidate who was rejected suggested practicing array and linked list problems under time pressure.
The conversation around the code matters just as much. Interviewers asked about the OOP pillars, exception handling, interface versus abstract class, DBMS normalization and SQL transactions. One candidate was asked to design a building facility center with OOP principles and write sample code for it. Several people were pushed to explain the projects on their resumes and why they chose their tech stack.
Manager rounds vary. One candidate described a technical discussion about their experience and decisions. Another faced several interviewers and mostly definition-style questions. Outcomes in these reports are mixed, so prepare for both a real conversation and a textbook quiz.
Synthesized from 11 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 Transunion process.
I went through a pretty straightforward process for a software engineer role, but the actual experience felt uneven. The first technical round was mostly about the frameworks and tools I had listed on my resume, and it stayed at a basic level. They asked about Spring Boot and Angular 8, and the focus was clearly on whether I had real working knowledge rather than deep theory. After that there was an HR round where they mainly checked my reasons for wanting to join the company and whether I was serious about the move.
The more frustrating version of the process was for a senior software engineer track, where the interviewer kept asking higher-level design questions but didn’t always seem to have a clear requirement in mind. One question was to create an API that can serve only 20 calls at a time and make the rest wait, and another was how to find the 10th highest value in a dataset of 1 billion records when only 1 million records can be fetched at a time. The questions themselves were reasonable, but the discussion got difficult because the interviewer seemed stuck on his own approach and wasn’t very open to alternative solutions. In my case, the process ended without an offer, and they also stopped after the resume screen because of visa sponsorship. My takeaway is to be ready for very practical system-design-style questions, but also expect the interview to stay at a basic framework level in some rounds and be prepared to explain your reasoning very clearly.
Prep tip from this candidate
Be ready to talk through rate limiting for an API that must cap concurrency at 20, and practice external-memory style thinking for top-K problems on very large datasets. Also review the basics of the frameworks you list, since they seemed to focus on Spring Boot and Angular 8 at a surface level.
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 Transunion
How would you evaluate the model?
| Question | |
|---|---|
| 85% vs 82% | |
| Concurrent LLM Serving | |
| Finding the Maximum Number in a List | |
| Previous NaN Values | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Find the Missing Number | |
| Prime to N | |
| Rectangle Overlap | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| String Subsequence | |
| Triplet Counting | |
| Confidence Interval Explanation | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Decision Tree Evaluation | |
| Longest Increasing Subsequence | |
| Radix Addition | |
| Production Model Monitoring | |
| Most Repetition | |
| Messenger Service Design | |
| Find Duplicate Numbers in a List | |
| Dijkstra implementation | |
| Binary Tree Validation | |
| Target Indices | |
| Filling Supermarket Bag | |
| Median O(1) | |
| Client Solution Pushback |
Synthesized from candidate reports. Individual experiences may vary.
Entry points differ between reports. One candidate had an online test with aptitude and verbal reasoning sections plus two coding problems, and described it as broad rather than deep. A campus candidate cleared a written test before being selected for interviews. Another candidate began with a recruiter call about background and fit for the role.
Technical rounds were often short and direct. Candidates mention implementing binary search, spiral traversal of an array, finding the maximum element in an array, and a stack implementation with complexity analysis. One candidate also got three moderate programming questions in a 45-minute round. Practice these basics under time pressure and explain your approach as you go.
Interviewers asked about OOP pillars, exception handling, interface versus abstract class, DBMS normalization, SQL transactions and, for one candidate, operating systems concepts. One was asked to design a building facility center with OOP principles and show all four pillars in code. Several candidates were pressed to explain their projects and tech stack choices.
Manager rounds differ by report. One candidate described a technical discussion about experience and how they approached decisions. Another faced several interviewers who asked definition-heavy questions. HR conversations covered behavioral questions and, in one case, relocation or availability to work from the office location, followed by a short review of how the interviews went.