They have a front-end LeetCode-style treasure hunt problem to complete the application.
I was curious and figured at least with something like this as part of the application, it would increase the chance that I get seen, so I took the time (~1 hour) to go through it and complete it.
You would think that having experience in all of the skills they require, plus already having been at the staff level for the past four years, plus successfully completing their problem-solving challenge in the application, would at least get you an intro interview... but you would be wrong.
What a waste of time.
The code challenge on the application begins with a Base64 encoded string. Once decoded, it reveals a Lambda URL.
Upon visiting this initial URL, you'll find a markdown document containing instructions. These instructions direct you to a second Lambda URL.
This second URL provides further instructions: a third, hidden URL resides within the HTML of the page rendered by the second URL. To find it, you must filter a collection of DOM nodes based on matching attribute conditions.
This process leads you to yet another Lambda URL. This final URL returns a string. The instructions state you must build a simple React app in CodeSandbox that fetches this string and displays it with a typewriter effect, using only React APIs (and no CSS).
The submission requires the "flag" (which is the string obtained from the last Lambda URL) and the link to your CodeSandbox project.
The following metrics were computed from 1 interview experience for the Ramp Staff Software Engineer | Frontend role in United States.
Ramp's interview process for their Staff Software Engineer | Frontend roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Ramp's Staff Software Engineer | Frontend interview process in United States.