Software Engineer applicants have rated the interview process at Cox Automotive with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 58% positive. To compare, the company-average is 52.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 24 user submitted interviews for this role. To compare, the hiring process at Cox Automotive overall takes an average of 26 days.
Common stages of the interview process at Cox Automotive as a Software Engineer according to 24 Glassdoor interviews include:
Phone interview: 24%
Group panel interview: 15%
One on one interview: 14%
Presentation: 12%
Skills test: 12%
Background check: 8%
IQ intelligence test: 5%
Personality test: 5%
Drug test: 4%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Cox Automotive (Atlanta, GA) in Jan 2022
Interview
First, I had a Phone screening with one of the HR agents. Second, I had an interview with a Hiring manager for the team that I was applying for. I was given a coding assignment afterwards. Third, I had a Team/panel Interview with the team of the role I was applying for, which consisted of 45min of behavioral questions and 45min of technical questions
Interview questions [1]
Question 1
Tell me how do you handle conflict with another co-worker.
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.