Growth engineer owning Ramp's customer onboarding and application-decisioning flow

Interview for Ramp's Onboarding team, which owns the product flows and platform behind all new customer account creation, including the decisioning system that interfaces with fraud, compliance, and credit underwriting models. Expect metric-driven, ownership-heavy questions given the 2+ year bar and Ramp's 'high agency, high urgency' hiring philosophy.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

End-to-end feature ownership
Metric-driven / experimentation mindset
Automation of manual ops workflows (incl. AI-assisted)
Cross-functional partnership (product, risk, sales, ops)
Pragmatic problem-solving under ambiguity

Common question themes

A feature or workstream you owned from idea to shipped, measured impact

How you'd automate or scale an operations team's manual review process

Handling a fast-paced, ambiguous problem where the standard approach failed

Working with cross-functional stakeholders (risk, compliance, sales) on a shared flow

Experience with Python/Flask, SQL, or production AI/LLM use cases (if any)

Your bar for 'fast and reliable' shipping in a startup environment

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Ramp Software Engineer interviews

All Ramp interviews