Junior Java Developer applicants have rated the interview process at Vanguard with 3 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 68.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Junior Java Developer roles take an average of 28 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Vanguard overall takes an average of 23 days.
Common stages of the interview process at Vanguard as a Junior Java Developer according to 5 Glassdoor interviews include:
Phone interview: 36%
IQ intelligence test: 14%
Presentation: 14%
Group panel interview: 7%
Skills test: 7%
Background check: 7%
Drug test: 7%
Other: 7%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Vanguard (Malvern, PA) in Dec 2016
Interview
Short phone interview followed up by going into their Malvern offices. Group of potential hires there with you, and you watch presentations for part of the day. The rest of the day is the interview itself, where you split up as a group and meet with current employees 1-on-1
Interview questions [1]
Question 1
How would you code a program to answer a hangman game?
I applied online. I interviewed at Vanguard (Malvern, PA) in Oct 2019
Interview
2 rounds of interview.Technical and behavioral rounds, onboarding was smooth process.
Questions came around projects worked with and the flow, core Java, Spring Boot, micro services, threading, and coding as well.
I applied online. The process took 4 weeks. I interviewed at Vanguard (Malvern, PA) in Sep 2018
Interview
Phone interview, technical assessment, in person interview. The interview process is a little long but well worth it for such a prestigious company. Everyone was very helpful and nice along the way.
Vanguard emailed me to set up a phone screen, but it turned into a technical interview with HR. They asked me basic questions about Java, but was expecting in-depth technical answers, not simple responses.