J'ai postulé en ligne. J'ai passé un entretien chez Ramp
Entretien
Phone screen followed by a coding challenge. Phone screen was standard. So was the technical screen, though the interviewer showed up 15 minutes late after I had to email the recruiter asking if the interview was still happening.
I breezed through the coding challenge with time to spare, but then heard back the next day that they weren't moving forward because they wanted "cleaner code". It wasn't a clear response but if I was to give advice, I'd say don't focus on functionality as much as writing something that fits their style.
Questions d'entretien [1]
Question 1
Use React to make a 4x4 grid where each cell can have a normal, active, or dead state (should be reflected with colors). Clicking a cell will toggle it between normal and active, and activating a normal cell while another cell is active will make those two cells "fight" (use random number) and return one to normal and the other to dead. At the end, output the winning cell and all the cells that that cell defeated.
Follow up: "What would you change about the code if you were going to add more functionality to the cells later"
J'ai postulé en ligne. J'ai passé un entretien chez Ramp (Homewood, IL) en mars 2026
Entretien
Apply, get automated invite to coder pad to complete code test. Complete the code test, I then received an automated rejection. Code test allows 90 minutes for completion. Job description is permanently listed so they may just be farming data/applicants/resumes.
Questions d'entretien [1]
Question 1
get url from the dom using console getQuery, then GET that url and build wordle in react
I recently completed all stages of Ramp’s interview process, including initial CTF challenge then two technical rounds (which I was told I performed very well on), followed by final rounds focused on technical, behavioral, and architectural discussions. I came in prepared, felt aligned with the interviewers, and didn’t pick up on any signs of concern throughout.
Despite the time and energy invested, the final response was a brief note saying they wouldn't be moving forward—without any feedback or even a general comment like “it was a tough decision” or "sorry but we're looking for someone with different experience". While earlier rounds included constructive takeaways, the final stages offered nothing but a cold denial.
I’m very self-aware and typically can recognize when something hasn’t landed well, but in this case, there was little indication that anything was off. That’s exactly why feedback would’ve been valuable. As a candidate, you’re left wondering whether it was technical, communication-related, or something else entirely.
If you’re applying here, know that the process is structured and the team seems smart and kind—but don’t count on transparency or closure at the end if it doesn't go your way. Which can lead to a very negative and regrettable experience. Good luck!
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Ramp en avr. 2025
Entretien
There was a coding test while I applied for the job. Seemed straightforward enough. Took me around 20-25 minutes to get it done to the exact thing they wanted.
Received a very generic rejection email after a week. This shows that the company doesn't respect the candidates time and is trying to be the belle of the ball who wants all the suitors to try as hard as they can here.
One of the weirdest application experiences ever.
If they want their applicants to go through hoops like this,can't imagine how they are with their employees. Wouldn't recommend a workplace like this which can be a disaster for work like balance.
Questions d'entretien [1]
Question 1
Gave a base64 encoded string which resorts to a URL which points to a webpage. This webpage has a set of very simple yet convoluted requirements of what needs to be done. Basically, they give another web page and you have find the go through the elements and find grab another link. That link showed me the word 'treasure' which then had to be written out in a typewriter effect on a code sandbox project and then the link was to be submitted with the application.