Applications Engineer applicants have rated the interview process at Mechdyne with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 25.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Applications Engineer roles take an average of 24 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Mechdyne overall takes an average of 57 days.
Common stages of the interview process at Mechdyne as a Applications Engineer according to 4 Glassdoor interviews include:
Phone interview: 30%
Personality test: 20%
Background check: 10%
Skills test: 10%
Drug test: 10%
IQ intelligence test: 10%
Group panel interview: 10%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Mechdyne in Aug 2016
Interview
1. An online “morality test” (yes, really; lifted verbatim from Frydman, Avraham Allen, "College student nonprofessionals in mental health settings: the effects of participation." (). Masters theses 1896 - February 2014. Paper 1538.). 2. An online personality test. 3. A Mechdyne HR Skype-proctored SAT/ACT/GRE-style standardized exam. 4. A telephone technical interview.
5
Other Applications Engineer Interview Reviews for Mechdyne
I applied through college or university. I interviewed at Mechdyne
Interview
Got a call for a phone interview (15 minutes top). Then received two behavioral surveys. Followed by a 2 hour technical interview. The first part of the hour was critical thinking questions and the second half was all coding on paper for a given scenario.
Interview questions [1]
Question 1
Asked about my experiences pertaining to coding and software.
I applied through college or university. The process took 2 weeks. I interviewed at Mechdyne (Marshalltown, IA) in Jul 2016
Interview
I gave a brief phone interview which was a mix of technical and non technical questions. After that there was a longer interview with both technical and non-technical questions. The interviewer was nice and good to talk to. He was a little intimidating thought. During the programming questions he was talking to his fellow interviewer and didnt seem to have too much interest in listening to me solve the question.
Interview questions [1]
Question 1
Basic programming questions with threads, strings and numbers.
What are your 3 strengths and 3 weaknesses?