
Prosper.com Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Prosper.com.
Software Engineer
The interview process had 5 rounds in total. These included 2 coding rounds, 1 System design round, 1 round focused on SQL and API design, and a Manager round. When it came to discussing numbers, the recruiter was quite aggressive. She didn't even congratulate me on the offer and rudely suggested I "shouldn't consider accepting the offer." In my opinion, accepting an offer should make both parties happy. Her view was that negotiation means the candidate has to concede while the company stays firm. This isn't fair when neither side is willing to compromise.
- Can you write SQL queries using group by and joins?
- Questions on Linked List coding problems.
- How would you find the Least Common Ancestor?
Software Engineer
The whole process was fast and organized. Communication was prompt, which helped things move along. The technical phone screen wasn't too hard. The on-site interviews were pretty standard for software engineering roles, including a mix of behavioral, experience-based, and technical questions. Although it was for a front-end job, the technical questions focused on general CS and JavaScript concepts, not CSS.
- Can you explain how to create a throttle function in JavaScript?
Software Engineer
So for this senior software engineer role, I went through about 4 or 5 rounds of interviews. I spoke with a project manager, a project lead, a backend dev, a frontend dev, and also HR. The job itself sounded okay at first, the work environment seemed manageable, but honestly, it ended up being a terrible experience. The manager was really strict, and the workload was huge with deadlines that were super tight. We had to get a lot of story points done each sprint, and the manager would really dig into our time estimates. We'd estimate based on our experience, and they'd go check with this senior dev who'd been there forever, and they'd always say it could be done way faster. Then the manager would just change the points. If we questioned it, we'd have to break down every single story point, hour by hour, and justify it. Just finishing one ticket was a nightmare, and the manager was constantly putting us down. It was just zero respect. Eventually, most of the team left, which I found out later when I talked to them.
- We'll start by discussing the company and then you can share your background.
- Can you solve three Data Structures and Algorithms problems in JavaScript in about an hour?
- Please explain the code you write for these DSA problems.
Prosper.com Software Engineer Interview Questions
Quoted word for word from Prosper.com interview reports.
“What is the least common ancestor of two nodes in a binary tree?”
Read reports →“Print the path from a given target node from the root or return it as a list?”
Read reports →“How do you delete the kth node from a LinkedList?”
Read reports →“What is the difference between SOAP vs REST?”
Read reports →“How would you count the number of islands given a 2d grid map of '1's (land) and '0's (water)?”
Read report →“What is the difference between an Abstract class and an Interface?”
Read report →“What is the difference between PUT vs POST?”
Read report →“What are the different types of exceptions in Java?”
Read report →“What are the latest features in JDK 1.8?”
Read report →Formats, difficulty and experience
Across all 12 Prosper.com interview reports.