Software Engineer applicants have rated the interview process at Vulcan with 2.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 64.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 22 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Vulcan overall takes an average of 29 days.
Common stages of the interview process at Vulcan as a Software Engineer according to 4 Glassdoor interviews include:
Phone interview: 33%
Skills test: 17%
One on one interview: 17%
Presentation: 8%
Group panel interview: 8%
Background check: 8%
Drug test: 8%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Vulcan (Seattle, WA) in May 2017
Interview
Initial Phone screen was a recruiter who didn't seem to know very much about technology or software. She seemed very interested in promoting Paul Allen rather than talking about the position itself.
I applied online. The process took 3 weeks. I interviewed at Vulcan (Seattle, WA) in Aug 2019
Interview
I applied online, and within a day I heard back from a recruiter, arranging a phone call for the following day, where I learned about the organization and the position and shared my background and reasons for seeking the role. After that I was invited to do a video phone interview with the hiring manager, where we dived into depth on the job, the project and what I could contribute to it (including my knowledge and skill level). A few days later the recruiter checked in, and invited to me the in-person interview. The in-person was 4 hours including a lunch break, where I met with 4 sets of people, all of whom were very kind and the conversations were illuminating. There were some technical questions, including a pair programming exercise. This was an incredibly smooth and positive interview process.
Interview questions [1]
Question 1
Now that you know more about the various aspects of the project, where would you best contribute?