DriveTime Automotive Group logo

DriveTime Automotive Group Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 18 interview experiences · FREE TO READ

2.1 Rounds average
Average Typical difficulty
64.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at DriveTime Automotive Group.

Showing 3 of 18
DriveTime Automotive Group logo
DriveTime Automotive Group

Software Engineer

Engineering · half a year ago

Intern Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It was a pretty chill interview process, the recruiters were really nice. The whole thing took about 2 weeks and there were just 2 rounds. The final round was with the engineers who would be doing the actual work.

Confirmed questions3 questions
  • Can you tell me about yourself?
  • Describe some projects you've worked on.
  • What are your career aspirations for the next 10 years?
DriveTime Automotive Group logo
DriveTime Automotive Group

Software Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical Coding

The whole thing started with a chat, then a technical interview and a review of my resume. It was actually pretty chill, not as intense as I thought it would be. The first chat, with the recruiter, was just about my background, why I'm interested in working here, and a quick look at my experience. It was friendly but still professional, and it took about half an hour. The technical interview was thorough but not crazy hard. The person interviewing me seemed more interested in how I'd handle real situations instead of just theoretical stuff. They threw some actual problems at me and asked how I'd tackle them. There were a few coding bits too, but it felt more like they wanted to see how I thought things through, not if I could perfectly recall algorithms. Going over my resume was a chance for me to really talk about what I've done and achieved. The interviewer seemed genuinely curious about my past projects and asked some really good follow-up questions. It felt more like a genuine conversation than an interrogation.

Confirmed questions1 question
  • How do you handle working in a fast-paced environment
DriveTime Automotive Group logo
DriveTime Automotive Group

Software Engineer

Engineering

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Technical Behavioral

This was a really long and unclear interview process that took about a month. They asked questions that didn't seem to relate to the job I applied for. The interviewers didn't seem up-to-date with current tech and were focused on older systems. It felt like they got uncomfortable if I knew more about enterprise projects and asked tough questions without good reason. Some interviewers were distracted by phone/slack notifications and even laughed while I was answering. I got the impression they lacked experience in enterprise architecture and patterns. They eventually offered a role with a lower salary. It's frustrating that they wasted so much time if they weren't going to offer the role based on my skills. They should have given feedback earlier. This whole thing felt unprofessional and like a waste of time, and I'm glad I didn't end up working with such aggressive and seemingly clueless people.

Confirmed questions1 question
  • Can you tell me about general software engineering concepts?

DriveTime Automotive Group Software Engineer Interview Questions

Quoted word for word from DriveTime Automotive Group interview reports.

Solve the problem of finding the longest match of a subset between two arrays.

Read reports

Write code on the whiteboard to return the century given a year.

Read reports

Can you explain the difference between overridden and overloaded methods?

Read reports

Can you explain the difference between an abstract class and an interface?

Read reports

Could you explain the distinction between relational and non-relational databases?

Read report

Can you tell me how to improve web page loading speed?

Read report

What unit tests would you create for the traveling salesman problem?

Read report

Regarding component-based UI applications, can you detail the mechanism by which parent components are informed of updates originating from child components?

Read report

Formats, difficulty and experience

Across all 18 DriveTime Automotive Group interview reports.

Interview formats

Technical 38.2%
Behavioral 38.2%
Coding 23.5%

Interview difficulty

Easy 27.8%
Average 66.7%
Difficult 5.6%

Candidate experience

Positive 64.7%
Negative 29.4%
Neutral 5.9%