W. L. Gore & Associates New Grad Operations interview questions
based on 2 ratings - Updated Jan 29, 2020
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
100%
Campus Recruiting
Campus Recruiting
Interview search
2 interviews
W. L. Gore & Associates interviews FAQs
New Grad Operations applicants have rated the interview process at W. L. Gore & Associates with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 59% positive. This is according to Glassdoor user ratings.
Candidates applying for New Grad Operations roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at W. L. Gore & Associates overall takes an average of 39 days.
Common stages of the interview process at W. L. Gore & Associates as a New Grad Operations according to 2 Glassdoor interviews include:
Drug test: 50%
Group panel interview: 50%
Here are the most commonly searched roles for interview reports -
2 hour interview, interviewed by 4 groups of 2 associates. Fairly relaxed environment, most interview questions focused on previous work/internship experience. One of the best interview processes I have gone through.
I applied through college or university. The process took 2 weeks. I interviewed at W. L. Gore & Associates in Dec 2013
Interview
There was an on-campus interview with 2 associates who asked general behavior questions and items from my resume. This was followed by an invitation for an on-site interview, including dinner the night before with associates outside of the interview process to ask general questions about the company, experiences, etc. The onsite interview had 4 pairs for 30 mins each, each interview had specific target to explore specific attributes they were looking for (teaming, previous relevant experience, project leadership, etc.)
Interview questions [1]
Question 1
Something in your production area is going wrong. How would you fix it?