Credit Acceptance logo

Credit Acceptance Software Engineer Interview Questions
& Process

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

Based on 17 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
47.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Credit Acceptance.

Showing 3 of 17
Credit Acceptance logo
Credit Acceptance

Software Engineer

Engineering · a year ago

Senior Easy Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

Started with a recruiter call, then had some "get to know you" rounds with the senior engineering manager, a "communication and culture" chat, a "technical deep-dive" (which wasn't really a deep dive, more like JS string and array functions, kind of a letdown), and a "critical thinking" interview. I'm still not sure about these "critical thinking / systems design" interview parts where they ask about global deployment, pen-testing, etc. I probably didn't do well on that.

Confirmed questions8 questions
  • Can you share an instance where your priorities had to be changed?
  • How would you handle a situation where you're working on a complex project and it looks like you won't meet the deadline?
  • What are the advantages of using Test-Driven Development (TDD)?
Credit Acceptance logo
Credit Acceptance

Lead Developer

Engineering · a year ago

Lead Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

I applied on the website and a recruiter reached out pretty quickly for a chat. It was a good call and they answered my questions. Right after, they asked for my availability for the next step, which I sent. The next round was supposed to be a technical screen with the hiring manager, but it was honestly one of the worst interviews ever. The manager was late, seemed unprepared, and even said the role was like being a 'dictator'. They asked about technologies not in the job description and had expectations way different from the posting. They asked super open-ended questions but wanted specific answers, and when I asked for clarification on a hypothetical problem, they got mad my example wasn't exactly like Credit Acceptance's. They also complained about their own team's issues without taking responsibility. When I asked about the biggest challenge, they said 'company culture' and then tried to backtrack. They also claimed to be Agile but couldn't explain SAFe and their methods seemed like anti-patterns. I told the recruiter I was withdrawing, but they never responded. The same job is still listed over a month later.

Confirmed questions6 questions
  • Have you used any technologies that weren't mentioned in the job description?
  • Can you elaborate on your approach to solving this hypothetical scenario?
  • What do you see as the primary difficulty associated with this position?
Credit Acceptance logo
Credit Acceptance

Software Engineer

Engineering

Mid Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Background check
Interview formats
Behavioral Technical Coding System Design

The interview process had 6 rounds total. It started with a recruiter screening for about 20-30 minutes. Then there was a Karat screening round, which was about 1 hour and included 3 scenario-based questions plus a coding question. Next, a critical thinking round focused on a 1-hour system design scenario. After that, a technical deep dive that lasted 1 hour. Finally, a behavioral round, also 1 hour. There was also a background check before the offer.

Confirmed questions6 questions
  • Regarding system design, what are KPIs?
  • How can one construct scalable APIs while maintaining performance?
  • What about the security of APIs?

Credit Acceptance Software Engineer Interview Questions

Quoted word for word from Credit Acceptance interview reports.

How would you filter a list of articles using a search keyword in HTML, CSS, and JavaScript?

Read reports

Can you write a simple HTML/CSS code to style the background of a page?

Read reports

What are the advantages of using Test-Driven Development (TDD)?

Read reports

How can one construct scalable APIs while maintaining performance?

Read report

How would you optimize a slow stored procedure if there were no budget or resource limitations?

Read report

Can you discuss the tradeoffs between Redux, Context, and Hooks?

Read report

What is your assessment of the team's current situation?

Read report

Formats, difficulty and experience

Across all 17 Credit Acceptance interview reports.

Interview formats

Behavioral 38.5%
Technical 35.9%
Coding 17.9%
System Design 7.7%

Interview difficulty

Easy 17.6%
Average 58.8%
Difficult 23.5%

Candidate experience

Positive 47.1%
Neutral 17.6%
Negative 35.3%