RevolutionParts logo

RevolutionParts Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
87.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at RevolutionParts.

Showing 3 of 8
RevolutionParts logo
RevolutionParts

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Technical Coding Behavioral

I started with a 30-minute initial interview at the college career fair. They then scheduled an on-site interview for the following week. The on-site lasted about 2-3 hours, where I talked with several engineers and the CTO. I got to ask a lot of questions and learned about Revolution Parts and what they do. It seemed tough at first, but I actually enjoyed it. I managed to finish all the interviews in one day, which was great. Talking to the employees, it really seems like a good place to work, and I'd definitely recommend interviewing here.

Confirmed questions4 questions
  • Questions about object-oriented principles
  • Questions about algorithms
  • Questions about runtime complexity
RevolutionParts logo
RevolutionParts

Software Engineer

Engineering · more than a year ago

Mid Easy Negative experience Decline offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical Coding

First had a quick chat with the recruiter. Then, a little over a week later, I went in for a 3+ hour interview at their office. During this second interview, I met with four different people. They asked me a mix of questions about my past experience and some technical stuff. After that, they told me I should hear back within a few days. Since it was a Friday, they said by the middle of the next week. I didn't hear back until two weeks later, with no apology and no other contact. They called to offer me a job but instead of telling me the details like position, salary, and benefits, they asked if I was ready to accept the job right then. I was honest and said I was looking for jobs elsewhere in the country because my S.O. was moving, but it would depend. They told me to reach out again when I was ready to commit and that was it. I still don't know what they were going to offer. It was a really weird interview/offer process and left a bad impression.

Confirmed questions2 questions
  • PHP code challenge on palindrome strings
  • Java OOP questions covering overriding and overloading
RevolutionParts logo
RevolutionParts

Senior Software Engineer

Engineering

Senior Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical System Design Behavioral

First, a quick chat with the recruiter about your background. Then, a short technical assessment covering backend or full stack tech, and system design for service and microservice setups. Finally, an interview with the hiring manager focusing on working with other teams and past project wins/losses.

Confirmed questions2 questions
  • Can you design a service using a service architecture pattern?
  • Now, design the same service but using a microservice architecture pattern.

RevolutionParts Software Engineer Interview Questions

Quoted word for word from RevolutionParts interview reports.

Can you write code to determine if a word reads the same forwards and backward?

Read reports

What are your thoughts on making the palindrome function more efficient?

Read reports

Could you tell me what happens behind the scenes when you visit a website like Amazon?

Read reports

Can you design a service using a service architecture pattern?

Read report

Can you tell me about the AI project that you worked on?

Read report

Formats, difficulty and experience

Across all 8 RevolutionParts interview reports.

Interview formats

Behavioral 32%
Technical 28%
Coding 24%
System Design 12%
Presentation 4%

Interview difficulty

Easy 12.5%
Average 87.5%
Difficult 0%

Candidate experience

Positive 87.5%
Negative 12.5%