CARFAX Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 53 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at CARFAX.
CARFAX
Software Engineer
Entry Average Neutral experience No offer 1 round
Interview process
Recruiter call Background check
Interview formats
Behavioral
I had an initial chat with the recruiter, where they asked some basic screening questions. They said the interview team would get back to me, but after waiting three weeks with no response, I got a rejection email.
Confirmed questions3 questions
- What interests you about CarFax?
- What are your reasons for pursuing an MLOps role?
- Can you share details about your past work experiences?
CARFAX
Senior Software Engineer
Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Coding Coding Technical Behavioral
The interview process was super relevant to the job description, with four rounds: two coding challenges, a technical chat, and a meeting with the manager. The coding challenges were the best part, really focusing on the core skills needed, like connecting to external APIs, building RESTful APIs, and using ReactJS for the front-end. The technical interview questions were also spot on with the job requirements and my past work. Honestly, this was one of the most well-thought-out interview processes I've been through—definitely designed to help candidates show what they can do.
Confirmed questions1 question
- Regarding the Chatbox project, what's your approach to removing personal identity information from user questions?
CARFAX
Software Engineer
Mid Average Negative experience No offer 4 rounds
Interview process
Technical screen Technical screen Panel Onsite
Interview formats
Technical Coding Technical Behavioral
This interview process was long and frankly not great for people who get anxious because the panel coding interview had very little time, and the prep instructions were misleading. It was weird because they seemed to not know what position I was interviewing for, even though I was referred by their internal recruiter. I was interviewing for a full-stack role and the initial tech screening was good - a simple Hackerrank web call and object manipulation, which was a good prep for the REST API certification test. The interviewer was great and gave good feedback. The next part, the technical panel interview, was annoying. They asked random syntax gotcha questions about languages or cloud stuff that were on my resume but not relevant to the job, like Python syntax for a Javascript/C# role or why use AWS lambda when AWS wasn't even mentioned. The coding part was supposed to be an hour but started 20 minutes late, so there was only about 35 minutes for a coding challenge that wasn't even for a full-stack position. My advice for technical prep: don't list languages on your resume you can't answer random trivia about. I'd also remove languages not directly relevant to the job or look up common interview questions for any language listed. Also, don't just prep for the specific role like API architecture for a full-stack job, focus on generic data structure questions like you'd see on LeetCode.
Confirmed questions4 questions
- What's the number of unique sets in a list of integers, given the list and a minimum length?
- Can you explain what object oriented programming is?
- What does an underscore do in Python?
CARFAX Software Engineer Interview Questions
Quoted word for word from CARFAX interview reports.
“What's the number of unique sets in a list of integers, given the list and a minimum length?”
Read reports →“What must be included in a try-catch block to guarantee the finally block isn't skipped?”
Read reports →“Given a website, extract a list of items. Then, implement a feature that allows displaying the corresponding item by entering just the first few letters of its name.”
Read reports →“What is Inversion of Control and why is it used in systems like Spring?”
Read reports →“When would you choose not to normalize tables in a database?”
Read report →“Could you list the various interfaces within the Java collection framework?”
Read report →“You wake up and the whole day is yours, what do you do?”
Read report →“Describe how you would implement a restful service to perform CRUD operations on a vehicle with id and vin, and make with id and name.”
Read report →“Can you explain input validation and how to implement different validation rules for different fields in a table, using Python?”
Read report →Formats, difficulty and experience
Across all 53 CARFAX interview reports.