Build the backend systems behind Ramp's underwriting, credit limits, and risk decisioning

Ramp is hiring a backend engineer for its Credit Engineering team, which owns systems influencing $100+ billion in annual payment volume through underwriting, automated limit management, and portfolio risk decisioning. The role requires 2+ years of backend engineering experience, Python proficiency, and experience with distributed/async systems that demand strict auditability and correctness. Based in New York, NY (hybrid).

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Real-time credit/risk decisioning systems
Automated limit management (stateful, scalable systems)
Auditability, observability, and correctness guarantees
Converting ambiguous business/risk problems into technical specs
Python backend engineering, distributed & async systems
Agentic workflows for automating credit decisions

Common question themes

Design a real-time system for automated credit limit adjustments

How do you guarantee auditability and correctness in a financial decisioning system

Convert an ambiguous risk-strategy problem into a concrete data model/spec

Tell me about a subtle correctness bug you caught in a high-stakes system

How would you design guardrails for an AI agent automating credit decisions

Describe your experience with distributed systems and async frameworks in production

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