Candidates applying for Senior Software Engineer roles take an average of 22 days to get hired, when considering 14 user submitted interviews for this role. To compare, the hiring process at Ramp overall takes an average of 19 days.
Common stages of the interview process at Ramp as a Senior Software Engineer according to 14 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 27%
Skills test: 27%
Group panel interview: 7%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Ramp (New York, NY) in May 2024
Interview
I was originally contacted in May of 2024 and proceeded to do an initial call. After the call I was given a cryptic puzzle to solve that would lead to a programming challenge. I solved that and moved on to the next round.
I moved on to a live coding interview. This live interview was a [1] coding problem. I passed this with no problem.
After this, I was scheduled for the 3-4 hour interview rounds, which included two coding challenges and one conversational interview designed to discover my breadth of experience. The coding challenges included developing a [2] JS class. I was very nervous during this interview and stumbled a lot but overall I felt like I did well. The second coding challenge was a [3] coding challenge and I solved this challenge as well. The interviewer was very invested in the process and was very positive. The third interview was a conversation about my experience with various technologies. I was told to prepare for this with details so I did. The conversation went well and the interviewer seemed very impressed with what I presented. A final interview with the hiring manager was also scheduled for the following day.
This is where I was thrown off. The interesting thing to note is that the recruiter told me she would provide updates throughout the process and I explicitly asked her if I would complete all interviews before a decision was made. I never received any updates and about 5 minutes before my final interview, I was sent a text message stating that they would not continue because they did not see a path to an offer. She offered to give me feedback and when I requested the feedback, I was ghosted.
I invested a ton of time with them and never felt like this would happen because my interactions were mostly positive. However, this put a sour taste in my mouth about the company.
To give you my two cents about my interactions, I had two people who were very positive and welcoming. They made the interviews easier to get through in terms of making you feel less nervous. The other 3 people that I interacted with seemed very cocky and self-righteous. They almost seemed annoyed at the fact that they had to interview someone. Take that for what it is but I believe that everything happens for a reason and this was just another learning experience with good interview practice.
Interview questions [1]
Question 1
[1] React calendar day-view
[2] JavaScript class for a spreadsheet with basic formula support
[3] React e-mail inbox
Engineering and recruiting teams were very nice.
However the question they asked was quite dumb and doesn’t really test for analytical skills. More like “out-of-the-box” thinking. Still pretty dumb. Avoid. Avoid. Avoid.
I applied through a recruiter. I interviewed at Ramp in Sep 2025
Interview
I got scheduled for a technical phone screen. I had prepared by going through Glassdoor, and got one of the questions that is repeated in the posts here. I had recently done another interview in which they asked something fairly similar, so I finished the problem in 20mins. The interviewer then gave me a "bonus" problem which was basically doing more HTTP calls with different edge cases. After making some progress, I ran out of time while handling another one of the bonus problem's edge cases. The next day I received a rejection with no explanation. It's weird to me that someone does pretty well because they were well-prepared, is given something called a "bonus", and then is rejected for no reason. I wouldn't have minded a rejection if I had done poorly, but the way it happened it seems the interviewer was accusing me of cheating, which is maybe a reflection on the company but more so on the interviewer himself.
Interview questions [1]
Question 1
Fairly straightforward question that involves knowledge of HTTP requests and simple algorithms. No need for Leetcode prep.
Recruiter round, then a technical -- completeness is important and they won't tell you that upfront there are multiple parts to the question that you must complete or they won't move you to next round.