Disorganized and drawn-out interview process, which left much to be desired.
Thirty days elapsed from the initial contact with the recruiter until my interview, which was rescheduled twice by Ford.
The recruiter could not provide any information about the product or group I would be interviewing with. Would this, for example, be e-Commerce?
When I logged in for the remote interview (2 hours), the internal engineers listed on the interview agenda were not present. I was then interviewed by contractors, who revealed this detail at the end of my interview in the course of my questions on the team structure.
But I was not interviewing for a contracted position.
The interview itself was average, both on the behavioral and technical side, although the contractors appeared to have come in loaded with assumptions. They made a couple of errors and made incorrect statements when questioning my knowledge.
It seems like the technical portion of their interviews varies widely based on some of the reviews here, but anyway we walked through a test-driven development exercise.
I came away feeling very good about my prospects.
The next day, I received an impersonal one-line email which simply said, "This one wasn't a perfect match."
Overall, could have been structured much better, and probably varies widely by whichever group you interview with.
What is your definition of technical debt?
The following metrics were computed from 6 interview experiences for the Ford Software Engineer role in Detroit, Michigan.
Ford's interview process for their Software Engineer roles in Detroit, Michigan is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Ford's Software Engineer interview process in Detroit, Michigan.