Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela Ramp em mar. de 2023
Entrevista
All in all I was a bit disappointed to not get the offer, but it may have been for the best. I would be worried that the immense VC funding may be incentivizing unsustainable company and revenue growth. ***Interview Process***
- 1 hour coderpad interview.
- 1 hour coderpad interview.
- Final round, consisting of (a) 1 hour coderpad interview (b) Behavioral interview (c) Case study interview.
***Pros***
- Provided feedback about interviews.
- Interviewing engineers seem to have strong technical qualifications.
***Pain points***
- 3 practically identical coderpad interviews.
- Through the process I was told placement would come later, but then I don't feel like I was interviewed by team members where placement would have actually been more aligned. Absolutely nothing against the members that interviewed me and I probably would have worked well on separate teams. I just think that I didn't speak with anyone on a team where that team's business objective matched well with my interests.
***Red flags***
- No processes to ensure diversity and inclusion, besides "focusing on the recruiting pipeline". This isn't really acceptable for a >=500 person company.
- Too many unorganized product teams. I got the sense that Ramp may be growing too fast, and isn't sure how to organize its teams to work together.
Perguntas de entrevista [1]
Pergunta 1
Coderpads consisted of standard questions, reasonably solvable within the hour. You are not locked away from the internet which was really helpful to look up standard library components, so in that way it's more realistic to the day-to-day grind. I won't list the problem word-for-word but to get an idea of what kind of problems there are:
1. String/character counting and printing formatted output
2. Reading data and computing [average / sum / mean]
3. Making network requests and taking conditional actions from response data.
Fiz uma entrevista na empresa Ramp (New York, NY).
Entrevista
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.
Candidatei-me por meio de recrutador(a). Fui entrevistado pela Ramp em set. de 2025
Entrevista
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.
Perguntas de entrevista [1]
Pergunta 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.