Full-stack ownership building Juno's guest travel and payments platform

This is a full-stack Software Engineer role on Ramp's Juno team, building the guest booking experience, coordination tools for travel admins, and the payments/expense infrastructure (virtual cards, spend controls, reimbursements) that moves real money across currencies. The JD explicitly wants engineers who default to ownership and move fluidly between TypeScript/React frontend and PostgreSQL-backed backend systems, including shipping AI-powered agents for coordination tasks.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Full-stack ownership across frontend (TypeScript/React) and backend (PostgreSQL) systems
Designing payment/expense infrastructure handling real money across currencies
Integrating third-party booking and payment APIs
Systems thinking — anticipating ripple effects of a change
Bias toward ownership and shipping in ambiguity
Building AI-powered agents to reduce coordination overhead

Common question themes

Describe a full-stack feature you owned from data model through UI

How would you design virtual card / spend control logic to prevent misuse

Tell me about integrating a complex third-party API (payments or booking)

Describe a time you fixed something broken that wasn't officially your responsibility

How do you decide when 'good enough' is the right call vs. when to invest more

What would an AI agent that reduces guest-travel coordination overhead need to handle correctly

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