Life Product Specialist applicants have rated the interview process at Prudential with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 60% positive. To compare, the company-average is 60.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Life Product Specialist roles take an average of 28 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Prudential overall takes an average of 26 days.
Common stages of the interview process at Prudential as a Life Product Specialist according to 6 Glassdoor interviews include:
Personality test: 21%
Skills test: 16%
Phone interview: 16%
Drug test: 11%
Group panel interview: 11%
Background check: 11%
One on one interview: 11%
IQ intelligence test: 5%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 2 weeks. I interviewed at Prudential (Plymouth, MN) in Jan 2016
Interview
I was called by a Human Resources Rep for a phone interview. After the phone interview, I went to the Prudential office in Plymouth, MN for a one on one interview with a manager.
I applied through a recruiter. The process took 3 months. I interviewed at Prudential (Plymouth, MN) in Oct 2014
Interview
Took a long time, 3 months. Interview was normal and relaxed. Met with a few managers and took a tour. Conversational interview, but more behavioral questions. Know your past successes and you will be fine. The managers are very relatable.
Interview questions [1]
Question 1
How did you handle a discrepancy with a supervisor?
I applied online. The process took 1 week. I interviewed at Prudential (Plymouth, MN)
Interview
I applied and was asked several days later to do some additional testing. Included some fast paced coding questions, a mock calling portion, and a personality assessment.
Interview questions [1]
Question 1
The most difficult portion was the coding. Had 20 minutes to answer 10 questions that required table reading and code interpretation. I found it difficult because the position was supposed to be entry-level.