Real, anonymous reports from people who interviewed for Software Engineer at Prudential, newest first and distilled into what to expect across the loop.
My process kicked off through recruiter and HR touchpoints, and then moved quickly into interview rounds that felt very “let’s confirm fit, then confirm execution.” I had three interview rounds overall, plus a HackerRank-style assessment. The first round was HR, then I met the team lead, and later the team lead joined by members of the team.
After a recruiter phone screening on Zoom, where the interviewer kept their camera off, I was sent a link to complete an online coding assessment. It was run through HackerRank, and it felt like a straightforward timed gate before anything deeper.
The interview process typically starts with a recruiter screen, followed by an online coding assessment, and then a series of behavioral and technical interviews. Candidates noted that the process felt organized and methodical, with a clear progression from screening to deeper discussions.
Technical interviews emphasized core programming fundamentals and practical knowledge over complex coding puzzles, often including questions on OOP concepts, data structures, and specific technologies like Java, SQL, and AWS. Candidates were expected to explain their reasoning during coding tasks, which highlighted their understanding rather than just the final answer.
Behavioral interviews were structured around specific scenarios, often using the STAR method to assess candidates' past experiences and decision-making processes. Interviewers focused on how candidates handled challenges and worked within teams, making the rounds feel less conversational and more evaluative.
Candidates experienced a variety of coding assessment formats, including timed online tests and video interviews that required them to explain their thought processes. Some found the time constraints and lack of retakes to be particularly challenging, impacting their performance.
While many candidates appreciated the structured nature of the interviews, some reported a lack of communication regarding next steps and outcomes, leading to feelings of frustration. The overall tone varied from supportive to impersonal, affecting candidates' perceptions of the company.
The overall difficulty of the interviews was described as average but demanding, with a focus on demonstrating depth in technical knowledge and problem-solving abilities. Candidates felt that the bar was set higher than expected, especially in technical discussions.