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:
  • 1-hour CoderPad interview
  • Behavioral interview
  • Case study interview.

Pros

• Provided feedback about interviews.
• Interviewing engineers seem to have strong technical qualifications.

Pain Points

• 3 practically identical CoderPad interviews.
• Throughout the process, I was told placement would come later, but 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 company of 500+ people.
• 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.

Coderpads consisted of standard questions, reasonably solvable within the hour. You are not locked away from the internet, which was really helpful for looking up standard library components. In that way, it's more realistic to the day-to-day grind.

I won't list the problems word-for-word, but to give you an idea of the kinds of problems there were:

1. String/character counting and printing formatted output.
2. Reading data and computing an average, sum, or mean.
3. Making network requests and taking conditional actions based on response data.