Real, anonymous reports from people who interviewed for Software Engineer at Broadridge, newest first and distilled into what to expect across the loop.
I experienced a shorter, more straightforward interview arc where the questions were meant to confirm fundamentals and then pivot quickly into practical coding.
I had a tougher, higher-scrutiny journey where technical depth mattered (sometimes around systems/DevOps and resume-linked engineering), and the experience could feel uneven across interviewers.
The interview process typically consists of an HR screen followed by one or more technical rounds, often including a take-home assignment or online assessment. The overall timeline can vary, with some candidates experiencing quick decisions while others face delays.
Candidates can expect a strong emphasis on technical skills, including coding challenges, data structures, algorithms, and sometimes system design discussions. The depth of technical questioning can vary, with some interviews being more fundamental while others require deeper knowledge.
Behavioral interviews are a significant component, often focusing on past experiences, cultural fit, and motivations for joining the company. Candidates should prepare to discuss their resume and relevant projects in detail.
The quality of communication throughout the process can vary significantly, with some candidates experiencing clear updates while others report ghosting or vague feedback after interviews. Candidates should be proactive in seeking clarity on their status.
Logistical challenges, such as scheduling conflicts or interviewer no-shows, have been reported, which can lead to frustration and uncertainty in the process. Candidates should be prepared for potential delays and confirm interview details in advance.
Candidates have reported a range of outcomes, from quick offers to extended waits with no offers. The inconsistency in outcomes often correlates with the clarity of the process and the perceived professionalism of the interviewers.