
Edmunds.com 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
Candidate interview experiences
First-hand accounts from people who interviewed at Edmunds.com.
Software Engineer
This interview left me with a bad taste in my mouth. I was really excited to interview with this company. They had technical issues in the beginning which made the interview start late. Then I was on video camera but they were not, so it was a bit uncomfortable for me since I was talking to google chat icons. Lastly, they didn’t give me enough time to look over the question and read the code. I maybe had maybe 2 minutes, maybe 3 and I was very confused during the technical. It didn’t leave a good impression because there were vital things I had missed had I gotten a chance to read the entire problem. The recruiter told me it would be a 15 min intro and 45 min technical. There was no intro, they didn’t ask a single question about myself. The first 20 min was the technical and then the rest of the time I got to ask questions. At the end I had one more question and the guy said we ran out of time, bye, and hung up. It was so abrupt and rude. Would not recommend to friends.
- Given two functions, one fast and one slow, how would you create a third function that improves its speed over time, potentially using caching?
- What are your methods for optimizing performance?
Software Engineer
First, there was a quick recruiter call to chat about my background and the job details. Then, if they liked me, I'd talk to the hiring manager. After that, there was a more technical phone call and finally a 3-hour onsite interview.
- What makes you want to work for Edmunds?
Software Engineer
So I had 2 phone interviews. The first one was with my direct report, and the second one was with his boss. Then I went on site for 4 interviews, each about an hour long, with a lunch break where I met my direct report. It all went pretty well. The very first interview was with my now boss's boss, and he had me build a parser using a recursive node builder algorithm. I got a bit nervous and needed a little extra time, but he was patient. The next interview was also 1 on 1. After that, I interviewed with my current boss and the team lead. We mostly covered design and architecture topics, along with some basic algorithms and how to implement them. The final interview was with another team lead and their manager. This was the toughest part. They asked some in-depth questions about threading and other algorithms. I felt really challenged afterwards but excited about the chance. Everyone was super nice, and I got a great overall vibe.
- lexicographic permutation algorithm
Edmunds.com Software Engineer Interview Questions
Quoted word for word from Edmunds.com interview reports.
“What is TCP/UDP?”
Read reports →“Knowing the max and min of an array, how can you improve the time complexity of a sort algorithm?”
Read reports →“Given two functions, one fast and one slow, how would you create a third function that improves its speed over time, potentially using caching?”
Read reports →“Solve this coding problem.”
Read reports →“Can you explain encapsulation?”
Read report →“How would you approach Algorithms and CS basics?”
Read report →“How would you design X system?”
Read report →“What are your thoughts on General + CS basics?”
Read report →“What are your methods for optimizing performance?”
Read report →Formats, difficulty and experience
Across all 8 Edmunds.com interview reports.