Ramp · Primly Community

Ramp onsite / final round, how it really goes

market_realist · 6 replies

Went through the Ramp final round in March 2026. They call it an "onsite" but it was fully virtual for me. Five rounds, one day, with breaks. Here's the breakdown.

Round structure: Coding 1: 60 min, one medium-hard problem. See my notes above on their coding style. Coding 2: another 60 min, slightly different flavor, more systems-adjacent. System design: 60 min, design a core piece of their product. I got a version of the card transaction processing flow. Behavioral / leadership: 45 min. This one surprised me. It's real. They care about collaboration, conflict, how you've handled ambiguity. Had an eng manager on this one. Hiring manager 1:1: 30 min. This one felt like a mutual fit conversation. Ask about the team, the roadmap, what success looks like at 6 months.

What I noticed:

The debrief apparently happens same day or next morning. I got a verbal "likely moving forward" from the recruiter within 24 hours. Formal written feedback took another two days.

They don't ask Leetcode hard problems in the sense of "implement a segment tree." But they do expect you to reason through complex constraints. The fintech domain knowledge helps a lot. If you've worked in payments, banking, or expense systems before, say so early.

One thing nobody warned me about: the behavioral round will go deep on a specific conflict. They're not looking for a clean STAR story where you fixed everything. They want the messy part. What was hard about it. I gave an answer where I admitted I was wrong midway through and they seemed to respect that more than the times I tried to frame it cleanly.

Overall: five rounds is a lot but the day moved quickly and everyone was professional. I'd describe the vibe as "high-bar but not adversarial."

6 replies

remote_swe_42

"Not adversarial" is a good way to put it. My debrief was also same day. Recruiter texted me at 6pm with a preliminary thumbs up. Felt surprisingly human for a five-round loop.

brand_ben

Did they ask you anything about cross-functional work? I'm not SWE but reading these threads to understand the company culture.

infra_ines

The behavioral round definitely had cross-functional flavor. One question was about a time I had to ship something where design and eng had conflicting priorities. I think they care a lot about low-ego collaboration given how small the team still is.

staff_steph

The "messy part" point in the behavioral is so true across fast-moving startups at this stage. They want real. They've probably heard enough polished STAR stories to spot a rehearsed one in 30 seconds.

hardware_hugo

Five rounds for a non-FAANG is a lot. Do they give any rationale for it? Curious if it's actually predictive or just process debt from a previous regime.

infra_ines

Recruiter said it was intentional to reduce regret hires. Small team means a bad hire costs more than a slow hire. I get the logic even if a day of interviews is tiring.