Software Engineer applicants have rated the interview process at Ford Motor Company with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 62% positive. To compare, the company-average is 67.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 30 days to get hired, when considering 77 user submitted interviews for this role. To compare, the hiring process at Ford Motor Company overall takes an average of 29 days.
Common stages of the interview process at Ford Motor Company as a Software Engineer according to 77 Glassdoor interviews include:
Phone interview: 24%
Group panel interview: 21%
Skills test: 18%
One on one interview: 8%
Personality test: 7%
Background check: 7%
Drug test: 6%
Presentation: 5%
IQ intelligence test: 3%
Other: 1%
Here are the most commonly searched roles for interview reports -
Tested fundamentals, basic knowledge and problem-solving skills. They also paid attention to details like dress code, confidence, speaking-skills.
As an SE all you really require is sound fundamentals, a forever-learning mindset and confidence in your skills.
I interviewed at Ford Motor Company (Michigan City, IN)
Interview
It was great interview. Went very smooth and the process took no less than an hour. I would love to do interview again with them.
Recommend people to brush up on their algorithm problems
I applied online. I interviewed at Ford Motor Company (Chennai)
Interview
They have thorough interview process from Intro to technical scanning including coding , they make sure to scan through every perspective like culture, personality, knowledge base. Mostly interview panel will have more than 2 people
I applied through college or university. I interviewed at Ford Motor Company (Oakville, ON)
Interview
Interview process consisted of behavioural questions and technical questions. Behavioural questions were typical questions like how do you solve challenges. Technical portion included python code review. I was asked design pattern questions and file reading for hardware modules.
Interview questions [1]
Question 1
how do you solve challenges? Review this code and improve