Ramp Interview Questions — Page 3

Ramp·Software Engineer·Technical Phone Screen

May 2026

Ramp SWE interview with a meaty OOP/system design coding problem built around a banking simulator. The problem kept growing with each layer they added, which I wasn't fully expecting.

Design a banking system that supports creating accounts, depositing funds, transferring between accounts, and ranking accounts by total outgoing transaction volume.
Extend the banking system with a PAY operation that immediately debits an account and schedules a 2% cashback to be credited exactly 24 hours later. Each payment gets a unique ID. How do you structure the scheduling and ensure any operation after the due time reflects the credited balance?
How would you implement GET_PAYMENT_STATUS to return whether a cashback is still pending or has already been received, and handle invalid account or payment ID lookups?

“The first few operations felt manageable.”

View Post

Ramp·Software Engineer·Technical Phone Screen

May 2026

Coding round for a Software Engineer role at Ramp. One algorithmic problem, string manipulation flavored, but the constraint about needing a near-linear solution is what made it actually interesting rather than a trivial loop.

Given a string and an integer k where the string length is divisible by k, partition the string into consecutive non-overlapping blocks of length k. Return the minimum number of single-character replacements needed to make every block a palindrome.

“My first instinct was correct: for each block, just count mismatched mirror pairs and each mismatch costs one replacement.”

View Post

Ramp·Frontend Engineer·Take-home Assignment

May 2026

Ramp frontend interview had me building a mini Wordle clone in React, fetching the target word from an API and wiring up per-letter color feedback with a 6-guess limit. The unit tests were provided and mocking the endpoint was part of the deal, so you couldn't really fake your way through it.

Build a simplified Wordle game in React where the target word is fetched from a given HTTP endpoint. The game should handle user input, show per-letter feedback (correct position, present but misplaced, or absent), and stop on a win or after 6 attempts. Your implementation must pass provided unit tests that mock the API.

“The fetch part was fine, useEffect on mount, nothing wild.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend interview that was basically a testing-focused coding challenge. You get a React component with some specific behaviors and have to write Mocha + TypeScript tests covering the happy path, async timing, error states, and a single-run animation guarantee. More nuanced than I expected for a frontend screen.

You're given a React component that fetches a hidden flag from a URL, renders it with a typewriter animation, and must never retrigger that animation on re-render or remount. Write Mocha + TypeScript tests covering the happy path, async timing, the single-run guarantee, and error handling. Use sinon for mocking fetch and fake timers.

“The single-run guarantee part is what tripped me up.”

View Post

Ramp·Software Engineer·Technical Phone Screen

May 2026

Ramp coding screen for a software engineer role. One algorithmic problem, stock trading themed, which sounds like a classic leetcode variant but has a small twist with the unsorted multi-stock input format that can trip you up if you're not careful.

Given a list of unsorted trading records (date, stock ticker, price) for multiple stocks, compute the maximum total profit you can make across all stocks. You can make unlimited transactions per stock, hold multiple stocks simultaneously, but can only hold one unit of any single stock at a time and must start and end with no holdings.

“The core insight is the same as the classic 'best time to buy and sell stock with unlimited transactions' problem: just sum up every positive day-over-day price increase.”

View Post

Ramp·Software Engineer·Technical Phone Screen

May 2026

Ramp software engineer round focused on extending a recipe manager service with search and listing features. Pretty implementation-heavy with a side of design discussion about indexing trade-offs.

Implement a search function that returns all recipe IDs containing a given ingredient, case-insensitively, sorted by recipe ID ascending.
Implement a list function that returns all recipe IDs sorted by a given field like name, creation time, or ingredient count, with configurable ascending or descending order. Tie-breaking should always be recipe ID ascending.
Should you maintain an inverted index by ingredient to support O(1) lookups, or is a linear scan over all recipes acceptable? Walk through the trade-offs.

“Straightforward enough on the surface.”

View Post

Ramp·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round at Ramp for a software engineer role. Just one question but it had a lot of parts to it and I felt like I was scrambling to hit all of them.

Tell me about a project you're most proud of. What made it stand out, what did you specifically contribute, what obstacles came up, and what was the measurable impact?

“Four questions in one, basically.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend interview had me build a Wordle clone in React from scratch, no styling needed but the logic had to be solid. The component breakdown and state management discussion took up a good chunk of time alongside the actual coding.

Build a Wordle-style mini-game in React with up to 6 guess attempts, letter coloring logic (green/yellow/gray), correct duplicate letter handling, and win/loss detection.
Walk through how you'd break this into components and manage state across the app.

“The duplicate letter handling is where I stumbled.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

May 2026

Ramp frontend round focused on async data fetching inside React. Pretty technical for what I expected, they really wanted you to think through edge cases beyond just 'put it in useEffect'.

Inside a React component, fetch a flag value asynchronously on mount and manage loading, error, and success states. How do you structure this, and how do you expose the result to other parts of the component tree?
How do you handle cleanup of an in-flight fetch when the component unmounts, and what problems does skipping this cause?
React strict mode runs effects twice in development. How does that interact with your fetch-on-mount pattern, and what breaks if you haven't accounted for it?

“I went straight to useEffect with fetch and useState for the three states, which was fine.”

View Post

Ramp·Software Engineer·Technical Phone Screen

May 2026

Interviewed at Ramp for a software engineering role. The session started from a take-home Python script and pivoted into two bigger engineering judgment questions about Python trade-offs and what it'd actually take to ship the thing to production. Pretty conversational but the follow-ups had teeth.

What are the main advantages and disadvantages of Python as a language, particularly for data-processing and backend work?
What changes would you make to take this script from a single-file prototype to something running in a production pipeline?
The input feed grows to 50 GB and won't fit in memory. How does your design change?
The upstream feed occasionally sends a price of zero or an invalid date like February 30th. What's your policy for each case and why?
When would you choose not to use Python for this kind of service, and what would you use instead?
Show concretely how you'd represent and compare monetary values to avoid rounding bugs.

“I went in thinking this was a softball and started listing things like 'fast to write, great libraries' and the interviewer just waited.”

View Post