Ramp Interview Experiences

7 results

• 

  60-Minute CoderPad Maze Crawl Over HTTP, No PassRamp · Software Engineer · Technical Screen · Sep 2026

  Rejected

  Format: 60 min, live coding in CoderPad. Problem: You're given a base URL for a "maze" served over HTTP. A GET on the base URL returns JSON with a list of next step IDs: You then GET base_url/{step_id} for each step, which returns more next steps. You need to explore until you find the exit. Things to handle: Dead ends: {"next_steps": []} Flaky server: some requests return Service Temporarily Una…

• 

  URL Maze BFS Tech Screen with Flaky 503s and a Silent InterviewerRamp · Software Engineer · Technical Screen · Sep 2026

  In progress

  Just finished my Ramp tech screen today, so here's the writeup. Process: one hour, one question, 5 minutes of Q&A at the end. Question: URL Maze (a classic that keeps showing up in past interview reports) You're given a start URL. Calling it returns JSON where the key is next_stops and the value is a list of paths. You append each path to the host and keep visiting, until some URL returns {"messa…

• 

  Ramp Account Executive interview experience: 45-minute presentationRamp · Account Executive · Jul 2026

  Rejected

  The process was long. The recruiter kept me updated, but the timeline still stretched out to roughly six interviews. The biggest demand was a 45-minute presentation that took about 20 hours to prepare. I received positive feedback during the stages I completed, so I expected a clearer ending. Instead, I got a rejection email with almost no explanation. After putting in that much time, I wished th…

• 

  Ramp Software Engineer interview: AI-assisted development screenRamp · Software Engineer · HR Screen · Jul 2026

  After a recruiter reached out, I had a short screen that was mostly about how I use AI day to day. We discussed what I had built or worked on with coding assistants and answered questions directly about AI-assisted development. The recruiter did not go deeply into much else, so the AI emphasis was clear. The next step was another technical conversation with a practical coding feel. It had two par…

• 

  URL Maze BFS Problem, Rejected Over a Debugging MissRamp · Software Engineer · Technical Screen · Apr 2026

  Rejected

  The question was the "URL maze, find the exit" problem that's already known on this forum. Right from the start we were just talking through it, testing the URL, then I wrote the program, and finally wrote a BFS solution that passed. The follow-up: they swapped in a different URL and had me run my Part 1 solution against it, and this time it didn't pass — I needed to handle status codes like 503…

• 

  Recursive URL-Fetching Round Under Time PressureRamp · Software Engineer · Technical Screen · Feb 2026

  They give you a URL, and you have to call it. The response might contain a new set of URLs, or it might contain other data; then you keep calling whichever URLs come back, recursing/iterating like this until you finally get back "congrats". You don't need to return the path, just the final URL. The problem itself isn't especially hard, but overall it's pretty tedious and practical. During the int…

• 

  Four Onsite Rounds, No OfferRamp · Software Engineer · Onsite · Jan 2026

  Rejected

  Coding (I'm posting the full original question) Given a list of flights: Part 1: get_user_with_most_flights() Part 2: get_user_location(time) The problem itself wasn't hard — a classic binary search question. But I had to figure out on my own how to import the file (the file and the test weren't even in the same folder), and I wasn't that familiar with writing tests in pytest, so I spent some tim…