Software Engineer applicants have rated the interview process at Cox Automotive with 4 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 57.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Cox Automotive overall takes an average of 18 days.
Common stages of the interview process at Cox Automotive as a Software Engineer according to 1 Glassdoor interviews include:
Phone interview: 20%
Drug test: 20%
Personality test: 20%
One on one interview: 20%
Presentation: 20%
Here are the most commonly searched roles for interview reports -
I applied through other source. I interviewed at Cox Automotive (Hyde Park, NY) in Nov 2020
Interview
This is for a position in their new hyde park location. 1st round was behavioral and previous skills history. Second round was technical with technology based non algo questions. I was promised an awnser either yes or no but no awnser was provided. Seems very unprofessional, I would not want to work here with that type of professionalism.
Interview questions [1]
Question 1
C# tech stack type questions. Sql server, some java script.
I applied online. The process took 2 months. I interviewed at Cox Automotive (Atlanta, GA) in Oct 2025
Interview
The process started with an initial phone call with the recruiter, followed by a short conversation with the hiring manager about the role and my background. After that, I was invited onsite to the Atlanta campus for a panel interview with three team members, two Principal Engineers and one Senior Software Engineer.
The onsite included two medium-level LeetCode-style coding questions. The interview itself went really well, and I was told afterward that I had passed and they intended to move forward. However, communication afterward was very slow. My original recruiters were laid off due to budget issues, and after waiting about 5.5 weeks with no updates, I called my new recruiter and was told they had decided to move forward with another candidate.
Overall, the interview experience was positive and the engineers were great, but the recruiting communication felt unorganized and stale, especially since updates only came after I reached out several weeks later.
Interview questions [1]
Question 1
OOPS Concepts, 2 Leetcode Medium Questions, and White board system design question
A meeting with a recruiter early on. A call back later for a final interview onsite at the location. The onsite contained both a behavioral and technical stage with different managers across the different teams
Interview questions [1]
Question 1
What was a time you took initiative to optimize a process/project workflow?
the interview consisted of one phone screen with the recruiter, and then 2 in person rounds. one technical and one behavioral. They were pretty basic questions. The technical included lots of OOP concepts.