Build the API and agent surfaces that let developers and AI agents move billions through Ramp

Ramp's Dev API team owns the programmatic surfaces — APIs and agent interfaces — that let developers and AI agents read from and write to Ramp's finance platform. This interview probes backend API design, developer experience instincts, and daily hands-on use of AI coding agents as a primary way of building.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

API design and developer experience
Python/Temporal/Postgres backend architecture
Reliability and correctness at scale
AI-agent-first development workflows
End-to-end technical ownership

Common question themes

Walk me through a backend project you owned end-to-end, from architecture to rollout to monitoring

How would you design an API/endpoint used by thousands of external developers so it's hard to misuse?

Describe a time bad docs or bad error messages caused real pain — what would you have done differently

How do you use AI coding agents in your daily workflow, and where do you not trust them

How would you build tooling that lets other teams ship their own API surfaces (a 'software factory')?

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