Ramp engineering manager interview loop

careerveteran (Primly starter) · 5 replies

Went through the Ramp EM loop last fall. I'm a hiring manager myself with 15 years of experience, so I paid particular attention to what they were actually trying to evaluate versus what they said they were evaluating. Here's the real breakdown.

The rounds (for EM): Recruiter screen: see the other thread. Same basics apply. Engineering screen: yes, you still code. One medium problem, 45 minutes. This surprised some people I talked to. They want to know you can still think through code, even if your day-to-day is meetings. Not looking for perfection, looking for fluency. System design: same as IC loop in format. You're expected to think at the architecture level. At the EM level they also probe your instinct for team execution risks, not just technical ones. People leadership rounds (two): these are separate. One focused on coaching and developing engineers. One focused on cross-functional leadership and navigating up and sideways. Both interviewers asked for specific examples, pushed on what I actually did vs. what the team did. Hiring manager debrief: a conversation with the director or VP. Part assessment, part sales pitch. They're checking for culture fit at the leadership level.

What they really care about for EMs: Org health instincts. Not just can you ship, can you build a team that ships without you in the room. Directness. Ramp culture skews toward high directness. I got asked directly: "tell me about a time you had to tell an engineer they weren't meeting bar." They want specifics. Their scale is still Series D / early scale-up. They care about EMs who can operate in ambiguity without needing perfect process infrastructure.

Timeline: recruiter screen to offer was 16 days for me. They move fast.

Overall: the bar felt appropriately high for a company at their stage. Raise it below and you get regret hires. Raise it well and the team gets better.

5 replies

director_dee (Primly starter)

The coding round for EMs is a deliberate choice and honestly I respect it. At my company we dropped it for senior EMs and I sometimes regret that. Technical context-switching is a real skill.

firsttime_mgr (Primly starter)

How explicit were they about leveling? Like did they tell you what level of EM they were targeting, how many directs, team scope, etc.?

ux_uma (Primly starter)

Very explicit, which I appreciated. They told me expected team size (6-8), rough domain (spending controls infrastructure), reporting structure, and what the next 12 months looked like in terms of hiring headcount. I've been in loops where they play this close to the chest until late. Ramp didn't do that.

tired_recruiter (Primly starter)

16 days screen to offer is legitimately fast for an EM loop. A lot of companies take 4-6 weeks at this level. Good signal about their internal alignment.

Primly Team

One stage people tend to underestimate in EM loops is the evidence behind leadership stories. In most processes at this level, the interviewer is not just validating that you’ve coached, resolved conflict, or driven delivery. They’re testing whether you can isolate your direct actions, the constraints you faced, and the measurable signal that your approach worked.

A useful structure is: Context (team/product constraints) → Tension (what was breaking) → Your decision (what you did and why) → Tradeoffs (what you didn’t do) → Results (what changed) → Reflection (what you’d repeat or change). The common failure mode is staying at “I’m a collaborative leader” altitude, or describing what “we” did without a crisp decision you personally owned.

For folks who have been through Ramp’s EM loop or similar, what follow-up question most reliably exposed whether a leadership example was truly yours versus the team’s?