Yodle Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Yodle.
Yodle
Software Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Take home Recruiter call Phone screen
Interview formats
Technical Coding System Design Behavioral
First I solved a harder problem from their website and got a call back in a couple of days. Then there was a minor tech screening with their HR recruiter who was nice and knew their stuff. We talked about my experience and some easy data structure questions. After that, I had a phone interview with an engineering manager. They asked about a project from my resume and then a question to design a small system using OOP. I clarified the requirements beforehand. The interview was straightforward, but I felt the time wasn't enough to design the system. The interviewer was patient and we had a good interaction.
Confirmed questions2 questions
- Can you tell me about your experience with a specific project from your resume?
- How would you design an order management system?
Yodle
Software Engineer
Mid Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation
Interview formats
Behavioral Technical Coding System Design
I got an email to set up a phone interview with HR. It was about 30 minutes, and we talked about me and some basic computer science stuff. Then, I had an hour-long interview with a software engineer who asked me a bunch of Java questions and some data structure problems. After that, I went to their NYC office for a full day of interviews. First, I talked to the head software engineer for an hour and had to solve a problem on the whiteboard. Then, I had an hour to code a simple Java problem on their computers. After lunch, I met with a product lead and then the CTO.
Confirmed questions7 questions
- Can you share a contribution you've made?
- Tell me about yourself.
- Basic CS questions
Yodle
Software Engineer
Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Coding Behavioral Technical
Applied online, then I guess my resume got seen cause I solved some coding problems from their website. The interviewer called me soon after. They asked some easy technical questions, but then they got hung up on whether I was ready to move to Manhattan, saying I wasn't educated enough about the area since I'd never lived there and needed to do more research. This seemed to be their main focus over the actual interview questions, which were pretty basic. Never heard back after that.
Confirmed questions4 questions
- Can you implement a hash map using a tree?
- How does the memory usage differ between a stack and a queue?
- Which do you prefer, strongly typed or weakly typed languages, and why?
Yodle Software Engineer Interview Questions
Quoted word for word from Yodle interview reports.
“Can you implement a hash map using a tree?”
Read reports →“How would you determine the deepest common ancestor of two nodes in a binary search tree?”
Read reports →“What distinguishes the heap from the stack in terms of memory management?”
Read reports →“What is the difference between heap and stack?”
Read reports →“Can you sort an array of integers that is in a 250GB file?”
Read report →“What is the difference between a stack and a queue?”
Read report →“How does the memory usage differ between a stack and a queue?”
Read report →“Could you implement a hash map using an array?”
Read report →“How would you implement a stack using a list?”
Read report →Formats, difficulty and experience
Across all 19 Yodle interview reports.