Candidates describe Broadridge software engineering interviews as built on CS fundamentals: Java and OOP, SQL, data structures, and detailed questions about your resume. Reports describe two to three stages.
$110K
Avg. Base Comp
$125K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Broadridge's software engineering interviews as weighted toward computer science fundamentals and resume depth. Several accounts begin with an online assessment that mixes aptitude, MCQs, SQL, Java or OOP, and one or two straightforward coding problems such as array manipulation or summing the numbers within a string. Technical interviews follow, with questions on OOP concepts, SQL joins, sorting algorithms, linked lists and trees, and detailed walk-throughs of the projects on your CV.
OOP and SQL come up most often. One candidate was asked to trace a join query on paper, and another to explain Java interfaces and why Java lacks multiple inheritance. Short coding tasks included sorting an array of 1s and 0s without built-in functions, merging strings, printing sequences and counting repeated characters in a string. One candidate was asked to compare the time complexity of linear, doubly and circular linked lists and explain when to use insertion, bubble, merge or selection sort, and noted that precision mattered.
Interviewers also press on your own work. Several candidates say they were questioned on every project they listed, including design decisions. One candidate met team leads and a project manager who asked about CI/CD practices, basic testing and their resume in detail.
Candidates report two or three stages, and the closing conversation is usually an HR or manager chat about background, motivation and team behavior. Reported outcomes include both offers and rejections, so the best preparation is being able to explain the fundamentals and your projects clearly.
Synthesized from 14 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 Broadridge process.
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 Broadridge
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Random SQL Sample | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Scrambled Tickets | |
| Find Bigrams | |
| Last Transaction | |
| Upsell Transactions | |
| Longest Streak Users | |
| Payments Received | |
| String Shift | |
| Customer Orders | |
| Size of Joins | |
| Find the Missing Number | |
| Comments Histogram | |
| Minimum Change | |
| Raining in Seattle | |
| Get Top N Frequent Words | |
| Bagging vs Boosting | |
| Employee Salaries (ETL Error) | |
| Duplicate Rows | |
| Google Maps Improvement | |
| Flight Records |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report an online test covering aptitude, Java or OOP, SQL, DBMS, networking and basic data structures, with one or two straightforward coding problems such as array manipulation. Not every candidate describes this stage, so it may depend on the role or hiring track.
One candidate describes a short first-round HR conversation about why Broadridge, salary expectations and availability. It also included technical questions drawn from the job description, such as OOP in Java and CI/CD, so it is worth reading the posting closely.
Candidates report questions on OOP, SQL joins, DBMS, networking, sorting algorithms, linked lists and trees. Short coding problems included sorting an array of 1s and 0s without built-in functions and counting repeated characters in a string. Interviewers often expected candidates to explain and trace through algorithms such as merge sort.
Many candidates say interviewers dug into their CV, asking what they built, why they chose certain approaches and how technologies were used. Some who found it hard to explain fundamentals or concepts in depth report not advancing, so prepare clear, detailed explanations of everything you list.
Later conversations are described as manager, tech lead or HR discussions. One candidate's HR round was casual and focused on getting to know them, and another met team leads and a project manager. Format appears to differ by team and level.
