DealerOn Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at DealerOn.
DealerOn
Software Engineer
Mid Easy Neutral experience No offer 6 rounds
Interview process
Take home Recruiter call Technical screen Onsite Panel Group Presentation Offer
Interview formats
Coding Behavioral Technical System Design
So the process started with a take home coding test, which was pretty standard OOP stuff. After that, I had a phone screen with the recruiter, which was basically just a questionnaire about my background. Then came the on-site, which was three separate interviews. First was a technical one, second was about work experience, and the last was a chat with management. The on-site itself was good, but the recruiter was kinda rough. They admitted to not reading my resume at the start of the phone call and then just complained about the format. Later, they called about a potential offer but wanted me to take less money than I initially asked for. When I asked how much less, they told me to make an offer. I did, even lower than my initial application, but they still said they probably couldn't match it. Never had a recruiter ask me to name my lowest acceptable salary before, felt like they were trying to lowball me.
Confirmed questions3 questions
- Can you design a program to tackle a straightforward issue using object-oriented programming in either Java or C#?
- Could you explain the distinction between relational and non-relational databases?
- How do you approach situations when you find yourself stuck on a work-related problem?
DealerOn
Software Engineer
Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Coding Behavioral
The interview was pretty laid-back, mainly to get a feel for your skills and how you approach work and problem-solving. They asked about your knowledge of their tech stack and general development concepts and routines.
Confirmed questions2 questions
- Can you walk me through your solution to the code test and your thoughts on the problem?
- Tell me about how you solved the code test and your understanding of the problem.
DealerOn
Software Engineer
Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding Technical
I first talked to a recruiter, and then they sent me a take-home assignment that was supposed to take 4-6 hours to complete. If you have a busy life, especially as a parent, this is a real bummer. You might end up spending your Saturday afternoon coding and then never even hear back from them. They won't even send a rejection email. So, unless you've got nothing else going on on a Saturday, I'd say avoid applying here.
Confirmed questions3 questions
- Create a program simulating a Mars Rover.
- Build a program that simulates a register.
- Develop a program to calculate distance.
DealerOn Software Engineer Interview Questions
Quoted word for word from DealerOn interview reports.
“Build a program that simulates a register.”
Read reports →“Create a program simulating a Mars Rover.”
Read reports →“Could you explain the distinction between relational and non-relational databases?”
Read reports →“If you had abundant financial resources, what type of software would you aspire to create?”
Read reports →“Can you design a program to tackle a straightforward issue using object-oriented programming in either Java or C#?”
Read report →“Can you walk me through your solution to the code test and your thoughts on the problem?”
Read report →“How do you approach situations when you find yourself stuck on a work-related problem?”
Read report →“Tell me about how you solved the code test and your understanding of the problem.”
Read report →Formats, difficulty and experience
Across all 6 DealerOn interview reports.