Went through the Ramp frontend loop last month and wanted to write it up while it's fresh. Applied through LinkedIn, heard back in about a week, then a recruiter screen, then the technical stuff.
Phone screen (1 round) Typical intro call with a recruiter: background, why Ramp, logistics. Then a 45-min technical screen with an engineer. It was a React component problem: build a filterable list with debounced search. Nothing tricky at the surface, but they watched how I handled controlled vs uncontrolled inputs, whether I reached for useState vs useReducer, and whether I'd think about accessibility at all without being prompted. I added an aria-label without being asked and the interviewer mentioned it afterward, which felt like a good sign.
Onsite (4 rounds, all virtual) Round 1 was another coding round. Heavier on JavaScript fundamentals than I expected: closures, event loop, a question about how the browser handles microtasks vs macrotasks. Not leetcode-style algorithm work, more like "explain what this code does and why."
Round 2 was a UI design/build round. They gave me a prompt: design a spend approval flow component. I had to wireframe it verbally, then start building in a shared editor. They cared more about component structure and prop design than making it pretty. TypeScript was expected, not optional.
Round 3 was a system design round, frontend-flavored. Something like: design the client-side architecture for a real-time expense dashboard with live updates. I talked through WebSocket vs polling, state management, optimistic updates, and how you'd handle network failures gracefully. They pushed back on my first approach and I had to defend or revise.
Round 4 was behavioral. Standard stuff: conflict with a PM, time you had to push back on a scope change, how you'd mentor a junior dev.
Timeline: screened week 1, onsite week 3, decision week 5. Moved fast compared to most places I interviewed at in 2026.
Overall impression: they care a lot about product thinking on the frontend side. It's not just can-you-build-it, it's can-you-think-about-what-you're-building and why. Fintech context came up; they want people who understand that correctness matters more than clever.